HOW WE WORK

A better record
of what went wrong.

Signal Loss is an independent archive of significant digital service disruptions. It is designed to make primary-source incident information easier to scan, compare, and revisit.

01

Source selection

Entries link to provider-authored status reports, agency/court notices, or direct company statements. Where an original status portal is difficult to retrieve, we identify the independent capture used to preserve timestamps. Media reports are used only when they quote a company or document the public impact; those records are labelled accordingly. Unverified user-report spikes are not promoted to confirmed outages.

02

Summaries and accuracy

Summaries are editorial paraphrases, not provider statements. Durations, impact percentages, regions, and affected products are included only when supported by the linked source. Incident timelines show up to the three most recent timestamped source updates available to the editor. UTC is preserved; local clock times are converted in the reader’s browser. Date-only or approximate source timestamps are explicitly labelled, and missing updates are never invented. Provider reports may change after this archive snapshot.

03

Impact tiers

Widespread, Regional, and Product-level are editorial labels intended to help browse the archive. They are not provider severity ratings, customer counts, or a standardized measure of business impact.

04

Anonymous reactions

Reactions are designed to work without accounts. The server stores a salted hash derived from the visitor’s IP address and incident identifier, not the raw IP address. On shared networks, multiple people may be represented as one voter; rotating networks can weaken duplicate-vote prevention. Counts are community signals, not outage-impact metrics.

05

What this site is not

This is not a live status dashboard, an official provider status page, or a substitute for incident communications. Open and degraded statuses are the latest editorial snapshot retrieved during the stated coverage update, not a live health check. For operational decisions, follow the provider or agency status link directly. Coverage is curated and cannot guarantee capture of every local utility, telecom, bank, or public-sector event worldwide.

06

Corrections

For corrections, missing primary sources, or incident suggestions, contact the site maintainers. Every accepted entry should have a stable incident identifier, dates, a concise impact summary, and at least one original source.

Coverage snapshot · 18 November 2026: The archive contains 35 records, including 28 incidents or incident updates in the 4–18 November window and 7 earlier historical postmortems. Updates are currently curated into versioned data files; automatic discovery and editorial workflow are not yet enabled. The dataset excludes uncorroborated outage-report spikes (for example, Google Workspace showed no Gmail incident during the source check) and labels customer-reported or media-sourced events separately from provider-confirmed notices.
Browse the archive