User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
sucuri.net · Productivity
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 451 ms · 2 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:30 | 0 | 0.0 | 483 ms | 0 |
| 03:45 | 0 | 0.0 | 927 ms | 0 |
| 04:00 | 0 | 0.0 | 431 ms | 0 |
| 04:15 | 0 | 0.0 | 670 ms | 0 |
| 04:30 | 0 | 0.0 | 390 ms | 0 |
| 04:45 | 0 | 0.0 | 239 ms | 0 |
| 05:00 | 0 | 0.0 | 899 ms | 0 |
| 05:15 | 0 | 0.0 | 500 ms | 0 |
| 05:30 | 0 | 0.0 | 551 ms | 0 |
| 05:45 | 0 | 0.0 | 458 ms | 0 |
| 06:00 | 0 | 0.0 | 40 ms | 0 |
| 06:15 | 0 | 0.0 | 417 ms | 0 |
| 06:30 | 0 | 0.0 | 237 ms | 0 |
| 06:45 | 0 | 0.0 | 295 ms | 0 |
| 07:00 | 0 | 0.0 | 685 ms | 0 |
| 07:15 | 0 | 0.0 | 325 ms | 0 |
| 07:30 | 0 | 0.0 | 973 ms | 0 |
| 07:45 | 0 | 0.0 | 174 ms | 0 |
| 08:00 | 0 | 0.0 | 276 ms | 0 |
| 08:15 | 0 | 0.0 | 419 ms | 0 |
| 08:30 | 0 | 0.0 | 311 ms | 0 |
| 08:45 | 0 | 0.0 | 398 ms | 0 |
| 09:00 | 0 | 0.0 | 523 ms | 0 |
| 09:15 | 0 | 0.0 | 559 ms | 0 |
| 09:30 | 0 | 0.0 | 613 ms | 0 |
| 09:45 | 0 | 0.0 | 18 ms | 0 |
| 10:00 | 0 | 0.0 | 510 ms | 0 |
| 10:15 | 0 | 0.0 | 258 ms | 0 |
| 10:30 | 0 | 0.0 | 44 ms | 0 |
| 10:45 | 0 | 0.0 | 1165 ms | 0 |
| 11:00 | 0 | 0.0 | 291 ms | 0 |
| 11:15 | 0 | 0.0 | 872 ms | 0 |
| 11:30 | 0 | 0.0 | 519 ms | 0 |
| 11:45 | 0 | 0.0 | 132 ms | 0 |
| 12:00 | 0 | 0.0 | 540 ms | 0 |
| 12:15 | 0 | 0.0 | 495 ms | 0 |
| 12:30 | 0 | 0.0 | 386 ms | 0 |
| 12:45 | 0 | 0.0 | 156 ms | 0 |
| 13:00 | 0 | 0.0 | 484 ms | 0 |
| 13:15 | 0 | 0.0 | 155 ms | 0 |
| 13:30 | 0 | 0.0 | 324 ms | 0 |
| 13:45 | 0 | 0.0 | 510 ms | 0 |
| 14:00 | 0 | 0.0 | 171 ms | 0 |
| 14:15 | 0 | 0.0 | 936 ms | 0 |
| 14:30 | 0 | 0.0 | 331 ms | 0 |
| 14:45 | 0 | 0.0 | 374 ms | 0 |
| 15:00 | 0 | 0.0 | 820 ms | 0 |
| 15:15 | 0 | 0.0 | 294 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 Sucuri 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 Sucuri goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sucuri 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 Sucuri 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 Sucuri'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.