User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
onedrive.live.com · Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests onedrive.live.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 3191 ms · 2 min ago.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 3499 ms | 0 |
| 11:45 | 0 | 0.0 | 2051 ms | 0 |
| 12:00 | 0 | 0.0 | 3041 ms | 0 |
| 12:15 | 0 | 0.0 | 2769 ms | 0 |
| 12:30 | 0 | 0.0 | 2107 ms | 0 |
| 12:45 | 0 | 0.0 | 2350 ms | 0 |
| 13:00 | 0 | 0.0 | 2950 ms | 0 |
| 13:15 | 0 | 0.0 | 2485 ms | 0 |
| 13:30 | 0 | 0.0 | 2846 ms | 0 |
| 13:45 | 0 | 0.0 | 2291 ms | 0 |
| 14:00 | 0 | 0.0 | 1549 ms | 0 |
| 14:15 | 0 | 0.0 | 3265 ms | 0 |
| 14:30 | 0 | 0.0 | 2928 ms | 0 |
| 14:45 | 0 | 0.0 | 2796 ms | 0 |
| 15:00 | 0 | 0.0 | 2139 ms | 0 |
| 15:15 | 0 | 0.0 | 3338 ms | 0 |
| 15:30 | 0 | 0.0 | 2767 ms | 0 |
| 15:45 | 0 | 0.0 | 3376 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.
Embed this status badge · JSON
No outages on record for OneDrive 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 OneDrive goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Runs on: Microsoft Azure
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.