User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is SuperOps 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 → superops.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 48 min ago. Last stored result reached it in 106 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 226 ms | 0 |
| Mon 15 | 0 | 0.0 | 85 ms | 0 |
| Mon 17 | 0 | 0.0 | 178 ms | 0 |
| Mon 19 | 0 | 0.0 | 219 ms | 0 |
| Mon 21 | 0 | 0.0 | 67 ms | 0 |
| Mon 23 | 0 | 0.0 | 109 ms | 0 |
| Tue 01 | 0 | 0.0 | 167 ms | 0 |
| Tue 03 | 0 | 0.0 | 80 ms | 0 |
| Tue 06 | 0 | 0.0 | 290 ms | 0 |
| Tue 08 | 0 | 0.0 | 173 ms | 0 |
| Tue 10 | 0 | 0.0 | 280 ms | 0 |
| Tue 12 | 0 | 0.0 | 539 ms | 0 |
| Tue 14 | 0 | 0.0 | 95 ms | 0 |
| Tue 16 | 0 | 0.0 | 162 ms | 0 |
| Tue 19 | 0 | 0.0 | 232 ms | 0 |
| Tue 21 | 0 | 0.0 | 82 ms | 0 |
| Tue 23 | 0 | 0.0 | 232 ms | 0 |
| Wed 01 | 0 | 0.0 | 199 ms | 0 |
| Wed 04 | 0 | 0.0 | 75 ms | 0 |
| Wed 06 | 0 | 0.0 | 348 ms | 0 |
| Wed 08 | 0 | 0.0 | 211 ms | 0 |
| Wed 10 | 0 | 0.0 | 117 ms | 0 |
| Wed 13 | 0 | 0.0 | 202 ms | 0 |
| Wed 15 | 0 | 0.0 | 165 ms | 0 |
| Wed 17 | 0 | 0.0 | 156 ms | 0 |
| Wed 19 | 0 | 0.0 | 177 ms | 0 |
| Wed 21 | 0 | 0.0 | 191 ms | 0 |
| Wed 23 | 0 | 0.0 | 96 ms | 0 |
| Thu 02 | 0 | 0.0 | 212 ms | 0 |
| Thu 04 | 0 | 0.0 | 260 ms | 0 |
| Thu 06 | 0 | 0.0 | 140 ms | 0 |
| Thu 08 | 0 | 0.0 | 157 ms | 0 |
| Thu 10 | 0 | 0.0 | 165 ms | 0 |
| Thu 12 | 0 | 0.0 | 157 ms | 0 |
| Thu 14 | 0 | 0.0 | 157 ms | 0 |
| Thu 16 | 0 | 0.0 | 377 ms | 0 |
| Thu 18 | 0 | 0.0 | 262 ms | 0 |
| Thu 20 | 0 | 0.0 | 135 ms | 0 |
| Thu 22 | 0 | 0.0 | 101 ms | 0 |
| Fri 00 | 0 | 0.0 | 81 ms | 0 |
| Fri 02 | 0 | 0.0 | 85 ms | 0 |
| Fri 05 | 0 | 0.0 | 228 ms | 0 |
| Fri 07 | 0 | 0.0 | 107 ms | 0 |
| Fri 09 | 0 | 0.0 | 86 ms | 0 |
| Fri 10 | 0 | 0.0 | 115 ms | 0 |
| Fri 12 | 0 | 0.0 | 90 ms | 0 |
| Fri 14 | 0 | 0.0 | 142 ms | 0 |
| Fri 16 | 0 | 0.0 | 106 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 SuperOps 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 SuperOps yet. Outages of 10 minutes or more get their own page here.
Having trouble with SuperOps?
One report per service every 10 minutes from this network. No account.
Follow SuperOps
Get an email when SuperOps goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SuperOps alerts to Slack, Discord or a webhook — free.
About SuperOps
We track SuperOps (superops.com) as part of the AI group. SuperOps is the autonomous endpoint management platform for IT teams and MSPs. AI agents patch, fix and secure every device under your controls.
SuperOps publishes an official status page at status.superops.com; 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: 128 ms average, 81–262 ms range across 12 successful checks.
Questions
Is SuperOps down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was SuperOps last down?
We have not recorded a public SuperOps incident since monitoring began 7 days ago.
What is SuperOps's uptime?
From our own checks: 100% over 7 days of checks.
How fast does SuperOps respond?
128 ms on average over the last 24 hours (81–262 ms).
Does SuperOps have an official status page?
Yes, at https://status.superops.com.
SuperOps 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 SuperOps here at once, the problem is on SuperOps'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 SuperOps. 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.