This should be resolved now

In T308940#7947028, @RhinosF1 wrote:

This should be resolved now

I tried to report it sooner, but Phabricator was down!

Wikis are back up.. This incident is actively being investigated.

Edit: sorry the 400 was due to a typo of mine. Reporting_a_connectivity_issue maybe shouldn't use www.wikimedia.org in its example because THAT was still working so I had to change it.

It uses www.wikimedia.org precisely because it rarely involves appservers. These www-URLs are less costly to generate, usually cached internally, and more helpful in diagnosing connectivy issues. If you can reach www.wikimedia.org without issue, then it is not a connectivity issue.

This issue described in this task was due to something server-side that affected some traffic, but was not related your connectivity nor our connectivity.

This was a failure at the edge / caching layer. All services behind it were not directly affected but appeared down / received no traffic. beta cluster was not because it's not in the production environment.

In T308940#7951736, @Dzahn wrote:

https://wikitech.wikimedia.org/wiki/Incidents/2022-05-21_-_varnish_cache_busting

"A flood of API traffic from an AWS user caused caching servers to be overloaded. Services behind those caching servers were up but not reachable during this time."
Just curious:

• A single Amazon Web Services user?
• Could anyone with an Amazon Web Services account repeat this? (I'm not asking what that was as I wouldn't expect an answer to that, only if someone could)
• Does it appear to have been an accidental action (like a malfunctioning spider for example) or was it likely malice?
• If known, how would the AWS user be classified: a (small group of) individual(s), a small/medium business/organization, large business/organization or a (department of) a government?