W3C incident

Several services unavailable

Critical Resolved View vendor source →

W3C experienced a critical incident on February 28, 2022 affecting TR Publication and API and 1 more component, lasting 1d 20h. The incident has been resolved; the full update timeline is below.

Started
Feb 28, 2022, 01:31 PM UTC
Resolved
Mar 02, 2022, 10:08 AM UTC
Duration
1d 20h
Detected by Pingoru
Feb 28, 2022, 01:31 PM UTC

Affected components

TR PublicationAPIValidation Services

Update timeline

  1. identified Feb 28, 2022, 01:31 PM UTC

    A proxy server is currently experiencing performance issues which impacts several W3C services including the W3C Validators, the W3C API, the automated publications with echidna and services hosted under labs.w3.org. We have informed our hosting provider who is looking at this issue.

  2. identified Feb 28, 2022, 01:34 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Feb 28, 2022, 08:59 PM UTC

    A DDoS attack using validator services is currently in progress. Mitigations have been put in place to block offenders and limit its impact. The affected services are back and we continue to monitor them. Please note that while the attack is still ongoing, service performance might be reduced.

  4. monitoring Mar 02, 2022, 10:07 AM UTC

    The W3C API and services under labs.w3.org have been moved to a separate proxy server. Those services are now fully operational. W3C Validators continue to receive a lot of incoming traffic but the mitigations that have been put in place have been beneficial. Please note that W3C validators are now available exclusively over HTTPS.

  5. resolved Mar 02, 2022, 10:08 AM UTC

    This incident has been resolved.