W3C Outage History

W3C is up right now

Pingoru has recorded 26 incidents for W3C: 3 in the last 12 months and 0 in the last 90 days.

Source: status.w3.org

26incidents recorded
3last 12 months
0last 90 days
9 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking W3C in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202612 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 516 (0%)

Incidents, newest first

Major June 29, 2026 Authentication server not responding 1h 45m Website

Started Jun 29, 2026, 10:36 AM UTC· resolved Jun 29, 2026, 12:22 PM UTC

  1. investigating Jun 29, 2026, 10:36 AM UTC

    Our main authentication server (https://auth.w3.org) is currently unresponsive. We are investigating the issue.

  2. identified Jun 29, 2026, 10:54 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 29, 2026, 11:05 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 29, 2026, 12:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 16, 2026 Authentication System Incident 1d 2h Website, User & Group Management, TR Publication, Email & Mailing Lists and 5 more

Started Feb 16, 2026, 10:50 AM UTC· resolved Feb 17, 2026, 12:58 PM UTC

  1. monitoring Feb 16, 2026, 10:50 AM UTC

    We are currently experiencing an issue with our authentication system that is impacting all our services. We have identified the issue and are actively working on fixing it. During this time, existing sessions may intermittently fail, and new authentication attempts may be unsuccessful. We appreciate your patience and understanding while we work to resolve this matter.

  2. monitoring Feb 16, 2026, 10:51 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Feb 16, 2026, 05:01 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 17, 2026, 12:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 5, 2025 503 on www.w3.org 21m Website, User & Group Management, TR Publication, Email & Mailing Lists and 3 more

Started Dec 05, 2025, 09:07 AM UTC· resolved Dec 05, 2025, 09:28 AM UTC

  1. investigating Dec 05, 2025, 09:07 AM UTC

    We are currently investigating this issue.

  2. investigating Dec 05, 2025, 09:08 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Dec 05, 2025, 09:20 AM UTC

    Our website has been affected by a cloudflare issue. It is now back.

  4. resolved Dec 05, 2025, 09:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 6, 2025 Several services unavailable 1h 39m

Started Sep 06, 2025, 01:35 PM UTC· resolved Sep 06, 2025, 03:15 PM UTC

  1. investigating Sep 06, 2025, 01:35 PM UTC

    Some servers are currently experiencing problems which impacts several W3C services including wiki, Member pages, wbs. We are looking at the issue.

  2. resolved Sep 06, 2025, 03:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 20, 2024 Mailing list server temporarily unavailable 13m Email & Mailing Lists

Started Dec 20, 2024, 06:04 PM UTC· resolved Dec 20, 2024, 06:18 PM UTC

  1. investigating Dec 20, 2024, 06:04 PM UTC

    We are currently investigating this issue.

  2. resolved Dec 20, 2024, 06:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 5, 2024 spec-generator is timing out 17h 57m

Started Dec 05, 2024, 02:19 PM UTC· resolved Dec 06, 2024, 08:16 AM UTC

  1. identified Dec 05, 2024, 02:19 PM UTC

    A recent upgrade of the spec-generator dependencies is causing timeouts when generating document snapshots. A fix is in progress.

  2. resolved Dec 06, 2024, 08:16 AM UTC

    This incident has been resolved.

Read the full incident report →