Bucharest, Romania
“Partial outage”
12. jul., 14.10for 57 dage siden
Nej — GitHub fungerer normalt.
Last checked 7. sep., 23.26 UTC
Operational
Current status
8.00%
Known uptime
11
Monitored components
Tjenesten var i drift. Den officielle kilde rapporterer ingen aktive hændelser eller vedligeholdelsesvinduer.
0 outage reports in the last 24 hours.
Bucharest, Romania
“Partial outage”
12. jul., 14.10for 57 dage siden
Bucharest, Romania
“Major outage”
11. jul., 21.58for 58 dage siden
Bucharest, Romania
“User reported: Other issue”
11. jul., 19.36for 58 dage siden
Bucharest, Romania
“Degraded performance”
11. jul., 13.50for 58 dage siden
Bucharest, Romania
“Major outage”
22. jun., 1.59for 77 dage siden
Bucharest, Romania
“Degraded performance”
19. jun., 20.52for 80 dage siden
Bucharest, Romania
“User reported: Other issue”
19. jun., 13.06for 80 dage siden
0Del dine tanker om GitHub
Vær den første til at kommentere!
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. sep. 2026, 22.02 UTC · Resolved 4. sep. 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. sep. 2026, 20.39 UTC · Resolved 4. sep. 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. sep. 2026, 14.17 UTC · Resolved 3. sep. 2026, 17.11 UTC
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started 29. maj 2025, 21.30 UTC · Resolved 31. maj 2025, 04.30 UTC
The scheduled maintenance has been completed.
Started 28. maj 2025, 16.30 UTC · Resolved 29. maj 2025, 16.30 UTC
The scheduled maintenance has been completed.
Started 14. maj 2025, 16.30 UTC · Resolved 15. maj 2025, 16.30 UTC
Uptimus overvåger GitHub via den officielle statuskilde og normaliserer hændelser, vedligeholdelse og komponenter til én ensartet status.
Siden indeholder nu 11 komponenter, 142 hændelser, 34 vedligeholdelser og 50 dages kendt historik.
Uptimus er en uafhængig tjeneste og er ikke tilknyttet GitHub. En sund status garanterer ikke, at alle brugere, enheder eller områder er upåvirkede.
Få besked, når GitHub eller en overvåget komponent melder et større eller kritisk nedbrud. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer. Den tilgængelige historik indeholder 142 hændelser og giver mere kontekst end den aktuelle status. En nylig registreret hændelse var “Degradation in repos contents API”.
Få besked om nedsat ydelse, delvis påvirkning og mindre hændelser uden et fuldt nedbrud. Uptimus følger nu 11 GitHub-komponenter: Git Operations, Webhooks, API Requests, Issues. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.
Downdetectors offentlige sider er primært baseret på brugerrapporter. Uptimus kombinerer dem med officielle hændelser, vedligeholdelse og komponentstatus, når udbyderen offentliggør dataene.
| Jämförelsekriterier | Uptimus | Downdetector |
|---|---|---|
| Rapporter fra fællesskabet om 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. sep. 2026, 15.00 UTC · Resolved 1. sep. 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. maj 2025, 16.30 UTC · Resolved 8. maj 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. mar. 2025, 21.00 UTC · Resolved 19. mar. 2025, 05.00 UTC
The scheduled maintenance has been completed.
Started 28. feb. 2025, 17.00 UTC · Resolved 1. mar. 2025, 02.00 UTC
| Inkluderet |
| Adaptiv basislinje, der skelner enkelte rapporter fra større nedbrud | Inkluderet | Inkluderet |
|---|
| Rapportaktivitet over 24 timer og regionalt nedbrudskort | Inkluderet | Inkluderet |
|---|
| Ét arbejdsområde til websites, statusudbydere, Steam-spil og Android-apps og -spil | Inkluderet | Separat produkt |
|---|
| E-mail-, push- og webhookalarmer fra samme arbejdsområde | Inkluderet | Separat produkt |
|---|
| Officielle hændelsesopdateringer og statushistorik for GitHub | Inkluderet | Rapportbaseret |
|---|
| Komponentstatus og vedligeholdelse vises separat | Inkluderet | Begrænset på offentlige sider |
|---|
Rate this service
No reviews yet