Incident status

• Failed Apache restart

• - varnish cache busting

No incidents reported in the last 14 days.

Create a new incident report

1. Deal with the issue (See also Incident response).
2. Decide whether to write a lightweight or full-length report, and use the below form to start.
   Lightweight report (template):
   
   Full-length report (template):
3. Write up what happened, filling out the template. Use past incident reports for inspiration.
4. Once done, change the status to "in-review", preferably within 7 days of the incident.
   Within 3 weeks the ONFIRE working group will get back to you with feedback.
   After the ONFIRE review and any updates to the report, set the status to "final" and notify the ops@ mailing list.

Past incidents

This page tracks incident reports about Wikimedia Foundation properties, such as Wikipedia.

2022

• 2022-02-01 ulsfo network
• 2022-02-06 wdqs updater
• 2022-02-22 vrts
• 2022-02-22 wdqs updater codfw
• 2022-03-01 ulsfo network
• 2022-03-04 esams availability banner sampling
• 2022-03-06 wdqs-categories
• 2022-03-10 MediaWiki availability
• 2022-03-27 api
• 2022-03-27 wdqs outage
• 2022-03-29 network
• 2022-03-31 api errors
• 2022-04-06 esams network
• 2022-04-26 cr2-eqord down
• 2022-05-01 etcd
• 2022-05-05 Wikimedia full site outage
• 2022-05-21 - varnish cache busting
• 2022-05-24 Failed Apache restart

Incident history

Check Category:Incident documentation for older incident reports.

See also

• https://www.wikimediastatus.net (docs).

• Incident graphs by Krinkle.