User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Zight 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 → zight.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 80 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 |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 119 ms | 0 |
| Mon 18 | 0 | 0.0 | 125 ms | 0 |
| Mon 20 | 0 | 0.0 | 124 ms | 0 |
| Mon 22 | 0 | 0.0 | 164 ms | 0 |
| Tue 01 | 0 | 0.0 | 81 ms | 0 |
| Tue 03 | 0 | 0.0 | 29 ms | 0 |
| Tue 05 | 0 | 0.0 | 208 ms | 0 |
| Tue 07 | 0 | 0.0 | 57 ms | 0 |
| Tue 09 | 0 | 0.0 | 101 ms | 0 |
| Tue 11 | 0 | 0.0 | 130 ms | 0 |
| Tue 13 | 0 | 0.0 | 61 ms | 0 |
| Tue 16 | 0 | 0.0 | 221 ms | 0 |
| Tue 18 | 0 | 0.0 | 63 ms | 0 |
| Tue 20 | 0 | 0.0 | 82 ms | 0 |
| Tue 22 | 0 | 0.0 | 74 ms | 0 |
| Wed 01 | 0 | 0.0 | 79 ms | 0 |
| Wed 03 | 0 | 0.0 | 67 ms | 0 |
| Wed 05 | 0 | 0.0 | 63 ms | 0 |
| Wed 07 | 0 | 0.0 | 75 ms | 0 |
| Wed 10 | 0 | 0.0 | 110 ms | 0 |
| Wed 12 | 0 | 0.0 | 157 ms | 0 |
| Wed 14 | 0 | 0.0 | 50 ms | 0 |
| Wed 16 | 0 | 0.0 | 61 ms | 0 |
| Wed 18 | 0 | 0.0 | 57 ms | 0 |
| Wed 20 | 0 | 0.0 | 63 ms | 0 |
| Wed 23 | 0 | 0.0 | 127 ms | 0 |
| Thu 01 | 0 | 0.0 | 111 ms | 0 |
| Thu 03 | 0 | 0.0 | 308 ms | 0 |
| Thu 05 | 0 | 0.0 | 243 ms | 0 |
| Thu 07 | 0 | 0.0 | 116 ms | 0 |
| Thu 09 | 0 | 0.0 | 94 ms | 0 |
| Thu 11 | 0 | 0.0 | 109 ms | 0 |
| Thu 13 | 0 | 0.0 | 58 ms | 0 |
| Thu 15 | 0 | 0.0 | 119 ms | 0 |
| Thu 17 | 0 | 0.0 | 92 ms | 0 |
| Thu 19 | 0 | 0.0 | 47 ms | 0 |
| Thu 22 | 0 | 0.0 | 547 ms | 0 |
| Fri 00 | 0 | 0.0 | 190 ms | 0 |
| Fri 02 | 0 | 0.0 | 76 ms | 0 |
| Fri 04 | 0 | 0.0 | 63 ms | 0 |
| Fri 06 | 0 | 0.0 | 74 ms | 0 |
| Fri 08 | 0 | 0.0 | 128 ms | 0 |
| Fri 10 | 0 | 0.0 | 36 ms | 0 |
| Fri 12 | 0 | 0.0 | 131 ms | 0 |
| Fri 14 | 0 | 0.0 | 93 ms | 0 |
| Fri 16 | 0 | 0.0 | 106 ms | 0 |
| Fri 17 | 0 | 0.0 | 87 ms | 0 |
| Fri 18 | 0 | 0.0 | 80 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Zight 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 Zight yet. Outages of 10 minutes or more get their own page here.
Having trouble with Zight?
One report per service every 10 minutes from this network. No account.
Follow Zight
Get an email when Zight goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Zight alerts to Slack, Discord or a webhook — free.
About Zight
Zight is listed in our AI category and checked at zight.com. Zight captures what's on your screen and turns it into a video, a screenshot, or an AI guide your team can act on, shared instantly with a secure link.
Zight publishes an official status page at status.zight.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 121 ms average, 32–547 ms range across 14 successful checks.
Questions
Is Zight down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Zight last down?
We have not recorded a public Zight incident since monitoring began 8 days ago.
What is Zight's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Zight respond?
121 ms on average over the last 24 hours (32–547 ms).
Does Zight have an official status page?
Yes, at https://status.zight.com.
Zight 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Zight here at once, the problem is on Zight'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 Zight. 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.