Disruption with Email Delivery
Facts
- Source
- GitHub Status · original
- Started
- (18 h ago)
- Ended
- · lasted 2 h 7 min
- How it ended
- Microsoft marked it resolved.
- First captured by us
- Last changed
- (43 min ago)
Last text from Microsoft
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Quoted from GitHub Status (source), captured . Reproduced for reporting and archival purposes.
Official updates
Posted by GitHub Status, newest first.
Resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Monitoring
We’ve resolved the email-processing impact on our systems and are continuing to monitor. The upstream provider disruption may still cause delays for customers using that provider. Email delivery through other providers is operating normally.
Monitoring
We’re monitoring an email disruption related to an upstream provider degradation. Users whose email is hosted by the affected provider may experience delays in message delivery. Email service for users on other providers is currently operating normally. We’ll share updates as we learn more.
Monitoring
We are seeing recovery for sign-in, email address verification, and other forms of e-mail communication previously impacted. We will continue to monitor.
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Investigating
Users may be unable to sign-in, verify e-mail addresses, reset passwords, or receive e-mail notifications due to degradation with an upstream e-mail provider. We will continue to monitor and provide updates.
Investigating
We are seeing disruptions with email delivery for account sign-in and new account sign up. We are investigating.
Investigating
We are investigating reports of impacted performance for some GitHub services.
What Microsoft changed
Microsoft edits the text of an incident in place. We keep every version we capture (checked every minute) and highlight the difference. Removed text is struck through, added text is marked.
First version we captured
Captured · Microsoft's own timestamp · revisionfc3bmd41Original text as we first saw it
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.