Media resources
Background information and links for journalists, analysts, and researchers writing about ServiceAlert or citing our reliability reports.
For questions, interviews, or corrections, email support@servicealert.ai.
About ServiceAlert
ServiceAlert helps teams keep track of the online services they rely on. It monitors third-party status pages alongside a team’s own websites, APIs, DNS, and certificate-expiry checks. Incidents and customer-facing status updates are managed from the same dashboard.
Quick facts
- Public service catalog
- 2,300+ cloud and SaaS services. This count is rounded down to the nearest hundred.
- Reliability reports
- Published monthly after the reporting month has ended.
- Research basis
- Normalized provider-status observations. Public reports contain selected aggregate findings.
Research and citations
Our first provenance-qualified monthly report will be linked here after a complete reporting window is available.
- MethodologyHow public findings are calculated and what they do not measure.
- Incident historyPublic incident records and source links.
When citing a figure, link to the individual report and keep its measurement label intact. An issue-free-day rate is not the same as contractual or duration-based uptime.
Outage briefs to cite
Short incident summaries with provider links, UTC timelines, affected services and explicit corrections. Publication and review dates are separate from the incident dates.
- GitHub outage on August 17, 2026: timeline and recovery GitHub reported a 7-hour, 47-minute incident on August 17. A source-checked timeline separates broad recovery from Actions and Copilot recovery. Reviewed September 12, 2026.
- AWS Direct Connect Frankfurt incident: August 15–18, 2026 AWS reported packet loss at Equinix FR5 in Frankfurt. This corrected brief separates affected Direct Connect connections from wider AWS availability. Reviewed September 12, 2026.
Browse reviewed outage reports or subscribe to the outage report feed.
For a citation, use the brief's title, ServiceAlert.ai, its review date and its permanent URL. Keep provider attribution and regional or product scope intact. An incident window does not establish downtime for every customer. Report corrections to support@servicealert.ai.
Data availability
Public reports contain selected, rounded summary findings. We do not provide bulk observation history, a complete source inventory, internal thresholds, or event-level exports.
If you need to check a specific published figure, send the report link and your question to support@servicealert.ai.
Logos
Use the dark version on a light background and the light version on a dark background. Please do not alter the colors or proportions.
