User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
corsfix.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 39 min ago. Last stored result reached it in 161 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 168 ms | 0 |
| Mon 22 | 0 | 0.0 | 112 ms | 0 |
| Tue 00 | 0 | 0.0 | 137 ms | 0 |
| Tue 02 | 0 | 0.0 | 118 ms | 0 |
| Tue 04 | 0 | 0.0 | 125 ms | 0 |
| Tue 06 | 0 | 0.0 | 217 ms | 0 |
| Tue 08 | 0 | 0.0 | 114 ms | 0 |
| Tue 10 | 0 | 0.0 | 89 ms | 0 |
| Tue 12 | 0 | 0.0 | 112 ms | 0 |
| Tue 15 | 0 | 0.0 | 129 ms | 0 |
| Tue 17 | 0 | 0.0 | 180 ms | 0 |
| Tue 19 | 0 | 0.0 | 360 ms | 0 |
| Tue 21 | 0 | 0.0 | 550 ms | 0 |
| Wed 00 | 0 | 0.0 | 95 ms | 0 |
| Wed 02 | 0 | 0.0 | 307 ms | 0 |
| Wed 04 | 0 | 0.0 | 97 ms | 0 |
| Wed 06 | 0 | 0.0 | 181 ms | 0 |
| Wed 09 | 0 | 0.0 | 103 ms | 0 |
| Wed 11 | 0 | 0.0 | 126 ms | 0 |
| Wed 13 | 0 | 0.0 | 82 ms | 0 |
| Wed 15 | 0 | 0.0 | 110 ms | 0 |
| Wed 17 | 0 | 0.0 | 193 ms | 0 |
| Wed 19 | 0 | 0.0 | 107 ms | 0 |
| Wed 22 | 0 | 0.0 | 230 ms | 0 |
| Thu 00 | 0 | 0.0 | 161 ms | 0 |
| Thu 02 | 0 | 0.0 | 181 ms | 0 |
| Thu 04 | 0 | 0.0 | 158 ms | 0 |
| Thu 06 | 0 | 0.0 | 163 ms | 0 |
| Thu 08 | 0 | 0.0 | 72 ms | 0 |
| Thu 10 | 0 | 0.0 | 111 ms | 0 |
| Thu 12 | 0 | 0.0 | 74 ms | 0 |
| Thu 14 | 0 | 0.0 | 153 ms | 0 |
| Thu 16 | 0 | 0.0 | 165 ms | 0 |
| Thu 18 | 0 | 0.0 | 97 ms | 0 |
| Thu 20 | 0 | 0.0 | 133 ms | 0 |
| Thu 22 | 0 | 0.0 | 126 ms | 0 |
| Fri 00 | 0 | 0.0 | 333 ms | 0 |
| Fri 01 | 0 | 0.0 | 120 ms | 0 |
| Fri 03 | 0 | 0.0 | 79 ms | 0 |
| Fri 05 | 0 | 0.0 | 117 ms | 0 |
| Fri 07 | 0 | 0.0 | 110 ms | 0 |
| Fri 09 | 0 | 0.0 | 78 ms | 0 |
| Fri 11 | 0 | 0.0 | 85 ms | 0 |
| Fri 13 | 0 | 0.0 | 114 ms | 0 |
| Fri 15 | 0 | 0.0 | 100 ms | 0 |
| Fri 17 | 0 | 0.0 | 205 ms | 0 |
| Fri 18 | 0 | 0.0 | 170 ms | 0 |
| Fri 19 | 0 | 0.0 | 161 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 Corsfix 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 Corsfix goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Corsfix alerts to Slack, Discord or a webhook — free.
Corsfix, at corsfix.com, is one of the Cloud & developer services we monitor. Our CORS Proxy is fast and secure. Fetch any resource and solve CORS errors instantly. Start for free and scale as you grow.
Corsfix publishes an official status page at status.corsfix.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 133 ms average, 71–333 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Corsfix incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
133 ms on average over the last 24 hours (71–333 ms).
Yes, at https://status.corsfix.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 Corsfix here at once, the problem is on Corsfix'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 Corsfix. 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.