Blog
Why vendor status pages cannot be trusted alone
Vendor status pages are useful self-reports, not independent measurement. Why teams need an outside reachability check before telling customers everything is fine.
Vendor status pages are not independent journalism. They are operated by the same company whose product is under scrutiny. That does not make every entry a lie. It does mean they are a primary source with incentives, process lag, and a narrow definition of "down."
Self-report is not measurement
A status page usually reflects internal health checks, component dashboards, and human incident process. Those can be correct and still miss what your region or your API path is seeing. They can also stay green while public endpoints are failing for some customers.
What we do instead
StackWitness runs its own probes against real service hosts and also reads the public vendor status feed. We put those side by side:
- Independently measured reachability - did the host answer us from our regions?
- Vendor reported status - what did their status page say at the same window?
We do not claim to fully verify their product. A successful TCP/HTTP handshake is not proof that billing, search, or webhooks are healthy. It is still a harder signal than waiting for a button someone forgot to press.
The divergence that matters
When our probes cannot reach a host and the vendor still claims operational, that is a defensible under-report signal. When the vendor already reports an outage, we do not invent a fight with their page from a single handshake. Honesty is asymmetric on purpose.
Use vendor status pages. Just do not use them alone when you are about to tell a customer it is fine.