User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
obsidiansecurity.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 151 ms · 7 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 160 ms | 0 |
| 03:15 | 0 | 0.0 | 60 ms | 0 |
| 03:30 | 0 | 0.0 | 183 ms | 0 |
| 03:45 | 0 | 0.0 | 318 ms | 0 |
| 04:00 | 0 | 0.0 | 327 ms | 0 |
| 04:15 | 0 | 0.0 | 143 ms | 0 |
| 04:30 | 0 | 0.0 | 150 ms | 0 |
| 04:45 | 0 | 0.0 | 403 ms | 0 |
| 05:00 | 0 | 0.0 | 177 ms | 0 |
| 05:15 | 0 | 0.0 | 134 ms | 0 |
| 05:30 | 0 | 0.0 | 130 ms | 0 |
| 05:45 | 0 | 0.0 | 121 ms | 0 |
| 06:00 | 0 | 0.0 | 137 ms | 0 |
| 06:15 | 0 | 0.0 | 214 ms | 0 |
| 06:30 | 0 | 0.0 | 252 ms | 0 |
| 06:45 | 0 | 0.0 | 158 ms | 0 |
| 07:00 | 0 | 0.0 | 168 ms | 0 |
| 07:15 | 0 | 0.0 | 213 ms | 0 |
| 07:30 | 0 | 0.0 | 231 ms | 0 |
| 07:45 | 0 | 0.0 | 165 ms | 0 |
| 08:00 | 0 | 0.0 | 153 ms | 0 |
| 08:15 | 0 | 0.0 | 156 ms | 0 |
| 08:30 | 0 | 0.0 | 277 ms | 0 |
| 08:45 | 0 | 0.0 | 174 ms | 0 |
| 09:00 | 0 | 0.0 | 201 ms | 0 |
| 09:15 | 0 | 0.0 | 88 ms | 0 |
| 09:30 | 0 | 0.0 | 155 ms | 0 |
| 09:45 | 0 | 0.0 | 222 ms | 0 |
| 10:00 | 0 | 0.0 | 257 ms | 0 |
| 10:15 | 0 | 0.0 | 121 ms | 0 |
| 10:30 | 0 | 0.0 | 304 ms | 0 |
| 10:45 | 0 | 0.0 | 174 ms | 0 |
| 11:00 | 0 | 0.0 | 249 ms | 0 |
| 11:15 | 0 | 0.0 | 140 ms | 0 |
| 11:30 | 0 | 0.0 | 253 ms | 0 |
| 11:45 | 0 | 0.0 | 453 ms | 0 |
| 12:00 | 0 | 0.0 | 180 ms | 0 |
| 12:15 | 0 | 0.0 | 199 ms | 0 |
| 12:30 | 0 | 0.0 | 162 ms | 0 |
| 12:45 | 0 | 0.0 | 295 ms | 0 |
| 13:00 | 0 | 0.0 | 96 ms | 0 |
| 13:15 | 0 | 0.0 | 192 ms | 0 |
| 13:30 | 0 | 0.0 | 151 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Obsidian Security 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 Obsidian Security goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Obsidian Security alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Obsidian Security is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Obsidian Security's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.