Outage.ReportOutage.Report tracks service outages in real time from user problem reports and signals from social networks, judged against what is normal for each service. Our data is free to cite and screenshot with attribution — no permission needed.
Attribute the data to “Outage.Report” and, online, link the service page you are citing (for example outage.report/spotify). That is all we ask.
“User reports of problems with Spotify spiked at 14:32 UTC — around 12× the normal rate for the service, according to Outage.Report.”
Charts and incident cards are designed to be screenshotted and published — the outage.report mark is drawn inside the graphic. If you crop it out, credit Outage.Report in the caption.
Cite our numbers as user reports (“reports spiked”, “reports peaked at N per 5 minutes”), not as counts of affected users — reports are a sample that indicates scale and timing, not a census.
Users report problems directly on each service page, and we continuously monitor social signals about services not working. Both streams are bucketed into per-service time series, minute by minute.
Every service has a background level of complaints even on a normal day. Incoming volume is compared against what is typical for that service; an incident is confirmed only when reports significantly exceed that baseline — not at any fixed absolute number.
Each confirmed incident is recorded with its start time, peak report rate and when it occurred, duration, severity, the most-reported problems, and the geographic spread of reports. Records stay on the service page permanently, so a citation keeps pointing at the incident it described.