Incident on 2017-10-11 15:51:28 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 degraded service affecting GitHub Issues, starting 15:51 UTC on 11 Oct 2017. GitHub marked it resolved at 15:51 UTC after under a minute.
GitHub says
GitHub's latest update, , in short excerpts.
<ul><li><strong>2017-10-11 15:51:28</strong> - We're currently experiencing high replication delay on our primary database cluster.
Timeline
Times in UTC, GitHub's own where it gives them.
11 Oct 2017
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>2017-10-11 15:51:28</strong> - We're currently experiencing high replication delay on our primary database cluster.
Last updated