alert

We have resumed Pages builds and will continue to monitor as we process a delayed backlog of events.We have resumed delivery of webhooks and will continue to monitor as we process a delayed backlog of events.We've completed validation of data consistency and have enabled some background jobs. We're continuing to monitor as the system recovers and expect to resume delivering webhooks at 16:45UTC.Background jobs remain paused as we near completion of validation of data consistency.We are validating the consistency of information across all data stores. Webhooks and Pages builds remain paused.The majority of restore processes have completed. We anticipate all data stores will be fully consistent within the next hour.We continue to monitor restores which are taking longer than anticipated. We estimate they will be caught up in an hour and a half.Our restore operations are still on track to serve consistent data within the hour. We've posted an update at https://blog.github.com/2018-10-21-october21-incident-report/.Our restore operations are proceeding as expected, on track for serving fully consistent data within the next 1.5 hours.We are currently in the later stages of a restore operation, with the aim of serving fully consistent data within the next 2 hours.We continue work to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We continue working to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We are continuing work to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We continue working to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We are continuing to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We continue to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We are continuing to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We continue work to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We are continuing to work to migrate a data storage system in order to restore access to GitHub.com.We continue to work to migrate a data storage system in order to restore access to GitHub.com.We continue to migrate a data storage system in order to restore full access to GitHub.com.We continue to work on migrating a data storage system in order to restore access to GitHub.com.We're continuing to work on migrating a data storage system in order to restore access to GitHub.com.We're failing over a data storage system in order to restore access to GitHub.com.

We have resumed Pages builds and will continue to monitor as we process a delayed backlog of events.We have resumed delivery of webhooks and will continue to monitor as we process a delayed backlog of events.We've completed validation of data consistency and have enabled some background jobs. We're continuing to monitor as the system recovers and expect to resume delivering webhooks at 16:45UTC.Background jobs remain paused as we near completion of validation of data consistency.We are validating the consistency of information across all data stores. Webhooks and Pages builds remain paused.The majority of restore processes have completed. We anticipate all data stores will be fully consistent within the next hour.We continue to monitor restores which are taking longer than anticipated. We estimate they will be caught up in an hour and a half.Our restore operations are still on track to serve consistent data within the hour. We've posted an update at https://blog.github.com/2018-10-21-october21-incident-report/.Our restore operations are proceeding as expected, on track for serving fully consistent data within the next 1.5 hours.We are currently in the later stages of a restore operation, with the aim of serving fully consistent data within the next 2 hours.We continue work to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We continue working to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We are continuing work to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We continue working to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We are continuing to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We continue to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We are continuing to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We continue work to repair a data storage system for GitHub.com. You may see inconsistent results during this process.We are continuing to work to migrate a data storage system in order to restore access to GitHub.com.We continue to work to migrate a data storage system in order to restore access to GitHub.com.We continue to migrate a data storage system in order to restore full access to GitHub.com.We continue to work on migrating a data storage system in order to restore access to GitHub.com.We're continuing to work on migrating a data storage system in order to restore access to GitHub.com.We're failing over a data storage system in order to restore access to GitHub.com.