Advertisement · 728 × 90

Posts by OpenTrainTimes

This issue was resolved around 1300 today. We are still awaiting insight in to the root cause.

11 months ago 1 0 0 0

[status] Investigating: Engineers have identified high latency on our real-time feeds from the Network Rail Open Data platform. As a result, the real-time components of the website will be showing out-of-date or missing data. stspg.io/803310a12?u=...

11 months ago 1 0 0 1

Nothing out of the ordinary

1 year ago 0 0 0 0
Post image

To give you an idea of the relative volume of requests per second we handle, before 0100 is 'normal', and after 0100 is the excess of traffic. We have plenty of space for growth, but there's a limit!

1 year ago 0 0 0 0
Preview
404 errors due to excessive traffic From around 0100 on Friday 14th February, a number of IP addresses on the same network were scraping thousands of pages on our site, causing 404 errors to be returned to users. These addresses have b...

From around 0100 on Friday 14th February, a number of IP addresses on the same network were scraping thousands of pages on our site, causing 404 errors to be returned to users.

These addresses have been blocked and the website is now operating normally.

status.opentraintimes.com/incidents/lw...

1 year ago 0 0 2 0
Preview
Disruption to incoming data feeds OpenTrainTimes's Status Page - Disruption to incoming data feeds.

[status] Identified: Since around 1300, we have been having issues with our data feeds from Network Rail. This appears to be an industry-wide problem, and we are working to find a resolution. status.opentraintimes.com/incidents/31...

1 year ago 1 0 0 0

We're over here now

1 year ago 6 0 0 0