User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
slab.com · Cloud & developer
The vendor reports a major incident. Our homepage check still succeeds, so the impact may be limited to part of the service. Official status: The vendor reports an active issue
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 169 ms · 2 min ago.
Major incident
The vendor reports an active issue Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:30 | 0 | 0.0 | 81 ms | 0 |
| 03:45 | 0 | 0.0 | 107 ms | 0 |
| 04:00 | 0 | 0.0 | 83 ms | 0 |
| 04:15 | 0 | 0.0 | 134 ms | 0 |
| 04:30 | 0 | 0.0 | 184 ms | 0 |
| 04:45 | 0 | 0.0 | 57 ms | 0 |
| 05:00 | 0 | 0.0 | 71 ms | 0 |
| 05:15 | 0 | 0.0 | 61 ms | 0 |
| 05:30 | 0 | 0.0 | 105 ms | 0 |
| 05:45 | 0 | 0.0 | 79 ms | 0 |
| 06:00 | 0 | 0.0 | 62 ms | 0 |
| 06:15 | 0 | 0.0 | 83 ms | 0 |
| 06:30 | 0 | 0.0 | 96 ms | 0 |
| 06:45 | 0 | 0.0 | 95 ms | 0 |
| 07:00 | 0 | 0.0 | 68 ms | 0 |
| 07:15 | 0 | 0.0 | 124 ms | 0 |
| 07:30 | 0 | 0.0 | 95 ms | 0 |
| 07:45 | 0 | 0.0 | 93 ms | 0 |
| 08:00 | 0 | 0.0 | 72 ms | 0 |
| 08:15 | 0 | 0.0 | 53 ms | 0 |
| 08:30 | 0 | 0.0 | 133 ms | 0 |
| 08:45 | 0 | 0.0 | 98 ms | 0 |
| 09:00 | 0 | 0.0 | 52 ms | 0 |
| 09:15 | 0 | 0.0 | 93 ms | 0 |
| 09:30 | 0 | 0.0 | 127 ms | 0 |
| 09:45 | 0 | 0.0 | 58 ms | 0 |
| 10:00 | 0 | 0.0 | 104 ms | 0 |
| 10:15 | 0 | 0.0 | 153 ms | 0 |
| 10:30 | 0 | 0.0 | 84 ms | 0 |
| 10:45 | 0 | 0.0 | 107 ms | 0 |
| 11:00 | 0 | 0.0 | 106 ms | 0 |
| 11:15 | 0 | 0.0 | 73 ms | 0 |
| 11:30 | 0 | 0.0 | 153 ms | 0 |
| 11:45 | 0 | 0.0 | 79 ms | 0 |
| 12:00 | 0 | 0.0 | 77 ms | 0 |
| 12:15 | 0 | 0.0 | 131 ms | 0 |
| 12:30 | 0 | 0.0 | 183 ms | 0 |
| 12:45 | 0 | 0.0 | 92 ms | 0 |
| 13:00 | 0 | 0.0 | 123 ms | 0 |
| 13:15 | 0 | 0.0 | 104 ms | 0 |
| 13:30 | 0 | 0.0 | 351 ms | 0 |
| 13:45 | 0 | 0.0 | 160 ms | 0 |
| 14:00 | 0 | 0.0 | 107 ms | 0 |
| 14:15 | 0 | 0.0 | 142 ms | 0 |
| 14:30 | 0 | 0.0 | 58 ms | 0 |
| 14:45 | 0 | 0.0 | 192 ms | 0 |
| 15:00 | 0 | 0.0 | 144 ms | 0 |
| 15:15 | 0 | 0.0 | 149 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.
| Started | Peak | Duration | Status | Details |
|---|---|---|---|---|
| 2026-11-02 03:15 UTC | major outage | 12 h 11 min | Ongoing | Details → |
One report per service every 10 minutes from this network. No account.
Get an email when Slab goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Slab alerts to Slack, Discord or a webhook — free.
The vendor reports a major incident. Our homepage check still succeeds, so the impact may be limited to part of the service. Official status: The vendor reports an active issue
If Slab 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 Slab'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.