Who is down right now

20 down now · 248 this week

GitHub · Developer toolsMar 24, 2026, 16:59 UTC 7 months ago

Teams Github Notifications App is down

MajorNot disclosedUpdated 42d ago
Mar 24, 16:59 UTCMar 24, 19:51 UTC
Duration
2h 52m
Impact
Major
Root cause
Not disclosed
GitHub, 90 days
69 incidents
Affected
Not listed by the vendor.

Lesson: Engineering organizations should adopt AI and automation to solve DevSecOps challenges and maintain high availability across distributed services.

What happened

On March 24, 2026, between 15:57 UTC and 19:51 UTC, the Microsoft Teams Integration and Teams Copilot Integration services were degraded and unable to deliver GitHub event notifications to Microsoft Teams. On average, the error rate was 37.4% and peaked at 90.1% of requests to the service -- approximately 19% of all integration installs failed to receive GitHub-to-Teams notifications in this time period. This was due to an outage at one of our upstream dependencies, which caused HTTP 500 errors and connection resets for our Teams integration. We coordinated with the relevant service teams, and the issue was resolved at 19:51 UTC when the upstream incident was mitigated. We are working to update observability and runbooks to reduce time to mitigation for issues like this in the future.

Timeline

  1. Resolved · Mar 24, 19:51 UTC
    On March 24, 2026, between 15:57 UTC and 19:51 UTC, the Microsoft Teams Integration and Teams Copilot Integration services were degraded and unable to deliver GitHub event notifications to Microsoft Teams. On average, the error rate was 37.4% and peaked at 90.1% of requests to the service -- approximately 19% of all integration installs failed to receive GitHub-to-Teams notifications in this time period. This was due to an outage at one of our upstream dependencies, which caused HTTP 500 errors and connection resets for our Teams integration. We coordinated with the relevant service teams, and the issue was resolved at 19:51 UTC when the upstream incident was mitigated. We are working to update observability and runbooks to reduce time to mitigation for issues like this in the future.

More from GitHub

Full history