User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
temporal.io · Money
Something is off: the vendor reports a minor incident. Official status: Partially Degraded Service
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
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.
Reachable from all 4 regions we check from.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1210 ms · 4 min ago.
Minor incident
Partially Degraded Service Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 04:30 | 0 | 0.0 | 1396 ms | 0 |
| 04:45 | 0 | 0.0 | 802 ms | 0 |
| 05:00 | 0 | 0.0 | 1563 ms | 0 |
| 05:15 | 0 | 0.0 | 659 ms | 0 |
| 05:30 | 0 | 0.0 | 669 ms | 0 |
| 05:45 | 0 | 0.0 | 885 ms | 0 |
| 06:00 | 0 | 0.0 | 800 ms | 0 |
| 06:15 | 0 | 0.0 | 892 ms | 0 |
| 06:30 | 0 | 0.0 | 761 ms | 0 |
| 06:45 | 0 | 0.0 | 1304 ms | 0 |
| 07:00 | 0 | 0.0 | 951 ms | 0 |
| 07:15 | 0 | 0.0 | 1111 ms | 0 |
| 07:30 | 0 | 0.0 | 828 ms | 0 |
| 07:45 | 0 | 0.0 | 818 ms | 0 |
| 08:00 | 0 | 0.0 | 716 ms | 0 |
| 08:15 | 0 | 0.0 | 838 ms | 0 |
| 08:30 | 0 | 0.0 | 799 ms | 0 |
| 08:45 | 0 | 0.0 | 761 ms | 0 |
| 09:00 | 0 | 0.0 | 787 ms | 0 |
| 09:15 | 0 | 0.0 | 800 ms | 0 |
| 09:30 | 0 | 0.0 | 1090 ms | 0 |
| 09:45 | 0 | 0.0 | 588 ms | 0 |
| 10:00 | 0 | 0.0 | 871 ms | 0 |
| 10:15 | 0 | 0.0 | 769 ms | 0 |
| 10:30 | 0 | 0.0 | 793 ms | 0 |
| 10:45 | 0 | 0.0 | 825 ms | 0 |
| 11:00 | 0 | 0.0 | 764 ms | 0 |
| 11:15 | 0 | 0.0 | 954 ms | 0 |
| 11:30 | 0 | 0.0 | 858 ms | 0 |
| 11:45 | 0 | 0.0 | 849 ms | 0 |
| 12:00 | 0 | 0.0 | 611 ms | 0 |
| 12:15 | 0 | 0.0 | 982 ms | 0 |
| 12:30 | 0 | 0.0 | 963 ms | 0 |
| 12:45 | 0 | 0.0 | 909 ms | 0 |
| 13:00 | 0 | 0.0 | 713 ms | 0 |
| 13:15 | 0 | 0.0 | 952 ms | 0 |
| 13:30 | 0 | 0.0 | 1104 ms | 0 |
| 13:45 | 0 | 0.0 | 1040 ms | 0 |
| 14:00 | 0 | 0.0 | 789 ms | 0 |
| 14:15 | 0 | 0.0 | 1226 ms | 0 |
| 14:30 | 0 | 0.0 | 806 ms | 0 |
| 14:45 | 0 | 0.0 | 996 ms | 0 |
| 15:00 | 0 | 0.0 | 723 ms | 0 |
| 15:15 | 0 | 0.0 | 945 ms | 0 |
| 15:30 | 0 | 0.0 | 769 ms | 0 |
| 15:45 | 0 | 0.0 | 906 ms | 0 |
| 16:00 | 0 | 0.0 | 817 ms | 0 |
| 16:15 | 0 | 0.0 | 1210 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Temporal yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Temporal goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Temporal alerts to Slack, Discord or a webhook — free.
Something is off: the vendor reports a minor incident. Official status: Partially Degraded Service
If Temporal is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Temporal's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.