Checked 3 minutes ago
One problem in the last 48 hours, 1 hour ago, lasting 40 min.
This longer record is here so the 48-hour picture above can mean something — without it we could tell you a problem happened, but not whether that is normal for Azure DevOps.
Something was impaired on 5.55% of our checks over that window. That is how often Azure DevOps was reporting a problem somewhere, which is not the same as how often it was unreachable. The longest outage we have on record ran 16h 55m.
The last 30 days of Azure DevOps, one row each.
| Day | Clear | Up | Checks | Started | Longest ended |
|---|---|---|---|---|---|
| 2026-10-21 so far today | 95.48% | 100% | 177 | 1 | 40 min |
| 2026-10-20 | 100% | 100% | 287 | none | — |
| 2026-10-19 | 100% | 100% | 287 | none | — |
| 2026-10-18 | 100% | 100% | 287 | none | — |
| 2026-10-17 | 100% | 100% | 288 | none | — |
| 2026-10-16 | 100% | 100% | 287 | none | — |
| 2026-10-15 | 95.82% | 100% | 287 | 1 | 1h 0m |
| 2026-10-14 | 92.68% | 100% | 287 | 1 | 1h 45m |
| 2026-10-13 | 97.86% | 100% | 281 | 1 | 29 min |
| 2026-10-12 | 100% | 100% | 287 | none | — |
| 2026-10-11 | 100% | 100% | 287 | none | — |
| 2026-10-10 | 100% | 100% | 287 | none | — |
| 2026-10-09 | 97.21% | 100% | 287 | 1 | 40 min |
| 2026-10-08 | 100% | 100% | 287 | none | — |
| 2026-10-07 | 100% | 100% | 287 | none | — |
| 2026-10-06 | 89.55% | 100% | 287 | 1 | 2h 30m |
| 2026-10-05 | 94.08% | 100% | 287 | 1 | 1h 25m |
| 2026-10-04 | 100% | 100% | 287 | none | — |
| 2026-10-03 | 100% | 100% | 287 | none | — |
| 2026-10-02 | 91.29% | 100% | 287 | 2 | 1h 40m |
| 2026-10-01 | 100% | 100% | 287 | none | — |
| 2026-09-30 | 85.37% | 100% | 287 | 1 | 3h 30m |
| 2026-09-29 | 75.96% | 100% | 287 | 1 | 5h 45m |
| 2026-09-28 | 89.2% | 100% | 287 | 1 | 2h 35m |
| 2026-09-27 | 100% | 100% | 287 | none | — |
| 2026-09-26 | 100% | 100% | 288 | none | — |
| 2026-09-25 | 60.28% | 100% | 287 | 1 | 9h 37m |
| 2026-09-24 | 90.24% | 100% | 287 | 2 | 45 min |
| 2026-09-23 | 100% | 100% | 287 | none | — |
| 2026-09-22 | 81.88% | 100% | 287 | 2 | 3h 0m |
Clear is the share of checks that found nothing wrong at all; Up is the share that found Azure DevOps actually reachable — a vendor reporting one impaired component scores zero on the first and a hundred on the second, and both are true. Started counts outages that began that day and Longest ended the longest that finished on it, so a problem running across midnight is counted once, on the day it began, and measured on the day it stopped.
Rows recorded before 8 August 2026 do not carry a check count — the figure was kept and the denominator was not — so their percentages are shown without one rather than with a number borrowed from somewhere else. Rows before 9 August 2026 have no Up figure either: until then we recorded only whether something was wrong, not whether it was down, and the two are different questions.
| Started | Lasted | Severity | What happened |
|---|---|---|---|
| 2026-10-21 13:30 UTC | 40 min | having problems | Investigating a service disruption |
| 2026-10-15 07:20 UTC | 1h 0m | having problems | Investigating a service disruption |
| 2026-10-14 08:31 UTC | 1h 45m | having problems | Investigating a service disruption |
| 2026-10-13 13:26 UTC | 29 min | having problems | Investigating a service disruption |
| 2026-10-09 13:45 UTC | 40 min | having problems | Investigating a service disruption |
| 2026-10-06 16:20 UTC | 2h 30m | having problems | Investigating a service disruption |
| 2026-10-05 19:30 UTC | 1h 25m | having problems | Investigating a service disruption |
| 2026-10-02 21:45 UTC | 1h 40m | having problems | Investigating a service disruption |
| 2026-10-02 06:45 UTC | 25 min | having problems | Investigating a service disruption |
| 2026-09-30 00:15 UTC | 3h 30m | having problems | Investigating a service disruption |
| 2026-09-29 13:01 UTC | 5h 45m | having problems | Investigating a service disruption |
| 2026-09-28 19:55 UTC | 2h 35m | having problems | Investigating a service disruption |
| 2026-09-25 13:26 UTC | 1h 36m | having problems | Investigating a service disruption |
| 2026-09-24 22:25 UTC | 9h 37m | having problems | Investigating a service disruption |
| 2026-09-24 08:11 UTC | 45 min | having problems | Investigating a service disruption |
| 2026-09-22 19:21 UTC | 3h 0m | having problems | Investigating a service disruption |
| 2026-09-22 09:02 UTC | 1h 19m | having problems | Investigating a service disruption |
| 2026-09-21 17:11 UTC | 2h 10m | having problems | Investigating a service disruption |
| 2026-09-18 14:40 UTC | 35 min | having problems | Investigating a service disruption |
| 2026-09-09 20:50 UTC | 4h 31m | having problems | Investigating a service disruption |
Status pages report the vendor's view of their own service, and they lag real
outages — often by many minutes, sometimes by hours, because a human usually has to
confirm before anything is posted. They also can't see the two things most likely to
be wrong at your end.
The first is your own connection under load. A line that idles at 20 ms can
jump to 300 ms the moment something starts uploading, which drops you from sessions
and looks exactly like a server fault. Your plan speed says nothing about this; it's
called bufferbloat and almost nobody measures it.
The second is where everyone else in your group is. A service can be healthy in your
region and unwell in theirs, and if one person is hosting, their problem is everyone's
problem.
Azure DevOps being fine where you are does not mean it is fine for everyone in your group. The live dashboard resolves status against each person's own region, and will tell you which of your friends is in an affected area — plus who has the connection to host, which is usually a different question from who has the fastest plan.
Worth a look when more than one thing feels broken at once: if several are genuinely down together, the fault is usually something they share rather than anything at your end. We are not claiming these particular services fail together — the live dashboard says when they actually do.