User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
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 91 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 192 ms | 0 |
| Mon 14 | 0 | 0.0 | 74 ms | 0 |
| Mon 17 | 0 | 0.0 | 162 ms | 0 |
| Mon 19 | 0 | 0.0 | 190 ms | 0 |
| Mon 21 | 0 | 0.0 | 249 ms | 0 |
| Mon 23 | 0 | 0.0 | 78 ms | 0 |
| Tue 01 | 0 | 0.0 | 156 ms | 0 |
| Tue 03 | 0 | 0.0 | 140 ms | 0 |
| Tue 05 | 0 | 0.0 | 187 ms | 0 |
| Tue 07 | 0 | 0.0 | 213 ms | 0 |
| Tue 10 | 0 | 0.0 | 193 ms | 0 |
| Tue 12 | 0 | 0.0 | 249 ms | 0 |
| Tue 14 | 0 | 0.0 | 150 ms | 0 |
| Tue 16 | 0 | 0.0 | 177 ms | 0 |
| Tue 18 | 0 | 0.0 | 205 ms | 0 |
| Tue 21 | 0 | 0.0 | 209 ms | 0 |
| Tue 23 | 0 | 0.0 | 201 ms | 0 |
| Wed 01 | 0 | 0.0 | 84 ms | 0 |
| Wed 02 | 0 | 0.0 | 201 ms | 0 |
| Wed 05 | 0 | 0.0 | 75 ms | 0 |
| Wed 07 | 0 | 0.0 | 205 ms | 0 |
| Wed 09 | 0 | 0.0 | 163 ms | 0 |
| Wed 11 | 0 | 0.0 | 176 ms | 0 |
| Wed 13 | 0 | 0.0 | 130 ms | 0 |
| Wed 16 | 0 | 0.0 | 167 ms | 0 |
| Wed 18 | 0 | 0.0 | 127 ms | 0 |
| Wed 20 | 0 | 0.0 | 170 ms | 0 |
| Wed 22 | 0 | 0.0 | 255 ms | 0 |
| Thu 00 | 0 | 0.0 | 163 ms | 0 |
| Thu 02 | 0 | 0.0 | 158 ms | 0 |
| Thu 04 | 0 | 0.0 | 94 ms | 0 |
| Thu 07 | 0 | 0.0 | 193 ms | 0 |
| Thu 09 | 0 | 0.0 | 156 ms | 0 |
| Thu 11 | 0 | 0.0 | 175 ms | 0 |
| Thu 13 | 0 | 0.0 | 201 ms | 0 |
| Thu 15 | 0 | 0.0 | 212 ms | 0 |
| Thu 17 | 0 | 0.0 | 127 ms | 0 |
| Thu 19 | 0 | 0.0 | 164 ms | 0 |
| Thu 21 | 0 | 0.0 | 169 ms | 0 |
| Thu 23 | 0 | 0.0 | 109 ms | 0 |
| Fri 01 | 0 | 0.0 | 181 ms | 0 |
| Fri 03 | 0 | 0.0 | 174 ms | 0 |
| Fri 05 | 0 | 0.0 | 122 ms | 0 |
| Fri 08 | 0 | 0.0 | 167 ms | 0 |
| Fri 10 | 0 | 0.0 | 79 ms | 0 |
| Fri 11 | 0 | 0.0 | 91 ms | 0 |
| Fri 12 | 0 | 0.0 | 215 ms | 0 |
| Fri 14 | 0 | 0.0 | 91 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 Tezos 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 Tezos goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Tezos alerts to Slack, Discord or a webhook — free.
Tezos is listed in our Social category and checked at tezos.com. Tezos is an open-source platform that addresses key barriers facing blockchain adoption for assets and applications, backed by a global community of validators, researchers, and builders.
Tezos publishes an official status page at status.tezos.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with social services: feeds not loading, posts or messages not sending, and login loops.
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: 138 ms average, 63–215 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 Tezos incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
138 ms on average over the last 24 hours (63–215 ms).
Yes, at https://status.tezos.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report Tezos here at once, the problem is on Tezos'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 Tezos. 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.