User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 2 hr ago. Last stored result reached it in 173 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 58 ms | 0 |
| Mon 22 | 0 | 0.0 | 142 ms | 0 |
| Tue 01 | 0 | 0.0 | 97 ms | 0 |
| Tue 03 | 0 | 0.0 | 39 ms | 0 |
| Tue 05 | 0 | 0.0 | 101 ms | 0 |
| Tue 07 | 0 | 0.0 | 103 ms | 0 |
| Tue 09 | 0 | 0.0 | 103 ms | 0 |
| Tue 11 | 0 | 0.0 | 153 ms | 0 |
| Tue 13 | 0 | 0.0 | 94 ms | 0 |
| Tue 16 | 0 | 0.0 | 89 ms | 0 |
| Tue 18 | 0 | 0.0 | 62 ms | 0 |
| Tue 20 | 0 | 0.0 | 96 ms | 0 |
| Tue 22 | 0 | 0.0 | 165 ms | 0 |
| Wed 00 | 0 | 0.0 | 132 ms | 0 |
| Wed 03 | 0 | 0.0 | 134 ms | 0 |
| Wed 05 | 0 | 0.0 | 214 ms | 0 |
| Wed 07 | 0 | 0.0 | 55 ms | 0 |
| Wed 09 | 0 | 0.0 | 102 ms | 0 |
| Wed 12 | 0 | 0.0 | 240 ms | 0 |
| Wed 14 | 0 | 0.0 | 157 ms | 0 |
| Wed 16 | 0 | 0.0 | 186 ms | 0 |
| Wed 18 | 0 | 0.0 | 74 ms | 0 |
| Wed 20 | 0 | 0.0 | 146 ms | 0 |
| Wed 22 | 0 | 0.0 | 127 ms | 0 |
| Thu 01 | 0 | 0.0 | 95 ms | 0 |
| Thu 03 | 0 | 0.0 | 175 ms | 0 |
| Thu 05 | 0 | 0.0 | 210 ms | 0 |
| Thu 07 | 0 | 0.0 | 113 ms | 0 |
| Thu 09 | 0 | 0.0 | 170 ms | 0 |
| Thu 11 | 0 | 0.0 | 115 ms | 0 |
| Thu 13 | 0 | 0.0 | 81 ms | 0 |
| Thu 15 | 0 | 0.0 | 86 ms | 0 |
| Thu 17 | 0 | 0.0 | 214 ms | 0 |
| Thu 19 | 0 | 0.0 | 91 ms | 0 |
| Thu 21 | 0 | 0.0 | 102 ms | 0 |
| Thu 23 | 0 | 0.0 | 178 ms | 0 |
| Fri 01 | 0 | 0.0 | 148 ms | 0 |
| Fri 03 | 0 | 0.0 | 194 ms | 0 |
| Fri 06 | 0 | 0.0 | 28 ms | 0 |
| Fri 08 | 0 | 0.0 | 153 ms | 0 |
| Fri 10 | 0 | 0.0 | 167 ms | 0 |
| Fri 12 | 0 | 0.0 | 92 ms | 0 |
| Fri 14 | 0 | 0.0 | 78 ms | 0 |
| Fri 16 | 0 | 0.0 | 115 ms | 0 |
| Fri 17 | 0 | 0.0 | 132 ms | 0 |
| Fri 19 | 0 | 0.0 | 155 ms | 0 |
| Fri 21 | 0 | 0.0 | 84 ms | 0 |
| Fri 22 | 0 | 0.0 | 173 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Cerby 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 Cerby goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cerby alerts to Slack, Discord or a webhook — free.
We track Cerby (cerby.com) as part of the Cloud & developer group. Cerby is the identity automation platform that secures the applications traditional tools leave behind—extending control, security, and compliance everywhere.
Cerby publishes an official status page at status.cerby.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 129 ms average, 28–208 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 Cerby incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
129 ms on average over the last 24 hours (28–208 ms).
Yes, at https://status.cerby.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Cerby here at once, the problem is on Cerby'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 Cerby. 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.