Vendor Status DashboardRead the official signal
Each built-in integration uses a provider’s official machine-readable status source, never scraped page markup.
Status page monitor for on-call
Monitor the status pages behind your stack.
See the signal in your scope.
Watch 60 official machine-readable vendor feeds, filter provider incidents by the regions and components you use, and keep triage context beside your work.
Free forever · 5 vendorsNo accountNo extension telemetryLocal configuration
Scoped incident command center
Real product view
60 feedsofficial vendor sources
Your scoperegion, component and criticality
5 freereplace enabled vendors anytime
Local-firstno extension telemetry
What a useful monitor should do
Turn a provider update into an operational answer.
Separate global truth from your stack
Keep the provider’s incident visible, then filter your operational view by relevant region, component and profile.
Expose the blast radius
Mark dependencies P0, P1 or P2 so the same provider event carries the right urgency for your team.
Link back to the authority
Every signal keeps a route to the official source so responders can verify wording, timestamps and provider updates.
Keep response notes local
Profiles, criticality, notes and bounded HTTPS runbook links stay in local browser storage.
Never invent root cause
Concurrent changes are labeled as concurrent. The monitor does not claim that one vendor caused another failure.
Incident triage workflow
From official signal to the next response action.
Observe
Read the current incident or maintenance signal from the provider’s official feed.
Scope
Check whether the affected region or component overlaps the operational profile you are using.
Prioritize
Use dependency criticality to distinguish a P0 production path from a lower-impact service.
Act
Open the official proof, capture local triage context and follow the runbook your team already trusts.
The source remains authoritative
Useful signal, with honest limits.
Status pages can be late
A provider may publish after users begin seeing impact. Absence of an official incident is not proof that your systems are healthy.
Providers may omit your exact impact
Official updates can be broad or incomplete. Your metrics, logs and traces remain essential for confirming user-facing impact.
This is not root-cause detection
The extension helps answer whether a vendor is reporting trouble. It does not replace observability or causal investigation.
Straight answers
Status page monitor FAQ
What does a status page monitor watch?
Vendor Status Dashboard reads official machine-readable status feeds from supported providers. It does not scrape status-page HTML.
Does a provider incident mean my stack is affected?
Not necessarily. Provider status is global truth. Add regional and component scope plus P0, P1 or P2 criticality so your operational view reflects the dependencies you actually use.
Does Vendor Status Dashboard detect root cause?
No. It reports official provider signals and can group concurrent changes, but it never claims that one vendor caused another failure. The provider source remains authoritative.
Do I need an account?
No. The free extension supports five enabled vendors, stores configuration locally and sends no extension telemetry to VendorStatus. See the privacy policy for the complete data boundary.
Start with your production path
Monitor the five vendors that matter first.
Install free, enable the providers behind your critical path, then open the Side Panel when an incident starts.
Free forever · 5 vendors · No account · Local configuration