Bucharest, Romania
“Partial outage”
Jul 12, 2:10 PMabout 57 days ago
UptimusGitHub statusUptimusGitHub status
No — GitHub is operational.
Last checked Sep 6, 02:24 PM UTC
Operational
Current status
8.00%
Known uptime
11
Monitored components
The service was operational. The official source currently reports no active incidents or maintenance windows.
0 outage reports in the last 24 hours.
Bucharest, Romania
“Partial outage”
Jul 12, 2:10 PMabout 57 days ago
Bucharest, Romania
“Major outage”
Jul 11, 9:58 PMabout 58 days ago
Bucharest, Romania
“User reported: Other issue”
Jul 11, 7:36 PMabout 58 days ago
Bucharest, Romania
“Degraded performance”
Jul 11, 1:50 PMabout 58 days ago
Bucharest, Romania
“Major outage”
Jun 22, 1:59 AMabout 77 days ago
Bucharest, Romania
“Degraded performance”
Jun 19, 8:52 PMabout 80 days ago
Bucharest, Romania
“User reported: Other issue”
Jun 19, 1:06 PMabout 80 days ago
0Share your thoughts about GitHub
Be the first to comment!
Official component health and availability history.
11 tracked components
90 days ago → Today
Geographic clusters from community-submitted reports.
Official updates and resolved service disruptions.
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.
Started Sep 4, 2026, 10:02 PM UTC · Resolved Sep 4, 2026, 10:23 PM UTC
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.
Started Sep 4, 2026, 08:39 PM UTC · Resolved Sep 4, 2026, 10:26 PM UTC
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.
Started Sep 3, 2026, 02:17 PM UTC · Resolved Sep 3, 2026, 05:11 PM UTC
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started May 29, 2025, 09:30 PM UTC · Resolved May 31, 2025, 04:30 AM UTC
The scheduled maintenance has been completed.
Started May 28, 2025, 04:30 PM UTC · Resolved May 29, 2025, 04:30 PM UTC
The scheduled maintenance has been completed.
Started May 14, 2025, 04:30 PM UTC · Resolved May 15, 2025, 04:30 PM UTC
Uptimus monitors GitHub through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.
This page currently includes 11 monitored components, 142 indexed incidents, 34 maintenance windows and 50 days of known history.
Uptimus is an independent monitoring service and is not affiliated with GitHub. A healthy status does not guarantee that every user, device or region is unaffected.
Get notified when GitHub or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 142 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “Degradation in repos contents API”.
Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 11 GitHub components: Git Operations, Webhooks, API Requests, Issues. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.
| Comparison criteria | Uptimus | Downdetector |
|---|---|---|
| Community outage reports for GitHub |
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.
Started Sep 1, 2026, 03:00 PM UTC · Resolved Sep 1, 2026, 04:01 PM UTC
Between 08:37 and 09:41 UTC on August 31, 2026, GitHub Copilot experienced degradation affecting several GPT models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4-mini, gpt-5.4-nano, and the gpt-5.6 family (Luna, Sol, and Terra). Users encountered elevated error rates and interrupted streaming responses. Other models were not affected. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.
Started Aug 31, 2026, 09:15 AM UTC · Resolved Aug 31, 2026, 09:58 AM UTC
On August 27th, 2026, between approximately 09:20 and 12:14 UTC, the Copilot service experienced a degradation of the Kimi K3 model due to an issue with our upstream provider. Users encountered elevated error rates when using Kimi K3. No other models were impacted. The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.
Started Aug 27, 2026, 10:04 AM UTC · Resolved Aug 27, 2026, 12:12 PM UTC
On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information. We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations. We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our systems more resilient under load.
Started Aug 26, 2026, 10:56 PM UTC · Resolved Aug 27, 2026, 12:26 AM UTC
On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI sessions. We confirmed this impact for a small number of customers (<1%). This was caused by a concentrated workload that created processing delays in our data storage layer. Automated retries increased the load and prolonged the degradation. We mitigated the incident by rebalancing traffic within our infrastructure. We are improving workload isolation, retry behavior, and detection of concentrated load to reduce the likelihood of recurrence and shorten our time to detect and mitigate similar incidents.
Started Aug 26, 2026, 08:40 PM UTC · Resolved Aug 27, 2026, 12:51 AM UTC
The scheduled maintenance has been completed.
Started May 7, 2025, 04:30 PM UTC · Resolved May 8, 2025, 04:30 PM UTC
The scheduled maintenance has been completed.
Started Apr 21, 2025, 04:30 PM UTC · Resolved Apr 22, 2025, 04:30 PM UTC
The scheduled maintenance has been completed.
Started Apr 2, 2025, 05:00 PM UTC · Resolved Apr 3, 2025, 05:00 PM UTC
The scheduled maintenance has been completed.
Started Mar 18, 2025, 09:00 PM UTC · Resolved Mar 19, 2025, 05:00 AM UTC
The scheduled maintenance has been completed.
Started Feb 28, 2025, 05:00 PM UTC · Resolved Mar 1, 2025, 02:00 AM UTC
| Included |
| Adaptive baseline that separates isolated reports from wider disruption | Included | Included |
|---|
| 24-hour report activity and regional outage view | Included | Included |
|---|
| One workspace for websites, provider status pages, Steam games and Android apps and games | Included | Separate product |
|---|
| Email, push and webhook alerts from the same workspace | Included | Separate product |
|---|
| Official incident updates and status timeline for GitHub | Included | User-report led |
|---|
| Component health and maintenance windows kept separate | Included | Limited on public pages |
|---|
Rate this service
No reviews yet
Discover other popular services and their current status
