Bucharest, Romania
“Partial outage”
12 lug, 14:1057 giorni fa
No — GitHub è operativo.
Last checked 7 set, 23:26 UTC
Operational
Current status
8.00%
Known uptime
11
Monitored components
Il servizio era operativo. La fonte ufficiale non segnala attualmente incidenti o manutenzioni attive.
0 outage reports in the last 24 hours.
Bucharest, Romania
“Partial outage”
12 lug, 14:1057 giorni fa
Bucharest, Romania
“Major outage”
11 lug, 21:5858 giorni fa
Bucharest, Romania
“User reported: Other issue”
11 lug, 19:3658 giorni fa
Bucharest, Romania
“Degraded performance”
11 lug, 13:5058 giorni fa
Bucharest, Romania
“Major outage”
22 giu, 1:5977 giorni fa
Bucharest, Romania
“Degraded performance”
19 giu, 20:5280 giorni fa
Bucharest, Romania
“User reported: Other issue”
19 giu, 13:0680 giorni fa
0Condividi i tuoi pensieri su GitHub
Sii il primo a commentare!
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 set 2026, 22:02 UTC · Resolved 4 set 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 set 2026, 20:39 UTC · Resolved 4 set 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 set 2026, 14:17 UTC · Resolved 3 set 2026, 17:11 UTC
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started 29 mag 2025, 21:30 UTC · Resolved 31 mag 2025, 04:30 UTC
The scheduled maintenance has been completed.
Started 28 mag 2025, 16:30 UTC · Resolved 29 mag 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 14 mag 2025, 16:30 UTC · Resolved 15 mag 2025, 16:30 UTC
Uptimus monitora GitHub tramite la fonte ufficiale e normalizza incidenti, manutenzioni e componenti in uno stato coerente.
Questa pagina include attualmente 11 componenti monitorati, 142 incidenti, 34 manutenzioni e 50 giorni di storico noto.
Uptimus è un servizio indipendente e non è affiliato a GitHub. Uno stato regolare non garantisce che ogni utente, dispositivo o area sia esente da problemi.
Ricevi un avviso quando GitHub o un componente monitorato segnala un'interruzione grave o critica. Gli avvisi possono essere inviati tramite i canali attivi nel workspace, inclusi email, push e integrazioni configurate. La cronologia disponibile contiene 142 incidenti indicizzati e offre un contesto oltre lo stato attuale. Un incidente recente indicizzato è stato «Degradation in repos contents API».
Ricevi avvisi su prestazioni degradate, impatto parziale e incidenti che non rappresentano un'interruzione completa. Uptimus monitora attualmente 11 componenti di GitHub: Git Operations, Webhooks, API Requests, Issues. Gli avvisi possono essere inviati tramite i canali attivi nel workspace, inclusi email, push e integrazioni configurate.
Le pagine pubbliche di Downdetector sono basate soprattutto sulle segnalazioni degli utenti. Uptimus le combina con incidenti ufficiali, manutenzioni e stato dei componenti quando il provider li pubblica.
| Criteri di confronto | Uptimus | Downdetector |
|---|---|---|
| Segnalazioni della community su 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 set 2026, 15:00 UTC · Resolved 1 set 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 ago 2026, 09:15 UTC · Resolved 31 ago 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 ago 2026, 10:04 UTC · Resolved 27 ago 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 ago 2026, 22:56 UTC · Resolved 27 ago 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 ago 2026, 20:40 UTC · Resolved 27 ago 2026, 00:51 UTC
The scheduled maintenance has been completed.
Started 7 mag 2025, 16:30 UTC · Resolved 8 mag 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
| Incluso |
| Baseline adattiva che distingue casi isolati da un’interruzione estesa | Incluso | Incluso |
|---|
| Attività delle ultime 24 ore e visualizzazione regionale | Incluso | Incluso |
|---|
| Un solo spazio per siti, provider di stato, giochi Steam e app e giochi Android | Incluso | Prodotto separato |
|---|
| Avvisi e-mail, push e webhook dallo stesso spazio | Incluso | Prodotto separato |
|---|
| Aggiornamenti ufficiali e cronologia dello stato di GitHub | Incluso | Basato sulle segnalazioni |
|---|
| Stato dei componenti e manutenzioni mostrati separatamente | Incluso | Limitato nelle pagine pubbliche |
|---|
Rate this service
No reviews yet