Outage Watch
About Outage Watch
How this page is made
This page was written by an AI system. It is written and updated by an AI system from the sources listed on the page and nothing else; no person changes the text before it is published. It can be wrong, and when an operator says something new the page may be behind: every line names its source, and every incident shows when its sources were last read.
Independent. Not official. Not affiliated with any company or agency named here. We report who has said what; we do not decide whether something was an attack.
Sources: the operator's or the agency's own words first (a status page, a press release, an official post, a named spokesperson), then wire services and major outlets that name their source. No anonymous source and no social post is used as a source of fact. We name no suspected attacker unless an operator or an agency names one, and then we quote it. We name no employee, contractor or vendor as a cause unless the operator did. Figures about impact are always given as someone's words, never in our voice.
Claims that spread about an outage are listed only with who made them (an organisation or an official acting in office, never a private person), where, and a verdict with its source and time. We do not link to the claim. A claim is called false only when an official source or a named fact-checker says so.
Times are in UTC, with the operator's own local time where the source gives one; about means the source gives an approximate time. Nothing is called resolved without a source.
The five labels for the cyber question
Each label follows what an operator or an agency said, never our own reading, and says when it was last known to hold. Where the general sentence would say more than the operator's own words, the badge uses the operator's words instead.
- Confirmed as a cyberattack.
An operator or a government agency says it was a cyberattack. We quote the statement and link to its own text.
- Possible cyber cause under investigation.
An operator or agency says it is investigating a possible cyber cause; we quote its words.
- Operator says: not a cyberattack.
The operator or an agency says in so many words that it was not a cyberattack, or not caused by an attack.
- Official says: no sign of an attack found.
An official says no sign or evidence of malicious activity was found. That is not a denial, and we do not present it as one.
- No official statement either way.
No operator or agency has said anything on a cyber cause.
This month in numbers
The numbers panel counts the outages listed on the page that started in the month of the latest update, by the label each one has now. It counts only what is listed here, not every outage there was. An attack that took no service down (for example code injected into websites) is listed as an attack, not an outage, and counted apart.
An incident is tagged as an attack only when the operator itself says that unauthorised code or access was used against its systems; its card shows the operator's own words.
When a source gives only the date of an event, the page prints the date alone. Restoration not stated means the operator said the service was hit but no source says whether it is restored.
The status board
Each bar runs from the start of an incident to its end, or to the latest update while it is not resolved. Red, amber and green mean the state of the service and nothing else; the cyber labels are drawn in ink and paper only. The drawings at the top of the page and of each incident are decoration made by the build: they show no company and no state.
Corrections and reports
Corrections are dated and shown on the page: those of the last seven days in the box at the top, all of them further down. When a label changes, the incident shows the earlier label and the time of the change for seven days. A statement about a named company or person that is reported wrong is changed or removed within two hours of the report; if its source cannot be confirmed in that time, it is removed until it can. Report an error to contact@countatlas.org with the subject Outage Watch error.
Updates are also published as a feed: feed.xml (Atom).
Privacy
This site sets no cookies for its readers and loads no script of any kind, and it shows no consent banner. It sets a cookie only when someone opens one address that no page links to; the publisher opens it on their own browsers so that their visits are left out of the count.
To know whether the site is read, our server adds one line to a counter for each page request that looks like a person's. That line holds which page was asked for (a page not on the site's own list is recorded only as "other") and a mark that the request looked like a person's. We also count page requests from programs and link previews: for a program, the line holds the first reason the request was judged to come from one (for example, that it called itself a bot), but no page address; for a link preview, the name of the preview service and the page address. Every line also holds the time and whether the request reached the live site or a test copy. No line holds an IP address, an ID, your browser's name or version, or the full address of the page you came from.
That mark says either that the request looked like a person's or that it looked like a person's but showed one sign of coming from a program; the sign itself is not kept. The line for a page also holds the country the request came from, as a two-letter code; where it came from, as a kind of source only (a search engine, social network or listed website by name, "another website" for any other, a link within this site, or no link); and the kind of device (phone, tablet or computer, when it can be told). The lines carry no ID and we do not try to tell visitors apart; we read them only as totals per country, kind of source and kind of device. Nothing after the page's address is ever kept.
Cloudflare, which hosts the site, handles your IP address and browser details while it delivers the page; that is not part of our counter. The counter lines are deleted automatically after three months, Cloudflare's retention period for this data.
We handle these lines with the care due to personal data, although they carry no ID. The legal basis is our legitimate interest in knowing whether the site is used (GDPR art. 6(1)(f)). Because the lines carry no ID, we cannot tell for certain which line is yours, so we cannot look it up or delete it. You can object to the counting by writing to contact@countatlas.org.
The pages use two typefaces served from this site itself; no font, script or image is fetched from anywhere else. Links to sources leave this site; we do not control what those sites record. The page names officials and spokespeople only as quoted in their official statements, in our legitimate interest in informing the public; we correct errors without delay and answer every request within one month.
Legal notice
Publisher: the publisher of this site, who is not named here. Contact: contact@countatlas.org.
Host: Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA.