All WordPress.org services are currently…

[RESOLVED] All WordPress.org services are currently offline. We are working with the hosting provider to determine the scope of the problem and how to resolve it.

0043 UTC – This is related to a INAP data center outage in Chicago. They are currently investigating.

0200 UTC – INAP says the root cause is a fiber cut and the ETA is 1-2 hours for partial restoration of services.

0210 UTC – We have updated DNS for wordpress.org, api.wordpress.org, and downloads.wordpress.org so that requests no longer timeout and an error page is returned quickly instead. Hopefully this should prevent slowdowns on WordPress sites checking for auto-updates, etc.

0300 UTC – Network services have been restored to the data center and WordPress.org services are back online.

wordpress.net maintenance/downtime

The server hosting *.wordpress.net will be offline for maintenance starting at 9PM Pacific on Wednesday November 17th. We expect the maintenance to take 6 hours or less.

Between 2000 and 2120 UTC…

UPDATE The switch maintenance is now complete.

UPDATE: Internap has announced a maintenance window starting Saturday May 16 at 2100 CDT to upgrade the software on the affected switches. They believe that the outage was caused by a software problem which is fixed in a more recent release. There should be no downtime as part of this maintenance.

Between 2000 and 2120 UTC today there were some intermittent connectivity issues which affected all of WordPress.org. In some cases this would have resulted in complete unreachability and in other cases it might have meant a 5XX error or higher than normal response time. The underlying cause appears to be a faulty network switch which has since been removed from production and we are working with the hosting provider to identify the exact issue before attempting to return the switch to production.

There was a switch failure which affected some…

There was a switch failure which affected some WordPress.org services between 2300 and 2357 UTC. The WordPress.org website and API were mostly unaffected.