User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
uptimerobot.com · Cloud & developer
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 377 ms · 8 min ago.
No status feed
UptimeRobot does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 3 | 0 | 0.0 | 840 ms | 0 |
| Nov 3 | 0 | 0.0 | 653 ms | 0 |
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.
No outages on record for UptimeRobot 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 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.
UptimeRobot is listed in our Cloud & developer category and checked at uptimerobot.com. Live checks and user reports.
UptimeRobot has no official status feed we can read, so this page relies on our own checks and user reports.
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 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 809 ms average, 308–1739 ms range across 43 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public UptimeRobot incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
809 ms on average over the last 24 hours (308–1739 ms).
Not one we can read. This page uses independent checks of uptimerobot.com and user reports.
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 UptimeRobot here at once, the problem is on UptimeRobot's side.