 |
| Is It Your Internet or a Platform Outage |
Large-scale outages affecting Microsoft 365, Teams, Zoom, and other widely used platforms have happened more than once this year, and when one hits, it often looks exactly like a problem with your own home internet — a call won't connect, a file won't sync, a sign-in page hangs. Knowing how to tell the difference quickly saves you from spending twenty minutes restarting your router for a problem that was never yours to fix in the first place.
Why Platform Outages Masquerade as Local Internet Problems
When a major service like Microsoft 365 or a cloud provider it depends on has an issue, the symptoms you personally experience often look purely local: an app that won't load, a login that hangs, a file that won't sync. Nothing about the error message necessarily tells you the problem is happening on Microsoft's or another provider's end rather than your own network — which is exactly why large outages this year have repeatedly caused people to blame their home WiFi before realizing the actual cause was much further upstream.
Step 1: Check Whether It's Affecting Everything, or Just One Service
This is the fastest and most useful first check. Try loading a completely unrelated website — a news site, a search engine, anything that doesn't depend on the same service that's failing.
- If unrelated sites load normally, but one specific service (Teams, Zoom, a cloud file tool) is broken: this points strongly toward a platform-specific issue, not your internet connection
- If everything is failing, including sites that have nothing to do with each other: this points toward a genuine local or ISP-level problem, covered in our other network guides on this site
Step 2: Check an Independent Status Source
Most major platforms maintain a status page, and independent outage-tracking sites aggregate real-time user reports across many services at once, which is often faster and more reliable than a company's own status page, since those are sometimes slow to officially acknowledge an issue already affecting many users.
What to check:
- The platform's own status page (search "[service name] status")
- An independent outage tracker, which shows a live chart of user-submitted reports and is often one of the fastest ways to confirm "it's not just you"
If reports are spiking broadly for the exact service you're having trouble with, right around the time your problem started, that's a strong signal this isn't a local issue at all.
Step 3: Ask a Colleague on a Different Network
If a colleague working from a completely different location and internet provider is experiencing the exact same issue at the same time, this effectively rules out your specific home network as the cause, since it's extremely unlikely two unrelated home networks would fail identically and simultaneously by coincidence.
Step 4: Know the Telltale Signs of a Platform-Side Issue
A few patterns specifically suggest the problem sits upstream rather than with you:
- A service that was working fine suddenly fails for everyone in a meeting or team at once, rather than progressively for one person
- Sign-in pages that hang or spin indefinitely, rather than showing a connection error — this is a common pattern specifically tied to authentication-related outages
- Multiple seemingly unrelated services failing together (for example, Teams, Outlook, and OneDrive all having problems simultaneously) — this pattern has repeatedly pointed to a shared underlying dependency failing, such as a cloud provider or authentication system multiple services rely on
Step 5: What to Actually Do During a Confirmed Platform Outage
Once you've confirmed it's not your network, further local troubleshooting is genuinely a waste of time until the outage resolves. Instead:
- Switch to an alternative communication method if one is available — a phone call, a different messaging platform, or the affected service's mobile app, which occasionally remains functional even when the desktop client doesn't
- Let relevant colleagues or clients know proactively that you're aware of a wider issue, rather than letting them assume something is wrong on your end specifically
- Check the status page periodically rather than continuously, and resume normal work once it's confirmed resolved
Step 6: Don't Let This Become a Habit of Assuming Every Problem Is "Just an Outage"
It's worth being honest that genuine local network problems are still far more common day-to-day than major platform outages. If you've checked an independent status source and reports aren't spiking for the service you're using, treat it as a local issue and work through the relevant troubleshooting — our guides on home WiFi slowing down during work hours and router placement and setup mistakes cover the most common underlying causes.
A Fast Diagnostic Order
- Try an unrelated website — does the rest of the internet work?
- Check an independent outage tracker for the specific service
- Ask a colleague on a different network if they're affected too
- If confirmed local, move to standard network troubleshooting instead
Quick Reference
| Signal | Points toward |
|---|---|
| Only one service fails, everything else works | Platform-specific issue |
| Everything fails, including unrelated sites | Local network issue |
| Colleague on a different network has the same problem | Platform-side, not your network |
| Outage tracker shows a spike for that exact service | Confirmed platform outage |
| No spike on outage trackers, only you affected | Genuinely local — troubleshoot your network |
Status pages and outage trackers reflect real-time conditions and can change quickly — always check current status directly rather than relying on this guide's examples, which describe general patterns rather than any specific ongoing incident.