User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 69 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 69 ms | 0 |
| Mon 22 | 0 | 0.0 | 26 ms | 0 |
| Tue 00 | 0 | 0.0 | 40 ms | 0 |
| Tue 02 | 0 | 0.0 | 51 ms | 0 |
| Tue 04 | 0 | 0.0 | 74 ms | 0 |
| Tue 06 | 0 | 0.0 | 31 ms | 0 |
| Tue 08 | 0 | 0.0 | 38 ms | 0 |
| Tue 11 | 0 | 0.0 | 49 ms | 0 |
| Tue 13 | 0 | 0.0 | 103 ms | 0 |
| Tue 15 | 0 | 0.0 | 42 ms | 0 |
| Tue 17 | 0 | 0.0 | 60 ms | 0 |
| Tue 20 | 0 | 0.0 | 191 ms | 0 |
| Tue 22 | 0 | 0.0 | 120 ms | 0 |
| Wed 00 | 0 | 0.0 | 71 ms | 0 |
| Wed 02 | 0 | 0.0 | 49 ms | 0 |
| Wed 05 | 0 | 0.0 | 49 ms | 0 |
| Wed 07 | 0 | 0.0 | 73 ms | 0 |
| Wed 09 | 0 | 0.0 | 68 ms | 0 |
| Wed 11 | 0 | 0.0 | 96 ms | 0 |
| Wed 13 | 0 | 0.0 | 71 ms | 0 |
| Wed 16 | 0 | 0.0 | 93 ms | 0 |
| Wed 17 | 0 | 0.0 | 118 ms | 0 |
| Wed 19 | 0 | 0.0 | 71 ms | 0 |
| Wed 21 | 0 | 0.0 | 175 ms | 0 |
| Thu 00 | 0 | 0.0 | 31 ms | 0 |
| Thu 02 | 0 | 0.0 | 124 ms | 0 |
| Thu 04 | 0 | 0.0 | 72 ms | 0 |
| Thu 06 | 0 | 0.0 | 86 ms | 0 |
| Thu 08 | 0 | 0.0 | 44 ms | 0 |
| Thu 10 | 0 | 0.0 | 65 ms | 0 |
| Thu 12 | 0 | 0.0 | 76 ms | 0 |
| Thu 14 | 0 | 0.0 | 162 ms | 0 |
| Thu 16 | 0 | 0.0 | 230 ms | 0 |
| Thu 18 | 0 | 0.0 | 101 ms | 0 |
| Thu 20 | 0 | 0.0 | 28 ms | 0 |
| Thu 22 | 0 | 0.0 | 43 ms | 0 |
| Fri 01 | 0 | 0.0 | 34 ms | 0 |
| Fri 03 | 0 | 0.0 | 86 ms | 0 |
| Fri 05 | 0 | 0.0 | 59 ms | 0 |
| Fri 06 | 0 | 0.0 | 95 ms | 0 |
| Fri 08 | 0 | 0.0 | 46 ms | 0 |
| Fri 10 | 0 | 0.0 | 37 ms | 0 |
| Fri 11 | 0 | 0.0 | 42 ms | 0 |
| Fri 12 | 0 | 0.0 | 43 ms | 0 |
| Fri 14 | 0 | 0.0 | 98 ms | 0 |
| Fri 17 | 0 | 0.0 | 72 ms | 0 |
| Fri 18 | 0 | 0.0 | 123 ms | 0 |
| Fri 20 | 0 | 0.0 | 69 ms | 0 |
100% 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Tatum 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 Tatum goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Tatum alerts to Slack, Discord or a webhook — free.
Tatum is listed in our Cloud & developer category and checked at tatum.io. Tatum makes blockchain development simple. It’s the go-to blockchain development platform with a unified framework for building Web3 apps using any of the 100+ protocols.
Tatum publishes an official status page at status.tatum.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 66 ms average, 34–123 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Tatum incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
66 ms on average over the last 24 hours (34–123 ms).
Yes, at https://status.tatum.io.
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 Tatum here at once, the problem is on Tatum'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 Tatum. 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.