User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
opentraintimes.com · Cloud & developer
Is OpenTrainTimes down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → opentraintimes.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 165 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 12 | 0 | 0.0 | 1118 ms | 0 |
| Tue 14 | 0 | 0.0 | 1091 ms | 0 |
| Tue 16 | 0 | 0.0 | 1017 ms | 0 |
| Tue 19 | 0 | 0.0 | 1114 ms | 0 |
| Tue 21 | 0 | 0.0 | 1038 ms | 0 |
| Tue 23 | 0 | 0.0 | 1123 ms | 0 |
| Wed 01 | 0 | 0.0 | 1079 ms | 0 |
| Wed 04 | 0 | 0.0 | 533 ms | 0 |
| Wed 06 | 0 | 0.0 | 743 ms | 0 |
| Wed 08 | 0 | 0.0 | 1000 ms | 0 |
| Wed 10 | 0 | 0.0 | 1039 ms | 0 |
| Wed 13 | 0 | 0.0 | 940 ms | 0 |
| Wed 15 | 0 | 0.0 | 1114 ms | 0 |
| Wed 17 | 0 | 0.0 | 931 ms | 0 |
| Wed 19 | 0 | 0.0 | 672 ms | 0 |
| Wed 21 | 0 | 0.0 | 1244 ms | 0 |
| Wed 23 | 0 | 0.0 | 1125 ms | 0 |
| Thu 02 | 0 | 0.0 | 1182 ms | 0 |
| Thu 04 | 0 | 0.0 | 930 ms | 0 |
| Thu 06 | 0 | 0.0 | 1030 ms | 0 |
| Thu 08 | 0 | 0.0 | 972 ms | 0 |
| Thu 10 | 0 | 0.0 | 1042 ms | 0 |
| Thu 12 | 0 | 0.0 | 966 ms | 0 |
| Thu 14 | 0 | 0.0 | 879 ms | 0 |
| Thu 16 | 0 | 0.0 | 857 ms | 0 |
| Thu 18 | 0 | 0.0 | 1059 ms | 0 |
| Thu 20 | 0 | 0.0 | 569 ms | 0 |
| Thu 22 | 0 | 0.0 | 1036 ms | 0 |
| Fri 00 | 0 | 0.0 | 849 ms | 0 |
| Fri 01 | 0 | 0.0 | 1000 ms | 0 |
| Fri 03 | 0 | 0.0 | 1101 ms | 0 |
| Fri 06 | 0 | 0.0 | 1169 ms | 0 |
| Fri 08 | 0 | 0.0 | 976 ms | 0 |
| Fri 10 | 0 | 0.0 | 920 ms | 0 |
| Fri 12 | 0 | 0.0 | 1064 ms | 0 |
| Fri 14 | 0 | 0.0 | 1096 ms | 0 |
| Fri 16 | 0 | 0.0 | 1139 ms | 0 |
| Fri 17 | 0 | 0.0 | 1051 ms | 0 |
| Fri 18 | 0 | 0.0 | 1071 ms | 0 |
| Fri 20 | 0 | 0.0 | 1061 ms | 0 |
| Fri 22 | 0 | 0.0 | 907 ms | 0 |
| Sat 00 | 0 | 0.0 | 957 ms | 0 |
| Sat 02 | 0 | 0.0 | 711 ms | 0 |
| Sat 03 | 0 | 0.0 | 1014 ms | 0 |
| Sat 05 | 0 | 0.0 | — | 1 |
| Sat 07 | 0 | 0.0 | 884 ms | 0 |
| Sat 08 | 0 | 0.0 | 1036 ms | 0 |
| Sat 10 | 0 | 0.0 | 612 ms | 0 |
Reliability
98.86% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live OpenTrainTimes badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for OpenTrainTimes yet. Outages of 10 minutes or more get their own page here.
Having trouble with OpenTrainTimes?
One report per service every 10 minutes from this network. No account.
Follow OpenTrainTimes
Get an email when OpenTrainTimes goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OpenTrainTimes alerts to Slack, Discord or a webhook — free.
About OpenTrainTimes
We track OpenTrainTimes (opentraintimes.com) as part of the Cloud & developer group. Find detailed information on trains running in Great Britain
OpenTrainTimes publishes an official status page at status.opentraintimes.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 98.86% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 928 ms average, 165–1139 ms range across 15 successful checks.
Questions
Is OpenTrainTimes down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was OpenTrainTimes last down?
We have not recorded a public OpenTrainTimes incident since monitoring began 9 days ago.
What is OpenTrainTimes's uptime?
From our own checks: 98.86% over 9 days of checks.
How fast does OpenTrainTimes respond?
928 ms on average over the last 24 hours (165–1139 ms).
Does OpenTrainTimes have an official status page?
Yes, at https://status.opentraintimes.com.
OpenTrainTimes not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report OpenTrainTimes here at once, the problem is on OpenTrainTimes's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with OpenTrainTimes. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.