User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
customergauge.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 2 min ago. Last stored result reached it in 304 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 332 ms | 0 |
| Tue 05 | 0 | 0.0 | 238 ms | 0 |
| Tue 07 | 0 | 0.0 | 299 ms | 0 |
| Tue 09 | 0 | 0.0 | 282 ms | 0 |
| Tue 11 | 0 | 0.0 | 191 ms | 0 |
| Tue 13 | 0 | 0.0 | 288 ms | 0 |
| Tue 16 | 0 | 0.0 | 386 ms | 0 |
| Tue 18 | 0 | 0.0 | 286 ms | 0 |
| Tue 20 | 0 | 0.0 | 201 ms | 0 |
| Tue 22 | 0 | 0.0 | 189 ms | 0 |
| Wed 01 | 0 | 0.0 | 165 ms | 0 |
| Wed 03 | 0 | 0.0 | 292 ms | 0 |
| Wed 05 | 0 | 0.0 | 159 ms | 0 |
| Wed 07 | 0 | 0.0 | 201 ms | 0 |
| Wed 10 | 0 | 0.0 | 274 ms | 0 |
| Wed 12 | 0 | 0.0 | 260 ms | 0 |
| Wed 14 | 0 | 0.0 | 317 ms | 0 |
| Wed 16 | 0 | 0.0 | 169 ms | 0 |
| Wed 18 | 0 | 0.0 | 300 ms | 0 |
| Wed 20 | 0 | 0.0 | 162 ms | 0 |
| Wed 23 | 0 | 0.0 | 300 ms | 0 |
| Thu 01 | 0 | 0.0 | 265 ms | 0 |
| Thu 03 | 0 | 0.0 | 319 ms | 0 |
| Thu 05 | 0 | 0.0 | 396 ms | 0 |
| Thu 07 | 0 | 0.0 | 259 ms | 0 |
| Thu 09 | 0 | 0.0 | 190 ms | 0 |
| Thu 11 | 0 | 0.0 | 243 ms | 0 |
| Thu 13 | 0 | 0.0 | 322 ms | 0 |
| Thu 15 | 0 | 0.0 | 211 ms | 0 |
| Thu 17 | 0 | 0.0 | 210 ms | 0 |
| Thu 19 | 0 | 0.0 | 251 ms | 0 |
| Thu 21 | 0 | 0.0 | 294 ms | 0 |
| Thu 23 | 0 | 0.0 | 263 ms | 0 |
| Fri 01 | 0 | 0.0 | 292 ms | 0 |
| Fri 03 | 0 | 0.0 | 353 ms | 0 |
| Fri 04 | 0 | 0.0 | 199 ms | 0 |
| Fri 06 | 0 | 0.0 | 277 ms | 0 |
| Fri 08 | 0 | 0.0 | 205 ms | 0 |
| Fri 10 | 0 | 0.0 | 268 ms | 0 |
| Fri 12 | 0 | 0.0 | 216 ms | 0 |
| Fri 14 | 0 | 0.0 | 226 ms | 0 |
| Fri 16 | 0 | 0.0 | 265 ms | 0 |
| Fri 17 | 0 | 0.0 | 236 ms | 0 |
| Fri 19 | 0 | 0.0 | 300 ms | 0 |
| Fri 21 | 0 | 0.0 | 202 ms | 0 |
| Fri 23 | 0 | 0.0 | 256 ms | 0 |
| Sat 01 | 0 | 0.0 | 273 ms | 0 |
| Sat 03 | 0 | 0.0 | 304 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for CustomerGauge 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 CustomerGauge goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CustomerGauge alerts to Slack, Discord or a webhook — free.
CustomerGauge is listed in our Cloud & developer category and checked at customergauge.com. Leverage your B2B customer data to reduce churn and increase revenue in your accounts.
CustomerGauge publishes an official status page at status.customergauge.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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 252 ms average, 152–353 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 CustomerGauge incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
252 ms on average over the last 24 hours (152–353 ms).
Yes, at https://status.customergauge.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 CustomerGauge here at once, the problem is on CustomerGauge'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 CustomerGauge. 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.