Resolved after 4 hours 44 minutes, affecting Train movement data and Map data, on June 29, 2022.
We are down to a backlog of about 20-25 minutes of messages on the server, which should be clear by 1100
Affected components
Train movement dataMap data
Update timeline
- identified Jun 29, 2022, 05:43 AM UTC
A problem with one of our servers means that, from 0315 today, we have not been processing any data. Engineers are working on a fix.
- monitoring Jun 29, 2022, 06:00 AM UTC
The issue has been resolved and maps are now updating again, but may be showing stale data for the next couple of hours.
- monitoring Jun 29, 2022, 09:30 AM UTC
We are down to a backlog of about 20-25 minutes of messages on the server, which should be clear by 1100
- resolved Jun 29, 2022, 10:28 AM UTC
This incident has been resolved.
Your product runs on more than OpenTrainTimes
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services