Is OpenTrainTimes down?

Last checked 3m ago
Current status
OpenTrainTimes is up

No incidents right now.

OpenTrainTimes is operational right now. Last checked 3m ago; the most recent incident resolved 6d ago.

Real-time OpenTrainTimes status, recent outages, and incident history: pulled directly from OpenTrainTimes's official status page at status.opentraintimes.com every 5 minutes. Pingoru tracks 18 OpenTrainTimes services and has captured 3 incidents in the last 90 days (99.44% uptime). Get email, Slack, Discord, or webhook alerts the moment OpenTrainTimes reports a new incident, free for 3 monitors, no credit card.

Users who monitor OpenTrainTimes also follow these No-Code services: Zapier Airtable Webflow Typeform IFTTT Vasion Bubble Skylight Coda DoorDash View all 8,000+ providers
OpenTrainTimes uptime 99.44% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 5h 56m
    Started Oct 25, 2026, 03:10 AM UTC · Resolved Oct 25, 2026, 09:06 AM UTC
    TRUST FeedTrain movement data
    Timeline · 2 updates
    • monitoring · Oct 25, 2026, 08:22 AM UTC

      A problem with an upstream industry system is preventing train movement messages from being received by us and many other parties.

    • resolved · Oct 25, 2026, 12:13 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 3h 33m
    Started Oct 14, 2026, 01:57 PM UTC · Resolved Oct 14, 2026, 05:31 PM UTC
    Train movement dataMap data
    Timeline · 3 updates
    • monitoring · Oct 14, 2026, 01:57 PM UTC

      Engineers have been alerted to a problem with processing our TRUST and TD feeds, caused by a server issue on our side. Data is now flowing again, but may lag behind reality for about 15 minutes.

    • monitoring · Oct 14, 2026, 04:32 PM UTC

      The performance issue persists, and we have assigned additional servers to process the backlog of data

    • resolved · Oct 14, 2026, 05:31 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 19m
    Started Oct 03, 2026, 01:27 PM UTC · Resolved Oct 03, 2026, 01:46 PM UTC
    Train movement dataMap data
    Timeline · 3 updates
    • identified · Oct 03, 2026, 01:27 PM UTC

      Maps and schedule performance data are not updating at present due to an infrastructure issue. Engineers are investigating.

    • monitoring · Oct 03, 2026, 01:37 PM UTC

      This fault has been rectified, and maps are currently updating with the backlog of data

    • resolved · Oct 03, 2026, 01:46 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Incident record

Since April 2026 · Statuspage by Atlassian · 18 components checked every 5 minutes
52incidents recorded
7last 12 months
3last 90 days
4 hourstypical duration, 12 months

The longest incident in the last year, 404 errors due to excessive traffic on May 16, 2026, ran for 15 hours.

Most affected components, last 12 months

  • Train movement data4
  • Map data3
  • Schedule data2
  • Network Rail Open Data feeds1
  • TRUST Feed1

Latest incidents

  • TRUST reporting outage October 25, 2026 · 6 hours · major outage

    A problem with an upstream industry system is preventing train movement messages from being received by us and many other parties.

  • TD and TRUST feed issue October 14, 2026 · 4 hours · degraded service

    Engineers have been alerted to a problem with processing our TRUST and TD feeds, caused by a server issue on our side. Data is now flowing again, but may lag…

  • Degraded real-time information October 3, 2026 · 19 minutes · major outage

    Maps and schedule performance data are not updating at present due to an infrastructure issue. Engineers are investigating.

Outage history

Past 90 days · 3 incidents View full outage history →