What 'investigating' actually means: reading provider status pages under pressure
Status pages are written to reassure, not to inform. Here is how to read provider incident language and turn it into an operational decision.
When a provider you depend on posts an incident, the words they choose are deliberate. "Investigating", "identified", "monitoring", "resolved" are not casual descriptions. They are stages, and each one tells you something different about how much you can rely on that service in the next few minutes.
The vocabulary, decoded
Most major providers follow the same loose grammar. Knowing what each stage implies for your own systems is more useful than the prose attached to it.
- Investigating: the provider sees a problem but does not yet understand it. Assume the blast radius is still growing.
- Identified: they know the cause. Recovery has a shape now, but the impact is still live.
- Monitoring: a fix is in. This is the stage where things often look better than they are.
- Resolved: the provider considers it closed. Your downstream systems may still be draining queues and retries.
Scope is the word that matters most
The status itself is less important than the scope buried in the update. "Elevated error rates in eu-central-1" is a completely different operational situation from "elevated error rates", even though both might sit under the same red icon. One affects a region; the other affects everyone. Status pages routinely lead with the severity and bury the scope two sentences down.
Read the scope before the severity. A critical incident in a region you do not serve is someone else’s problem.
The gap between posted and real
There is almost always a lag between when an incident begins and when it appears on a status page. Providers verify before they publish, which is responsible but means the page trails reality. If your own signals show a provider degrading, you do not need to wait for their confirmation to start communicating with your customers. The status page is corroboration, not permission.
The practical move is to watch the providers you actually depend on, in one place, and to treat their status language as structured data rather than reassurance. The stage tells you how stable the situation is. The scope tells you whether it is yours to worry about.
Crowswatch watches the providers, domains and dependencies behind signals like these, and connects them into one operational view.
Monitor your dependencies with Crowswatch