Site is down again, assumed to be unresolved cause of first outage. Looking into it.
| CARVIEW |
Select Language
HTTP/2 302
server: nginx
date: Wed, 06 Aug 2025 13:45:11 GMT
content-type: text/plain; charset=utf-8
content-length: 0
x-archive-redirect-reason: found capture at 20080705211202
location: https://web.archive.org/web/20080705211202/https://github.wordpress.com/
server-timing: captures_list;dur=0.741605, exclusion.robots;dur=0.024109, exclusion.robots.policy;dur=0.010693, esindex;dur=0.014514, cdx.remote;dur=47.370354, LoadShardBlock;dur=831.534708, PetaboxLoader3.datanode;dur=320.428384, PetaboxLoader3.resolve;dur=378.424693
x-app-server: wwwb-app212
x-ts: 302
x-tr: 926
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0
set-cookie: wb-p-SERVER=wwwb-app212; path=/
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
HTTP/2 200
server: nginx
date: Wed, 06 Aug 2025 13:45:13 GMT
content-type: text/html; charset=UTF-8
x-archive-orig-server: nginx
x-archive-orig-date: Sat, 05 Jul 2008 21:11:59 GMT
x-archive-orig-connection: close
x-archive-orig-x-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
x-archive-orig-x-pingback: https://github.wordpress.com/xmlrpc.php
x-archive-guessed-content-type: text/html
x-archive-guessed-charset: utf-8
memento-datetime: Sat, 05 Jul 2008 21:12:02 GMT
link: GitHub Status
GitHub Status
Latest Updates RSS
-
github 1:38 pm on July 2, 2008 | 0 | # |
-
github 1:30 pm on July 2, 2008 | 0 | # |
We’re currently investigating the downtime we just had. When we know the cause we’ll post.
-
github 3:41 am on June 28, 2008 | 0 | # |
Site’s back up. We’ll be deploying a GFS-related fix real soon now - the site’s stability is our #1 priority.
-
github 3:39 am on June 28, 2008 | 0 | # |
Site’s back up. We’ll be deploying a GFS-related fix real soon now - the site’s stability is our #1 priority.
-
github 3:09 am on June 28, 2008 | 0 | # |
GFS is currently locked, we’re on it.
-
github 5:06 pm on June 25, 2008 | 0 | # |
Okay, we’re back now. Rest assured we’re in the process of re-configuring our GFS and re-architecting the repository storage on disk to make sure these issues stop popping up.
-
github 4:56 pm on June 25, 2008 | 0 | # |
Our GFS system is having problems and the site is unresponsive now. We’re on it.
-
github 11:00 am on June 19, 2008 | 0 | # |
We’ve been having intermittent issues with our GFS all day today. There was no loss of data but the site may have been inaccessible for a few minutes at different times. We’re working on a new architecture to help mitigate these problems before they become worse.
-
github 2:39 pm on June 18, 2008 | 0 | # |
Job Queue Update #2 - the queue is now all caught up thanks to a handful of new workers. The backlog was created when an enormous repository was pushed to GitHub and our existing workers couldn’t keep up. We’re going to keep the extra workers running to prevent this from happening again.
-
github 1:56 pm on June 18, 2008 | 0 | # |
Job Queue Update
We’re still running about 30 minutes behind, but we’ve bumped the priority on new repository creation and fork creation, so those jobs should be handled promptly even with the backlog.
The only things really effected by the delay at this point are the post receive events, such as Campfire hooks.
Recent Projects
-
Blog at WordPress.com
Prologue theme by Automattic