Incident on 2019-10-22 18:51 UTC
At a glance · GitHub's status
ResolvedLasted 3 h 39 min
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked just now
In short
GitHub reported degraded service affecting GitHub, starting 18:51 UTC on 22 Oct 2019. GitHub marked it resolved at 22:31 UTC after 3 h 39 min.
GitHub says
GitHub's latest update, , in short excerpts.
This incident has been resolved.
Timeline
Times in UTC, GitHub's own where it gives them.
22 Oct 2019
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+3 h 40 min
GitHubResolved
What GitHub changed
GitHub adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on GitHub's page.
One version so far. If GitHub edits it, each change shows here with what was removed and added.
First version we captured ·
As first seen: resolved
- Status
- resolved
Seen by us · GitHub's timestamp · GitHub's page
Official updates
Posted by GitHub Status, newest first. The newest are quoted in their first sentence; the full text of each is on GitHub's page.
Resolved ·
This incident has been resolved.
Investigating ·
We continue to monitor recovery.
Investigating ·
We are aware of the cause of the degradation and are monitoring its recovery.
Investigating ·
We are continuing to investigate degradation with webhook delivery logs, attachments and git lfs.
Investigating ·
We continue to investigate git lfs, attachments and webhook delivery log degradation.
Investigating ·
Some users are experiencing issues with git lfs, webhook delivery logs and attachments.
Investigating ·
Some users are experiencing issues with uploading attachments and with webhook delivery logs.
Last updated