User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
office.com · Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests office.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 243 ms · 2 min ago.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 115 ms | 0 |
| 11:45 | 0 | 0.0 | 307 ms | 0 |
| 12:00 | 0 | 0.0 | 982 ms | 0 |
| 12:15 | 0 | 0.0 | 828 ms | 0 |
| 12:30 | 0 | 0.0 | 187 ms | 0 |
| 12:45 | 0 | 0.0 | 419 ms | 0 |
| 13:00 | 0 | 0.0 | 173 ms | 0 |
| 13:15 | 0 | 0.0 | 210 ms | 0 |
| 13:30 | 0 | 0.0 | 207 ms | 0 |
| 13:45 | 0 | 0.0 | 136 ms | 0 |
| 14:00 | 0 | 0.0 | 189 ms | 0 |
| 14:15 | 0 | 0.0 | 133 ms | 0 |
| 14:30 | 0 | 0.0 | 138 ms | 0 |
| 14:45 | 0 | 0.0 | 213 ms | 0 |
| 15:00 | 0 | 0.0 | 478 ms | 0 |
| 15:15 | 0 | 0.0 | 281 ms | 0 |
| 15:30 | 0 | 0.0 | 232 ms | 0 |
| 15:45 | 0 | 0.0 | 286 ms | 0 |
| 16:00 | 0 | 0.0 | 190 ms | 0 |
| 16:15 | 0 | 0.0 | 112 ms | 0 |
| 16:30 | 0 | 0.0 | 177 ms | 0 |
| 16:45 | 0 | 0.0 | 218 ms | 0 |
| 17:00 | 0 | 0.0 | 233 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 Microsoft 365 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 Microsoft 365 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.