Planned PTIPS Outage for All Modes – 29 March 2026

Status Updates
1

A planned PTIPS outage is scheduled for the early hours of Sunday morning and will affect all GTFS static and real-time feeds.

What’s Happening?

  • Improvements to real-time bus information by generating bus predictions for the next trip during dead running.

  • Modify the GTFS feed response content type by removing UTF-8 binary for proto.

Outage Window:
From: 29 March 2026, 01:00 AM
To: 29 March 2026, 03:30 AM

Services Impacted:
All modes – GTFS static and real-time feeds

2

Is there an issue with the TrainLink coach feed? There were many periods yesterday where data was unavailable and today no data has been received since 10:15am.

3

Hi @james00 ,

We can see from our side that coaches are running in real-time today.

Could you please tell us whether you are experiencing an issue with a particular coach or with the TrainLink feed in general?

Could you please also share a screenshot of the issue you are encountering?

Regards,
Suraj

4

Hi Suraj,

The issue is with all TrainLink coach services (rail seems unaffected?)

For example, this is a snippet of the vehicle position feed I have pulled at approx 17:05 - The timestamps in the feed are shown below but have not updated since 15:43. Vehicles are showing “in service” but not receiving position updates.

As I type this updates have resumed again, but for the last 2 days there have been consistent drop outs for 1+ hours as shown in this example. I have cross referenced my data against other 3rd party apps such as AnyTrip who are also showing stale/outdated timestamps.

{
“vehicle_id”: “336VWM”,
“trip_id”: “168.300326.127.1513”,
“route_id”: “4T.C.168”,
“latitude”: -28.328922271728516,
“longitude”: 153.40338134765625,
“stop_id”: “24841”,
“current_status”: 1,
“timestamp”: 1774845830
},
{
“vehicle_id”: “724VGM”,
“trip_id”: “172.300326.127.1500”,
“route_id”: “4T.C.172”,
“latitude”: -28.133193969726562,
“longitude”: 153.4700469970703,
“stop_id”: “42172”,
“current_status”: 2,
“timestamp”: 1774845823
},
{
“vehicle_id”: “7171MO”,
“trip_id”: “361.300326.17.1440”,
“route_id”: “4T.C.361”,
“latitude”: -31.567768096923828,
“longitude”: 148.78717041015625,
“stop_id”: “28271”,
“current_status”: 2,
“timestamp”: 1774845824
},
{
“vehicle_id”: “1328 MO”,
“trip_id”: “540.300326.1.1235”,
“route_id”: “4T.C.540”,
“latitude”: -32.586952209472656,
“longitude”: 149.59442138671875,
“stop_id”: “28504”,
“current_status”: 2,
“timestamp”: 1774845855
},

5

31/03 update - position updates are been received as normal. Have not encountered any issues today. Thank you.

EDIT: position updates are delayed again. Issue does not seem to be resolved.

1 Like
6

Hi James,

we are sending the details of your investigation to the NSW Trains data team. We haven’t had any alarms or outages for NSW Trains realtime feeds but there is obviously some issues with the coaches.

Just out of interest, how did you find out there were realtime issues with the coaches specifically?

Thank you,
Marcela

7

Hi Marcie

Thanks for the update.

I split the TrainLink feed using the “C” identifier in the route_id to get coaches specifically. I have notifications setup for any feed that does not present timestamp updates for greater than 11 minutes. TrainLink is one of the feeds I monitor along with other NSW bus feeds and other states also.

So for the last 2 days the TrainLink feed has been pinging me constantly with stale timestamps. I have been monitoring the TrainLink feed since May last year but have not previously had this as an issue.

At time of typing, no updates to the coaches has been received for 72 minutes.

1 Like
8

Hi James,

just to let you know a ticket was raised yesterday for this issues. They are working on the route cause.
They have tried a manual work around to update the databases - not sure how well that’s going.
Will keep you updated on their progress.

Cheers,
Marcela

9

Awesome - thanks for the update.

1 Like