User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 1 hr ago. Last stored result reached it in 300 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 11 | 0 | 0.0 | 386 ms | 0 |
| Mon 13 | 0 | 0.0 | 334 ms | 0 |
| Mon 16 | 0 | 0.0 | 299 ms | 0 |
| Mon 18 | 0 | 0.0 | 361 ms | 0 |
| Mon 20 | 0 | 0.0 | 223 ms | 0 |
| Mon 22 | 0 | 0.0 | 320 ms | 0 |
| Tue 00 | 0 | 0.0 | 298 ms | 0 |
| Tue 02 | 0 | 0.0 | 274 ms | 0 |
| Tue 04 | 0 | 0.0 | 284 ms | 0 |
| Tue 06 | 0 | 0.0 | 246 ms | 0 |
| Tue 08 | 0 | 0.0 | 350 ms | 0 |
| Tue 11 | 0 | 0.0 | 231 ms | 0 |
| Tue 13 | 0 | 0.0 | 324 ms | 0 |
| Tue 15 | 0 | 0.0 | 290 ms | 0 |
| Tue 17 | 0 | 0.0 | 252 ms | 0 |
| Tue 20 | 0 | 0.0 | 426 ms | 0 |
| Tue 22 | 0 | 0.0 | 288 ms | 0 |
| Wed 00 | 0 | 0.0 | 408 ms | 0 |
| Wed 02 | 0 | 0.0 | 398 ms | 0 |
| Wed 05 | 0 | 0.0 | 214 ms | 0 |
| Wed 07 | 0 | 0.0 | 354 ms | 0 |
| Wed 09 | 0 | 0.0 | 287 ms | 0 |
| Wed 11 | 0 | 0.0 | 356 ms | 0 |
| Wed 13 | 0 | 0.0 | 234 ms | 0 |
| Wed 15 | 0 | 0.0 | 335 ms | 0 |
| Wed 18 | 0 | 0.0 | 334 ms | 0 |
| Wed 20 | 0 | 0.0 | 341 ms | 0 |
| Wed 22 | 0 | 0.0 | 287 ms | 0 |
| Thu 00 | 0 | 0.0 | 292 ms | 0 |
| Thu 02 | 0 | 0.0 | 301 ms | 0 |
| Thu 04 | 0 | 0.0 | 355 ms | 0 |
| Thu 06 | 0 | 0.0 | 244 ms | 0 |
| Thu 09 | 0 | 0.0 | 315 ms | 0 |
| Thu 11 | 0 | 0.0 | 312 ms | 0 |
| Thu 13 | 0 | 0.0 | 280 ms | 0 |
| Thu 15 | 0 | 0.0 | 245 ms | 0 |
| Thu 17 | 0 | 0.0 | 373 ms | 0 |
| Thu 19 | 0 | 0.0 | 330 ms | 0 |
| Thu 21 | 0 | 0.0 | 247 ms | 0 |
| Thu 23 | 0 | 0.0 | 254 ms | 0 |
| Fri 01 | 0 | 0.0 | 260 ms | 0 |
| Fri 03 | 0 | 0.0 | 279 ms | 0 |
| Fri 05 | 0 | 0.0 | 234 ms | 0 |
| Fri 07 | 0 | 0.0 | 217 ms | 0 |
| Fri 09 | 0 | 0.0 | 237 ms | 0 |
| Fri 11 | 0 | 0.0 | 275 ms | 0 |
| Fri 12 | 0 | 0.0 | 293 ms | 0 |
| Fri 14 | 0 | 0.0 | 300 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Opal 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 Opal goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Opal alerts to Slack, Discord or a webhook — free.
We track Opal (opal.dev) as part of the AI group. Opal is the access control plane for every identity. Our AI understands the CISO's context with a security engineer's precision.
Opal publishes an official status page at status.opal.dev; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 272 ms average, 217–373 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Opal incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
272 ms on average over the last 24 hours (217–373 ms).
Yes, at https://status.opal.dev.
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 Opal here at once, the problem is on Opal'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 Opal. 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.