Bucharest, Romania
“Partial outage”
12. Juli, 14:10vor 57 Tagen
UptimusDienst statusUptimusDienst status
Nein — GitHub ist betriebsbereit.
Last checked 7. Sept., 23:26 UTC
Operational
Current status
8.00%
Known uptime
11
Monitored components
Der Dienst war betriebsbereit. Die offizielle Quelle meldet derzeit keine aktiven Vorfälle oder Wartungsfenster.
0 outage reports in the last 24 hours.
Bucharest, Romania
“Partial outage”
12. Juli, 14:10vor 57 Tagen
Bucharest, Romania
“Major outage”
11. Juli, 21:58vor 58 Tagen
Bucharest, Romania
“User reported: Other issue”
11. Juli, 19:36vor 58 Tagen
Bucharest, Romania
“Degraded performance”
11. Juli, 13:50vor 58 Tagen
Bucharest, Romania
“Major outage”
22. Juni, 1:59vor 77 Tagen
Bucharest, Romania
“Degraded performance”
19. Juni, 20:52vor 80 Tagen
Bucharest, Romania
“User reported: Other issue”
19. Juni, 13:06vor 80 Tagen
0Teilen Sie Ihre Gedanken über GitHub
Seien Sie der Erste, der kommentiert!
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 4. Sept. 2026, 22:02 UTC · Resolved 4. Sept. 2026, 22:23 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 4. Sept. 2026, 20:39 UTC · Resolved 4. Sept. 2026, 22:26 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 3. Sept. 2026, 14:17 UTC · Resolved 3. Sept. 2026, 17:11 UTC
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started 29. Mai 2025, 21:30 UTC · Resolved 31. Mai 2025, 04:30 UTC
The scheduled maintenance has been completed.
Started 28. Mai 2025, 16:30 UTC · Resolved 29. Mai 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 14. Mai 2025, 16:30 UTC · Resolved 15. Mai 2025, 16:30 UTC
Uptimus überwacht GitHub über die offizielle Statusquelle und normalisiert Vorfälle, Wartungen und Komponenten in einen einheitlichen Status.
Diese Seite enthält derzeit 11 überwachte Komponenten, 142 Vorfälle, 34 Wartungen und 50 Tage bekannten Verlauf.
Uptimus ist ein unabhängiger Dienst und nicht mit GitHub verbunden. Ein gesunder Status garantiert nicht, dass alle Nutzer, Geräte oder Regionen unbeeinträchtigt sind.
Erhalte eine Meldung, wenn GitHub oder eine überwachte Komponente einen schweren Ausfall oder eine kritische Störung meldet. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen. Der verfügbare Verlauf enthält 142 erfasste Vorfälle und gibt Meldungen Kontext über den aktuellen Status hinaus. Ein kürzlich erfasster Vorfall war „Degradation in repos contents API“.
Erhalte Meldungen zu Leistungseinbußen, teilweisen Auswirkungen und kleineren Vorfällen ohne vollständigen Ausfall. Uptimus überwacht derzeit 11 GitHub-Komponenten: Git Operations, Webhooks, API Requests, Issues. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen.
Öffentliche Downdetector-Seiten basieren vor allem auf Nutzermeldungen. Uptimus verbindet diese mit offiziellen Vorfällen, Wartungen und Komponentenstatus, sofern der Anbieter sie veröffentlicht.
| Vergleichskriterien | Uptimus | Downdetector |
|---|---|---|
| Community-Störungsmeldungen zu 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 1. Sept. 2026, 15:00 UTC · Resolved 1. Sept. 2026, 16:01 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 31. Aug. 2026, 09:15 UTC · Resolved 31. Aug. 2026, 09:58 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 27. Aug. 2026, 10:04 UTC · Resolved 27. Aug. 2026, 12:12 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 26. Aug. 2026, 22:56 UTC · Resolved 27. Aug. 2026, 00:26 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 26. Aug. 2026, 20:40 UTC · Resolved 27. Aug. 2026, 00:51 UTC
The scheduled maintenance has been completed.
Started 7. Mai 2025, 16:30 UTC · Resolved 8. Mai 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 21. Apr. 2025, 16:30 UTC · Resolved 22. Apr. 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 2. Apr. 2025, 17:00 UTC · Resolved 3. Apr. 2025, 17:00 UTC
The scheduled maintenance has been completed.
Started 18. März 2025, 21:00 UTC · Resolved 19. März 2025, 05:00 UTC
The scheduled maintenance has been completed.
Started 28. Feb. 2025, 17:00 UTC · Resolved 1. März 2025, 02:00 UTC
| Enthalten |
| Adaptive Basislinie zur Trennung einzelner Meldungen von größeren Störungen | Enthalten | Enthalten |
|---|
| 24-Stunden-Meldeaktivität und regionale Störungskarte | Enthalten | Enthalten |
|---|
| Ein Arbeitsbereich für Websites, Statusanbieter, Steam-Spiele und Android-Apps und -Spiele | Enthalten | Separates Produkt |
|---|
| E-Mail-, Push- und Webhook-Alarme aus demselben Arbeitsbereich | Enthalten | Separates Produkt |
|---|
| Offizielle Vorfallmeldungen und Statusverlauf für GitHub | Enthalten | Meldungsbasiert |
|---|
| Komponentenstatus und Wartungsfenster getrennt dargestellt | Enthalten | Auf öffentlichen Seiten begrenzt |
|---|
Entdecken Sie andere beliebte Dienste und ihren aktuellen Status
Rate this service
No reviews yet
