User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Scanner 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 → scanner.dev—
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 62 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 12 | 0 | 0.0 | 181 ms | 0 |
| Mon 14 | 0 | 0.0 | 191 ms | 0 |
| Mon 16 | 0 | 0.0 | 852 ms | 0 |
| Mon 18 | 0 | 0.0 | 133 ms | 0 |
| Mon 20 | 0 | 0.0 | 257 ms | 0 |
| Mon 22 | 0 | 0.0 | 223 ms | 0 |
| Tue 00 | 0 | 0.0 | 252 ms | 0 |
| Tue 02 | 0 | 0.0 | 152 ms | 0 |
| Tue 04 | 0 | 0.0 | 213 ms | 0 |
| Tue 07 | 0 | 0.0 | 177 ms | 0 |
| Tue 09 | 0 | 0.0 | 185 ms | 0 |
| Tue 11 | 0 | 0.0 | 155 ms | 0 |
| Tue 13 | 0 | 0.0 | 167 ms | 0 |
| Tue 15 | 0 | 0.0 | 220 ms | 0 |
| Tue 17 | 0 | 0.0 | 170 ms | 0 |
| Tue 20 | 0 | 0.0 | 183 ms | 0 |
| Tue 22 | 0 | 0.0 | 164 ms | 0 |
| Wed 00 | 0 | 0.0 | 252 ms | 0 |
| Wed 02 | 0 | 0.0 | 247 ms | 0 |
| Wed 05 | 0 | 0.0 | 185 ms | 0 |
| Wed 07 | 0 | 0.0 | 154 ms | 0 |
| Wed 09 | 0 | 0.0 | 121 ms | 0 |
| Wed 12 | 0 | 0.0 | 177 ms | 0 |
| Wed 14 | 0 | 0.0 | 127 ms | 0 |
| Wed 16 | 0 | 0.0 | 190 ms | 0 |
| Wed 18 | 0 | 0.0 | 199 ms | 0 |
| Wed 20 | 0 | 0.0 | 246 ms | 0 |
| Wed 22 | 0 | 0.0 | 180 ms | 0 |
| Thu 00 | 0 | 0.0 | 210 ms | 0 |
| Thu 03 | 0 | 0.0 | 215 ms | 0 |
| Thu 05 | 0 | 0.0 | 191 ms | 0 |
| Thu 07 | 0 | 0.0 | 221 ms | 0 |
| Thu 09 | 0 | 0.0 | 261 ms | 0 |
| Thu 11 | 0 | 0.0 | 200 ms | 0 |
| Thu 13 | 0 | 0.0 | 106 ms | 0 |
| Thu 15 | 0 | 0.0 | 160 ms | 0 |
| Thu 17 | 0 | 0.0 | 258 ms | 0 |
| Thu 19 | 0 | 0.0 | 267 ms | 0 |
| Thu 21 | 0 | 0.0 | 182 ms | 0 |
| Thu 23 | 0 | 0.0 | 135 ms | 0 |
| Fri 01 | 0 | 0.0 | 245 ms | 0 |
| Fri 03 | 0 | 0.0 | 191 ms | 0 |
| Fri 05 | 0 | 0.0 | 198 ms | 0 |
| Fri 08 | 0 | 0.0 | 169 ms | 0 |
| Fri 10 | 0 | 0.0 | 159 ms | 0 |
| Fri 12 | 0 | 0.0 | 179 ms | 0 |
| Fri 14 | 0 | 0.0 | 134 ms | 0 |
| Fri 16 | 0 | 0.0 | 141 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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Scanner 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 Scanner yet. Outages of 10 minutes or more get their own page here.
Having trouble with Scanner?
One report per service every 10 minutes from this network. No account.
Follow Scanner
Get an email when Scanner goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Scanner alerts to Slack, Discord or a webhook — free.
About Scanner
We track Scanner (scanner.dev) as part of the AI group. The security data lake platform built for AI agents and modern security teams. Search and detect across petabytes in seconds. Retain everything forever. Power the next generation of detection & response.
Scanner publishes an official status page at status.scanner.dev; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 184 ms average, 62–267 ms range across 14 successful checks.
Questions
Is Scanner down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Scanner last down?
We have not recorded a public Scanner incident since monitoring began 7 days ago.
What is Scanner's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Scanner respond?
184 ms on average over the last 24 hours (62–267 ms).
Does Scanner have an official status page?
Yes, at https://status.scanner.dev.
Scanner 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 Scanner here at once, the problem is on Scanner'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 Scanner. 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.