Incident on 2011-01-28 22:18:00 UTC
At a glance · GitHub's status
ResolvedLasted under a minute
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Affects
- GitHub Issues
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked just now
In short
GitHub reported a partial outage affecting GitHub Issues, starting 22:18 UTC on 28 Jan 2011. GitHub marked it resolved at 22:18 UTC after under a minute.
GitHub says
GitHub's latest update, , in short excerpts.
<ul><li><strong>2011-01-28 22:18:00</strong> - Experiencing high DB load currently.
Timeline
Times in UTC, GitHub's own where it gives them.
28 Jan 2011
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 Issues
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>2011-01-28 22:18:00</strong> - Experiencing high DB load currently.
Last updated