OutageHQ runs automated health checks against over 90 popular services — including Google, GitHub, YouTube, Discord, and Slack — every 5 minutes. When something goes down, you know within seconds. Here is how the monitoring pipeline works, step by step.
Our monitoring system sends HTTP requests to each of the 90+ services we track every 5 minutes. We measure response time, HTTP status code, and whether the service is reachable at all. If a check fails or takes too long, the service is flagged immediately.
Each service is classified as Operational (responding normally), Degraded (slow or returning errors intermittently), or Down (unreachable or returning server errors). The classification updates automatically based on the latest check results.
Status changes are pushed to your browser via server-sent events the moment they happen. No need to refresh the page — you see the update within seconds of our system detecting it.
We record response times for every check and display them as interactive charts on each service page. You can spot performance degradation trends — a service slowing from 200ms to 2,000ms over an hour typically signals an emerging problem before it becomes a full outage.
Anyone can report an outage with a single click — no account, no email, no personal information collected. Community reports supplement our automated checks and help confirm whether an issue is widespread or isolated to a specific region or ISP.
We retain monitoring data for the past 24 hours on each service page, showing uptime percentage, response time trends, and the timeline of any incidents. This helps you distinguish between a brief blip and a sustained outage.
OutageHQ runs automated checks every 5 minutes and updates status pages when those checks show a service is operational, degraded, down, or unknown.
Degraded means the service is still reachable but checks are slow, intermittent, or returning errors that suggest partial problems.
User reports help identify symptoms that automated checks may not fully capture, such as login trouble, delayed messages, or app-specific failures.
No. One report is only a signal. It should be compared with automated checks, report volume, related services, and official sources.
Want to see it in action? Head to the service status dashboard to check the live status of any service, create a live status widget for your own site, or read more about OutageHQ.
← Back to dashboard