User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
catalystcloud.nz · Cloud & developer
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 3057 ms · 4 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:30 | 0 | 0.0 | 3443 ms | 0 |
| 03:45 | 0 | 0.0 | 4566 ms | 0 |
| 04:00 | 0 | 0.0 | 3751 ms | 0 |
| 04:15 | 0 | 0.0 | 2267 ms | 0 |
| 04:30 | 0 | 0.0 | 3777 ms | 0 |
| 04:45 | 0 | 0.0 | 4809 ms | 0 |
| 05:00 | 0 | 0.0 | 3758 ms | 0 |
| 05:15 | 0 | 0.0 | 4193 ms | 0 |
| 05:30 | 0 | 0.0 | 3556 ms | 0 |
| 05:45 | 0 | 0.0 | 2842 ms | 0 |
| 06:00 | 0 | 0.0 | 3991 ms | 0 |
| 06:15 | 0 | 0.0 | 3324 ms | 0 |
| 06:30 | 0 | 0.0 | 3569 ms | 0 |
| 06:45 | 0 | 0.0 | 3723 ms | 0 |
| 07:00 | 0 | 0.0 | 4242 ms | 0 |
| 07:15 | 0 | 0.0 | 3550 ms | 0 |
| 07:30 | 0 | 0.0 | 3292 ms | 0 |
| 07:45 | 0 | 0.0 | 3811 ms | 0 |
| 08:00 | 0 | 0.0 | 4452 ms | 0 |
| 08:15 | 0 | 0.0 | 3631 ms | 0 |
| 08:30 | 0 | 0.0 | 3479 ms | 0 |
| 08:45 | 0 | 0.0 | 4510 ms | 0 |
| 09:00 | 0 | 0.0 | 4394 ms | 0 |
| 09:15 | 0 | 0.0 | 2612 ms | 0 |
| 09:30 | 0 | 0.0 | 3043 ms | 0 |
| 09:45 | 0 | 0.0 | 4637 ms | 0 |
| 10:00 | 0 | 0.0 | 3957 ms | 0 |
| 10:15 | 0 | 0.0 | 4616 ms | 0 |
| 10:30 | 0 | 0.0 | 3480 ms | 0 |
| 10:45 | 0 | 0.0 | 3337 ms | 0 |
| 11:00 | 0 | 0.0 | 2945 ms | 0 |
| 11:15 | 0 | 0.0 | 3791 ms | 0 |
| 11:30 | 0 | 0.0 | 4047 ms | 0 |
| 11:45 | 0 | 0.0 | 3051 ms | 0 |
| 12:00 | 0 | 0.0 | 3698 ms | 0 |
| 12:15 | 0 | 0.0 | 4224 ms | 0 |
| 12:30 | 0 | 0.0 | 1164 ms | 0 |
| 12:45 | 0 | 0.0 | 2962 ms | 0 |
| 13:00 | 0 | 0.0 | 3064 ms | 0 |
| 13:15 | 0 | 0.0 | 5974 ms | 0 |
| 13:30 | 0 | 0.0 | 3132 ms | 0 |
| 13:45 | 0 | 0.0 | 3532 ms | 0 |
| 14:00 | 0 | 0.0 | 3269 ms | 0 |
| 14:15 | 0 | 0.0 | 3882 ms | 0 |
| 14:30 | 0 | 0.0 | 3912 ms | 0 |
| 14:45 | 0 | 0.0 | 5161 ms | 0 |
| 15:00 | 0 | 0.0 | 3674 ms | 0 |
| 15:15 | 0 | 0.0 | 3057 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 Catalyst Cloud 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 Catalyst Cloud goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Catalyst Cloud 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 Catalyst Cloud 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 Catalyst Cloud'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.