Incident on 2012-07-31 20:45:21 UTC
At a glance · GitHub's status
ResolvedLasted under a minute
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Affects
- GitHub Git operations
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked just now
In short
GitHub reported degraded service affecting GitHub Git operations, starting 20:45 UTC on 31 Jul 2012. GitHub marked it resolved at 20:45 UTC after under a minute.
GitHub says
GitHub's latest update, , in short excerpts.
<ul><li><strong>2012-07-31 20:45:21</strong> - We're investigating elevated failure rates on some of our file servers</li><li><strong>2012-07-31 21:17:20</strong> - We're a bit behind on jobs at the moment.
Timeline
Times in UTC, GitHub's own where it gives them.
31 Jul 2012
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
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 · 1 service
- Status
- resolved
- Services
- GitHub Git operations
Seen by us · GitHub's timestamp · GitHub's page
Affected services
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 ·
<ul><li><strong>2012-07-31 20:45:21</strong> - We're investigating elevated failure rates on some of our file servers</li><li><strong>2012-07-31 21:17:20</strong> - We're a bit behind on jobs at the moment.
Last updated