Incident on 2018-02-02 18:49:59 UTC
At a glance · GitHub's status
ResolvedLasted under a minute
- 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:49 UTC on 2 Feb 2018. GitHub marked it resolved at 18:49 UTC after under a minute.
GitHub says
GitHub's latest update, , in short excerpts.
<ul><li><strong>2018-02-02 18:49:59</strong> - Email delivery is running behind, you may see delays in receiving notifications.</li><li><strong>2018-02-02 19:17:37</strong> - Everything operating normally.</li></ul>
Timeline
Times in UTC, GitHub's own where it gives them.
2 Feb 2018
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
- 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 ·
<ul><li><strong>2018-02-02 18:49:59</strong> - Email delivery is running behind, you may see delays in receiving notifications.</li><li><strong>2018-02-02 19:17:37</strong> - Everything operating normally.</li></ul>
Last updated