User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
centralcsp.com · 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 38 min ago. Last stored result reached it in 1200 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 941 ms | 0 |
| Mon 18 | 0 | 0.0 | 875 ms | 0 |
| Mon 20 | 0 | 0.0 | 1206 ms | 0 |
| Mon 22 | 0 | 0.0 | 1105 ms | 0 |
| Tue 01 | 0 | 0.0 | 940 ms | 0 |
| Tue 03 | 0 | 0.0 | 907 ms | 0 |
| Tue 05 | 0 | 0.0 | 831 ms | 0 |
| Tue 07 | 0 | 0.0 | 1087 ms | 0 |
| Tue 09 | 0 | 0.0 | 1227 ms | 0 |
| Tue 11 | 0 | 0.0 | 1150 ms | 0 |
| Tue 13 | 0 | 0.0 | 1108 ms | 0 |
| Tue 16 | 0 | 0.0 | 1129 ms | 0 |
| Tue 18 | 0 | 0.0 | 1127 ms | 0 |
| Tue 20 | 0 | 0.0 | 1162 ms | 0 |
| Tue 22 | 0 | 0.0 | 1145 ms | 0 |
| Wed 00 | 0 | 0.0 | 1306 ms | 0 |
| Wed 03 | 0 | 0.0 | 1199 ms | 0 |
| Wed 05 | 0 | 0.0 | 1165 ms | 0 |
| Wed 07 | 0 | 0.0 | 1163 ms | 0 |
| Wed 09 | 0 | 0.0 | 1131 ms | 0 |
| Wed 12 | 0 | 0.0 | 1149 ms | 0 |
| Wed 14 | 0 | 0.0 | 1156 ms | 0 |
| Wed 16 | 0 | 0.0 | 1082 ms | 0 |
| Wed 18 | 0 | 0.0 | 1110 ms | 0 |
| Wed 20 | 0 | 0.0 | 1162 ms | 0 |
| Wed 22 | 0 | 0.0 | 1130 ms | 0 |
| Thu 01 | 0 | 0.0 | 486 ms | 0 |
| Thu 03 | 0 | 0.0 | 1158 ms | 0 |
| Thu 05 | 0 | 0.0 | 1287 ms | 0 |
| Thu 07 | 0 | 0.0 | 1058 ms | 0 |
| Thu 09 | 0 | 0.0 | 1077 ms | 0 |
| Thu 11 | 0 | 0.0 | 1045 ms | 0 |
| Thu 13 | 0 | 0.0 | 955 ms | 0 |
| Thu 15 | 0 | 0.0 | 864 ms | 0 |
| Thu 16 | 0 | 0.0 | 984 ms | 0 |
| Thu 19 | 0 | 0.0 | 1068 ms | 0 |
| Thu 21 | 0 | 0.0 | 1036 ms | 0 |
| Thu 22 | 0 | 0.0 | 1125 ms | 0 |
| Fri 01 | 0 | 0.0 | 653 ms | 0 |
| Fri 03 | 0 | 0.0 | 951 ms | 0 |
| Fri 05 | 0 | 0.0 | 841 ms | 0 |
| Fri 07 | 0 | 0.0 | 1099 ms | 0 |
| Fri 09 | 0 | 0.0 | 1186 ms | 0 |
| Fri 11 | 0 | 0.0 | 1063 ms | 0 |
| Fri 13 | 0 | 0.0 | 1076 ms | 0 |
| Fri 15 | 0 | 0.0 | 1159 ms | 0 |
| Fri 17 | 0 | 0.0 | 1156 ms | 0 |
| Fri 18 | 0 | 0.0 | 1200 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for CentralCSP 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 CentralCSP goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CentralCSP alerts to Slack, Discord or a webhook — free.
We track CentralCSP (centralcsp.com) as part of the Cloud & developer group. Monitor Content Security Policy and every client-side threat from real browser traffic. One header, no agent, EU-hosted. Start a free 14-day trial.
CentralCSP publishes an official status page at status.centralcsp.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 1014 ms average, 297–1200 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CentralCSP incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
1014 ms on average over the last 24 hours (297–1200 ms).
Yes, at https://status.centralcsp.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 CentralCSP here at once, the problem is on CentralCSP'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 CentralCSP. 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.