Is the Service Down, or Is It You? Settle It in Two Minutes

Outlook will not load. Or Teams says you are offline while everything else works. Or an app that was fine an hour ago now refuses, and you are already three steps into a fix you may not need.

I have watched people lose whole evenings to this, so let me give you the two minutes that stops it.

That is the expensive part. People reinstall things, reset settings and dismantle working machines over faults that were never theirs and were fixed by somebody else within the hour.

Two minutes settles it. This is the order.

The two minute test, in order

One: try it on your phone, on mobile data. Not your home Wi-Fi. Actual cellular.

Working there and failing on your PC means the problem is your machine or your connection. Failing on both means it is not you at all.

Two: try a different network entirely. Tether your PC to your phone for a minute.

Working on the tether and failing on your broadband narrows it to your home connection or something between you and that service.

Three: try a different browser, or a private window. That runs with extensions off.

Working there means the fault is your normal browser profile, which is a much smaller problem than the one you thought you had.

⭐ Those three tests take longer to read than to do, and between them they eliminate almost everything before you touch a setting.

What a mass outage actually looks like

Because knowing the shape of one saves you the afternoon.

It starts for a lot of people at once, with no update installed and nothing changed at your end. That last part is the tell. A fault that arrives while you are away from the machine, doing nothing, is rarely something you caused.

It is not usually total. During the Snipping Tool outage of January 2026, people could still use Windows perfectly. One app refused with a licensing error and everything else was fine.

And the error message often points the wrong way. That same outage told everybody to check they were signed in to the Microsoft Store. The Store was not the problem and the Store route did not fix it.

Ours, and marked as ours: when a message names a thing to go and check, and checking it changes nothing, stop following the message. It was written for a different failure than the one you have.

The evidence that it is not you

Ours, and marked as ours: search the exact error code with today's date. Not the error alone. The code plus the date.

Reported by owners in exactly that pattern: if a dozen people posted the same code that morning, you have your answer and it took thirty seconds. During the January 2026 outage, seven people confirmed the same fix within four hours on one thread, and three more reported it failing.

That volume in one afternoon is not a coincidence.

Check the vendor's own status page, if they have one for consumers. Microsoft publishes Windows release health with known issues in current builds, which is the closest thing to a consumer status page it runs.

⚠️ Be aware what those pages do and do not cover. Microsoft's service health dashboard is inside the admin centre and is for organizations, not for people with a home PC.

Its release health page covers Windows itself rather than individual apps.

What to do while it is down

Not nothing, but not much.

Wait, if you can. Most large outages are measured in hours.

Use the web version if the app is the thing failing. Web players, web mail and browser versions of desktop apps often survive when the installed app does not, because they take a different route.

Do not reinstall Windows. ⛔ Somebody did that over a browser bug in February 2025, then swapped an NVMe drive as well, and the actual fix was a browser update that arrived days later. He changed nothing else and it started working.

When it really is you after all

If the phone test and the tether test both point at your machine, it is yours, and the answer depends on what is failing.

Reported by advisers across every Store-app thread on Microsoft's boards, and worth following in order. One app, everything else fine. Repair it before you reset it. Settings, Apps, Installed apps, the three dots, Advanced options, then Repair. Repair keeps your data. Reset does not.

Every app that needs signing in. That points at your account rather than the apps. Copilot showing a blank page covers a specific version of this, where signing out and back in cleared a stuck session.

Everything that touches the internet. Then it is the connection. Websites slow to start loading covers the case where a speed test looks perfect and pages still crawl.

The thing worth changing about how you approach this

⭐ The habit worth building is checking before fixing, not after.

Almost everyone runs the diagnosis backwards. They spend an hour on their own machine, get nowhere, and only then search the error and find four hundred other people who had it that morning.

Ours, and marked as ours: two minutes of testing at the start is worth an hour of undoing at the end. And the machine you did not dismantle is worth more than either.

If it happens repeatedly to the same app

Then it is worth treating as a real fault rather than an outage, because outages do not recur weekly to one person.

Look at what is common to the failures. The same time of day points at something scheduled. After every restart points at startup. After every Windows update points at a version conflict.

Ours, and marked as ours: write down the date and time each time it happens, for three occurrences. That pattern is worth more to anybody helping you than any description of the symptom, and almost nobody arrives with one.

Status: written 22 August 2026. Microsoft publishes Windows release health for known issues in current builds, and its service health dashboard is an admin centre tool rather than a consumer one.

How do I know if a service is down or it is my computer?

Try it on your phone using mobile data rather than Wi-Fi. Working there and failing on your PC points at your machine. Failing on both means the service is down and there is nothing on your computer to fix.

Where can I check if Windows has a known problem?

Microsoft publishes a Windows release health page listing known issues in current builds. Its service health dashboard is different: that one lives inside the admin centre and is aimed at organizations rather than home users.

Why does the error message tell me to check the wrong thing?

Because messages are written for the failure the developer expected, not the one you have. In the January 2026 Snipping Tool outage the message sent everybody to the Microsoft Store, and the Store was not the problem and did not fix it.

Should I reinstall Windows if an app stops working?

Almost never, and certainly not first. One owner reinstalled Windows and replaced a drive over what turned out to be a browser bug, fixed days later by a routine update with nothing else changed on his machine.

The Short Version

• Phone on mobile data, then a tether, then a private window. Three tests, two minutes.
• A fault that starts while you are away, with nothing changed, is rarely yours.
• Search the error code plus today's date before touching anything.
• Error messages point at what the developer expected, not at what actually broke.
• Repair an app before you reset it. Repair keeps your data, reset does not.
• One owner reinstalled Windows and swapped a drive over a browser bug.

Where to Next

Pick up your phone, turn off its Wi-Fi, and try the thing that is failing. Thirty seconds, and it decides whether anything on this page or on your computer is worth your time.

If it turns out to be a sign-in problem, Copilot showing a blank page has a workaround an owner confirmed. If it is a Store app that will not open, the Snipping Tool not working covers the outage this page keeps referring to.

If you have been caught out by an outage that looked like your fault, tell me below what it was. I would like to build a list of the messages that mislead.