Is OpenTrainTimes TD Feed Down? Check the current OpenTrainTimes TD Feed status

OpenTrainTimes TD Feed is operational

Updated a few minutes ago

OpenTrainTimes TD Feed not working for you?

Monitoring OpenTrainTimes since December 2021. Learn more

0 incidents in 2025

Current OpenTrainTimes official ongoing incidents

No incidents reported in OpenTrainTimes's status page

IsDown pulls data from OpenTrainTimes's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.

OpenTrainTimes TD Feed issues reported by users in the last 24 hours

This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.

Latest user comments about OpenTrainTimes TD Feed problems

No comments yet

OpenTrainTimes TD Feed outage history

IsDown has tracked 4 incidents for OpenTrainTimes TD Feed since started monitoring OpenTrainTimes status in December 2021.

  • Nov 16 2024

    4 months ago · lasted about 2 hours

    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. More details

  • Aug 01 2024

    8 months ago · lasted about 4 hours

    A problem with one of our servers has resulted in a lack of rail data to all subscribers. Engineers are investigating. More details

  • Aug 08 2022

    over 2 years ago · lasted 3 minutes

    From around 0802, we have been seeing a complete loss of service on our TRUST feed. This has been resolved, however there is now instability on our TD feed. More details

  • Dec 2021 ...
    IsDown started monitoring OpenTrainTimes status

    We've tracked and collected 4 incidents for OpenTrainTimes TD Feed since started monitoring OpenTrainTimes status

OpenTrainTimes TD Feed outages in the last 30 days

Number of Incidents

0 issues

Last incident

118 days ago

Having problems with OpenTrainTimes TD Feed? What can you do?

  1. First, stay calm.

    • We know it's stressful when OpenTrainTimes TD Feed is down, but running around is not going to fix it.
    • Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.
  2. Make a quick evaluation of the impact

    • Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
    • Did OpenTrainTimes TD Feed already acknowledge the issue? And published a status update? (You can find it in the top of the page or in OpenTrainTimes TD Feed status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.
  3. Communicate with your team and users quickly

    • If OpenTrainTimes TD Feed is having problems and impacting your business, it's important to keep your team and users informed.
    • Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
    • If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.
  4. Understand the root cause

    • After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
    • Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.
  5. Is there any mitigation for the issue?

    • Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
    • Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.
  6. Service has recovered?

    • Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.
  7. Post-incident analysis

    • Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
    • Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
  8. Prepare for the next incident, because it will happen again

    • Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
    • Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by monitoring them for you and alerting you if they are having issues, and create status pages to communicate with your team and users.

Reports by users in other services in the last 12 hours

Snapchat https://www.snapchat.com/
Snapchat user reports
Mangakakalot https://mangakakalot.com/
Mangakakalot user reports
Meta https://meta.com
Meta user reports
Astound https://www.astound.com/
Astound user reports
Google Workspace https://workspace.google.com/
Google Workspace user reports
Discord https://discord.com/
Discord user reports
Apple https://apple.com
Apple user reports
Adobe https://adobe.com/
Adobe user reports
Buildkite https://buildkite.com/
Buildkite user reports
Microsoft Office 365 https://www.office.com/
Microsoft Office 365 user reports

Frequently Asked Questions

Is OpenTrainTimes TD Feed down today?

OpenTrainTimes TD Feed isn't down. You can check OpenTrainTimes TD Feed status and incident details on the top of the page. IsDown continuously monitors OpenTrainTimes TD Feed official status page every few minutes. In the last 24 hours, there were 0 outages reported.

What is the current OpenTrainTimes TD Feed status?

OpenTrainTimes TD Feed is currently operational. You can check OpenTrainTimes TD Feed status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.

Is there a OpenTrainTimes TD Feed outage now?

No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.

Is OpenTrainTimes TD Feed slow today?

Currently there's no report of OpenTrainTimes TD Feed being slow. Check on the top of the page if there are any reported problems by other users.

How are OpenTrainTimes TD Feed outages detected?

IsDown monitors the OpenTrainTimes TD Feed official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.

When was the last OpenTrainTimes TD Feed outage?

OpenTrainTimes TD Feed last outage was on November 16, 2024 with the title "Disruption to incoming data feeds"

OpenTrainTimes not working for you? How do I know if OpenTrainTimes is down?
How IsDown compares to DownDetector?

IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.