Skip to main content

​
Overview

Pro or Enterprise plan required. Crowdsourced incident detection is available on Pro and Enterprise plans. Free plan users can view official status page incidents only.
Crowdsourced Incidents are service disruptions detected through community feedback before the official status page acknowledges the problem. When multiple users report issues with a service, StatusStack aggregates these reports, assigns a confidence score, and can alert your team — often before the provider’s own status page reflects the outage.

​
How It Works

​
Detection Flow

  1. Community Reports — Users across StatusStack (including the browser extension) report issues they’re experiencing with a service
  2. Aggregation — StatusStack groups reports by service and timeframe to identify patterns
  3. Threshold Detection — When reports cross a confidence threshold, a crowdsourced incident is created
  4. Confidence Scoring — Each incident receives a confidence score based on report volume, consistency, and timing
  5. Notification — Your team is alerted about the potential issue
  6. Resolution — The incident is resolved when the service recovers or the official status page confirms and resolves the issue

​
Incident Details

Each crowdsourced incident includes:

​
Confidence Levels

​
Early Warning Advantage

Crowdsourced incidents give your team a head start on incident response. The detection lead time shows how far ahead of the official status page StatusStack detected the issue. Common scenarios where crowdsourced detection is faster:
  • Provider status pages that update slowly or infrequently
  • Regional outages that aren’t yet reflected on global status pages
  • Partial degradations that affect some users before being officially acknowledged
  • New or emerging issues during the early minutes of an incident

​
Notifications for Crowdsourced Incidents

Crowdsourced incidents integrate with StatusStack’s existing notification system. When a crowdsourced incident is detected for a service in one of your Stacks, your notification rules apply as usual. This means you can receive early warnings through:
  • Slack, Discord, or Microsoft Teams
  • Email notifications
  • SMS alerts
  • Custom webhook integrations

​
Best Practices

Don’t treat all crowdsourced incidents equally. High-confidence incidents (80%+) warrant immediate investigation, while low-confidence ones may be worth monitoring before taking action.
Crowdsourced incidents complement — not replace — official status page monitoring. Use them as an early warning layer on top of your existing monitoring setup.
Track how much advance warning crowdsourced detection gives you for services you depend on. This helps you understand the value and adjust your incident response accordingly.

Sources

Understanding monitored services

Notifications

Multi-channel notification system

Status Monitoring

Real-time status monitoring guide

Notification Setup

Configure alert rules

Browser Extension

Report an outage from Chrome or Edge with no account