User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
uptimerobot.com · Cloud & developer
Is UptimeRobot down?
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → uptimerobot.com—
Your browser → us—
Our checksReaching it
Official · ReportsNo status feed · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Our checks
Reaching it
Last check reached it in 1177 ms · 8 min ago.
Official status
No status feed
UptimeRobot does not publish a status feed we can read.
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:45 | 0 | 0.0 | 511 ms | 0 |
| 14:00 | 0 | 0.0 | 1701 ms | 0 |
| 14:15 | 0 | 0.0 | 910 ms | 0 |
| 14:30 | 0 | 0.0 | 661 ms | 0 |
| 14:45 | 0 | 0.0 | 1309 ms | 0 |
| 15:00 | 0 | 0.0 | 696 ms | 0 |
| 15:15 | 0 | 0.0 | 852 ms | 0 |
| 15:30 | 0 | 0.0 | 690 ms | 0 |
| 15:45 | 0 | 0.0 | 611 ms | 0 |
| 16:00 | 0 | 0.0 | 332 ms | 0 |
| 16:15 | 0 | 0.0 | 352 ms | 0 |
| 16:30 | 0 | 0.0 | 830 ms | 0 |
| 16:45 | 0 | 0.0 | 1400 ms | 0 |
| 17:00 | 0 | 0.0 | 404 ms | 0 |
| 17:15 | 0 | 0.0 | 1003 ms | 0 |
| 17:30 | 0 | 0.0 | 1248 ms | 0 |
| 17:45 | 0 | 0.0 | 970 ms | 0 |
| 18:00 | 0 | 0.0 | 683 ms | 0 |
| 18:15 | 0 | 0.0 | 691 ms | 0 |
| 18:30 | 0 | 0.0 | 417 ms | 0 |
| 18:45 | 0 | 0.0 | 361 ms | 0 |
| 19:00 | 0 | 0.0 | 1158 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed a live UptimeRobot status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for UptimeRobot yet. Outages of 10 minutes or more get their own page here.
Having trouble with UptimeRobot?
One report per service every 10 minutes from this network. No account.
Follow UptimeRobot
Get an email when UptimeRobot goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send UptimeRobot alerts to Slack, Discord or a webhook — free.
Questions
Is UptimeRobot down right now?
Checks are succeeding and user reports are near the baseline.
UptimeRobot not working for me but the status is fine. What now?
If UptimeRobot 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 UptimeRobot's side.
How does Damn is it down decide UptimeRobot's status?
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.
How often is UptimeRobot checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.