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 516 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 1304 ms | 0 |
| Mon 16 | 0 | 0.0 | 2664 ms | 0 |
| Mon 18 | 0 | 0.0 | 4316 ms | 0 |
| Mon 20 | 0 | 0.0 | 2469 ms | 0 |
| Mon 23 | 0 | 0.0 | 1739 ms | 0 |
| Tue 01 | 0 | 0.0 | 1056 ms | 0 |
| Tue 03 | 0 | 0.0 | 1433 ms | 0 |
| Tue 05 | 0 | 0.0 | 3179 ms | 0 |
| Tue 07 | 0 | 0.0 | 1492 ms | 0 |
| Tue 09 | 0 | 0.0 | 766 ms | 0 |
| Tue 11 | 0 | 0.0 | 233 ms | 0 |
| Tue 14 | 0 | 0.0 | 3167 ms | 0 |
| Tue 16 | 0 | 0.0 | 1033 ms | 0 |
| Tue 18 | 0 | 0.0 | 1518 ms | 0 |
| Tue 20 | 0 | 0.0 | 1575 ms | 0 |
| Tue 23 | 0 | 0.0 | 1466 ms | 0 |
| Wed 01 | 0 | 0.0 | 223 ms | 0 |
| Wed 03 | 0 | 0.0 | 448 ms | 0 |
| Wed 05 | 0 | 0.0 | 1416 ms | 0 |
| Wed 08 | 0 | 0.0 | 1301 ms | 0 |
| Wed 10 | 0 | 0.0 | 1579 ms | 0 |
| Wed 12 | 0 | 0.0 | 936 ms | 0 |
| Wed 14 | 0 | 0.0 | 1151 ms | 0 |
| Wed 16 | 0 | 0.0 | 124 ms | 0 |
| Wed 18 | 0 | 0.0 | 217 ms | 0 |
| Wed 21 | 0 | 0.0 | 709 ms | 0 |
| Wed 23 | 0 | 0.0 | 163 ms | 0 |
| Thu 01 | 0 | 0.0 | 1980 ms | 0 |
| Thu 03 | 0 | 0.0 | 172 ms | 0 |
| Thu 05 | 0 | 0.0 | 2634 ms | 0 |
| Thu 07 | 0 | 0.0 | 597 ms | 0 |
| Thu 09 | 0 | 0.0 | 3379 ms | 0 |
| Thu 11 | 0 | 0.0 | 824 ms | 0 |
| Thu 13 | 0 | 0.0 | 2275 ms | 0 |
| Thu 15 | 0 | 0.0 | 1576 ms | 0 |
| Thu 18 | 0 | 0.0 | 513 ms | 0 |
| Thu 20 | 0 | 0.0 | 322 ms | 0 |
| Thu 22 | 0 | 0.0 | 1225 ms | 0 |
| Fri 00 | 0 | 0.0 | 1895 ms | 0 |
| Fri 02 | 0 | 0.0 | 311 ms | 0 |
| Fri 04 | 0 | 0.0 | 156 ms | 0 |
| Fri 06 | 0 | 0.0 | 1160 ms | 0 |
| Fri 08 | 0 | 0.0 | 719 ms | 0 |
| Fri 10 | 0 | 0.0 | 300 ms | 0 |
| Fri 11 | 0 | 0.0 | 128 ms | 0 |
| Fri 12 | 0 | 0.0 | 2056 ms | 0 |
| Fri 14 | 0 | 0.0 | 1144 ms | 0 |
| Fri 15 | 0 | 0.0 | 516 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 Zed 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 Zed goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Zed alerts to Slack, Discord or a webhook — free.
Zed is listed in our Cloud & developer category and checked at zed.dev. Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Zed publishes an official status page at status.zed.dev; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 797 ms average, 128–2056 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 Zed incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
797 ms on average over the last 24 hours (128–2056 ms).
Yes, at https://status.zed.dev.
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 Zed here at once, the problem is on Zed'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 Zed. 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.