OpenTrainTimes incident

Database cluster issues

Resolved after 4 days 23 hours, affecting Train movement data and Schedule data, on February 22, 2023.

monitoring Feb 22, 2023, 10:01 PM UTC

One of our database clusters failed during our nightly import of timetable data. As a result, the public website may be showing incorrect data for 23rd February 2023. We are in the process of restoring from a backup.

Started
Feb 22, 2023, 08:56 PM UTC
Resolved
Feb 27, 2023, 08:56 PM UTC
Duration
4d 23h
Detected by Pingoru
Feb 22, 2023, 08:56 PM UTC

Affected components

Train movement dataSchedule data

Update timeline

  1. identified Feb 22, 2023, 08:56 PM UTC

    Engineers have detected a problem with one of our database clusters

  2. monitoring Feb 22, 2023, 10:01 PM UTC

    One of our database clusters failed during our nightly import of timetable data. As a result, the public website may be showing incorrect data for 23rd February 2023. We are in the process of restoring from a backup.

  3. resolved Feb 27, 2023, 08:56 PM 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.

Add your stack →