User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
dotcom-monitor.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 1 hr ago. Last stored result reached it in 60 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 11 | 0 | 0.0 | 396 ms | 0 |
| Wed 13 | 0 | 0.0 | 378 ms | 0 |
| Wed 15 | 0 | 0.0 | 99 ms | 0 |
| Wed 17 | 0 | 0.0 | 148 ms | 0 |
| Wed 19 | 0 | 0.0 | 89 ms | 0 |
| Wed 21 | 0 | 0.0 | 120 ms | 0 |
| Thu 00 | 0 | 0.0 | 110 ms | 0 |
| Thu 02 | 0 | 0.0 | 73 ms | 0 |
| Thu 04 | 0 | 0.0 | 50 ms | 0 |
| Thu 06 | 0 | 0.0 | 113 ms | 0 |
| Thu 08 | 0 | 0.0 | 164 ms | 0 |
| Thu 10 | 0 | 0.0 | 64 ms | 0 |
| Thu 12 | 0 | 0.0 | 72 ms | 0 |
| Thu 14 | 0 | 0.0 | 102 ms | 0 |
| Thu 16 | 0 | 0.0 | 102 ms | 0 |
| Thu 18 | 0 | 0.0 | 53 ms | 0 |
| Thu 20 | 0 | 0.0 | 443 ms | 0 |
| Thu 22 | 0 | 0.0 | 134 ms | 0 |
| Fri 00 | 0 | 0.0 | 54 ms | 0 |
| Fri 03 | 0 | 0.0 | 179 ms | 0 |
| Fri 05 | 0 | 0.0 | 41 ms | 0 |
| Fri 07 | 0 | 0.0 | 33 ms | 0 |
| Fri 09 | 0 | 0.0 | 516 ms | 0 |
| Fri 10 | 0 | 0.0 | 62 ms | 0 |
| Fri 12 | 0 | 0.0 | 56 ms | 0 |
| Fri 13 | 0 | 0.0 | 220 ms | 0 |
| Fri 15 | 0 | 0.0 | 206 ms | 0 |
| Fri 16 | 0 | 0.0 | 47 ms | 0 |
| Fri 18 | 0 | 0.0 | 78 ms | 0 |
| Fri 19 | 0 | 0.0 | 84 ms | 0 |
| Fri 21 | 0 | 0.0 | 69 ms | 0 |
| Fri 23 | 0 | 0.0 | 147 ms | 0 |
| Sat 01 | 0 | 0.0 | 64 ms | 0 |
| Sat 03 | 0 | 0.0 | 103 ms | 0 |
| Sat 06 | 0 | 0.0 | 66 ms | 0 |
| Sat 08 | 0 | 0.0 | 365 ms | 0 |
| Sat 10 | 0 | 0.0 | 96 ms | 0 |
| Sat 12 | 0 | 0.0 | 62 ms | 0 |
| Sat 14 | 0 | 0.0 | 28 ms | 0 |
| Sat 17 | 0 | 0.0 | 99 ms | 0 |
| Sat 19 | 0 | 0.0 | 102 ms | 0 |
| Sat 21 | 0 | 0.0 | 85 ms | 0 |
| Sun 00 | 0 | 0.0 | 134 ms | 0 |
| Sun 02 | 0 | 0.0 | 43 ms | 0 |
| Sun 04 | 0 | 0.0 | 90 ms | 0 |
| Sun 07 | 0 | 0.0 | 87 ms | 0 |
| Sun 09 | 0 | 0.0 | 30 ms | 0 |
| Sun 11 | 0 | 0.0 | 60 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 Dotcom Monitor 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 Dotcom Monitor goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track Dotcom Monitor (dotcom-monitor.com) as part of the Cloud & developer group. Website monitoring that catches downtime before customers do. Real-browser checks from 30+ locations, instant alerts and a 30-day free trial.
Dotcom Monitor publishes an official status page at status.dotcom-monitor.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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 75 ms average, 28–134 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Dotcom Monitor incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
75 ms on average over the last 24 hours (28–134 ms).
Yes, at https://status.dotcom-monitor.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 Dotcom Monitor here at once, the problem is on Dotcom Monitor'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 Dotcom Monitor. 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.