Bucharest, Romania
“Partial outage”
12 Goue., 14:1057 deiz zo
Não — GitHub está operacional.
Last checked 6 Gwen., 22:54 UTC
Operational
Current status
8.00%
Known uptime
11
Monitored components
O serviço estava operacional. A fonte oficial não relata incidentes ou janelas de manutenção ativas no momento.
0 outage reports in the last 24 hours.
Bucharest, Romania
“Partial outage”
12 Goue., 14:1057 deiz zo
Bucharest, Romania
“Major outage”
11 Goue., 21:5858 deiz zo
Bucharest, Romania
“User reported: Other issue”
11 Goue., 19:3658 deiz zo
Bucharest, Romania
“Degraded performance”
11 Goue., 13:5058 deiz zo
Bucharest, Romania
“Major outage”
22 Mezh., 1:5977 deiz zo
Bucharest, Romania
“Degraded performance”
19 Mezh., 20:5280 deiz zo
Bucharest, Romania
“User reported: Other issue”
19 Mezh., 13:0680 deiz zo
0Compartilhe sua opinião sobre GitHub
Seja o primeiro a comentar!
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 Gwen. 2026, 22:02 UTC · Resolved 4 Gwen. 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 Gwen. 2026, 20:39 UTC · Resolved 4 Gwen. 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 Gwen. 2026, 14:17 UTC · Resolved 3 Gwen. 2026, 17:11 UTC
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started 29 Mae 2025, 21:30 UTC · Resolved 31 Mae 2025, 04:30 UTC
The scheduled maintenance has been completed.
Started 28 Mae 2025, 16:30 UTC · Resolved 29 Mae 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 14 Mae 2025, 16:30 UTC · Resolved 15 Mae 2025, 16:30 UTC
O Uptimus monitora GitHub pela fonte oficial e normaliza incidentes, manutenções e componentes em um status consistente.
Esta página inclui atualmente 11 componentes monitorados, 142 incidentes, 34 manutenções e 50 dias de histórico conhecido.
O Uptimus é um serviço independente e não é afiliado ao GitHub. Um status saudável não garante que todos os usuários, dispositivos ou regiões estejam sem problemas.
Receba alertas quando GitHub ou um componente monitorado informar uma falha grave ou crítica. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas. O histórico disponível contém 142 incidentes indexados e oferece contexto além do status atual. Um incidente recente indexado foi “Degradation in repos contents API”.
Receba alertas sobre desempenho degradado, impacto parcial e incidentes que não representam uma falha completa. O Uptimus monitora atualmente 11 componentes do GitHub: Git Operations, Webhooks, API Requests, Issues. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.
As páginas públicas do Downdetector são orientadas por relatos de usuários. O Uptimus combina essa atividade com incidentes oficiais, manutenções e saúde dos componentes quando o provedor publica esses dados.
| Critérios de comparação | Uptimus | Downdetector |
|---|---|---|
| Relatos da comunidade sobre 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 Gwen. 2026, 15:00 UTC · Resolved 1 Gwen. 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 Eost 2026, 09:15 UTC · Resolved 31 Eost 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 Eost 2026, 10:04 UTC · Resolved 27 Eost 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 Eost 2026, 22:56 UTC · Resolved 27 Eost 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 Eost 2026, 20:40 UTC · Resolved 27 Eost 2026, 00:51 UTC
The scheduled maintenance has been completed.
Started 7 Mae 2025, 16:30 UTC · Resolved 8 Mae 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 21 Ebr. 2025, 16:30 UTC · Resolved 22 Ebr. 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 2 Ebr. 2025, 17:00 UTC · Resolved 3 Ebr. 2025, 17:00 UTC
The scheduled maintenance has been completed.
Started 18 Meur. 2025, 21:00 UTC · Resolved 19 Meur. 2025, 05:00 UTC
The scheduled maintenance has been completed.
Started 28 Cʼhwe. 2025, 17:00 UTC · Resolved 1 Meur. 2025, 02:00 UTC
| Incluído |
| Linha de base adaptativa que separa casos isolados de uma interrupção ampla | Incluído | Incluído |
|---|
| Atividade de 24 horas e visualização regional de interrupções | Incluído | Incluído |
|---|
| Um espaço para sites, provedores de status, jogos Steam e apps e jogos Android | Incluído | Produto separado |
|---|
| Alertas por e-mail, push e webhook no mesmo espaço | Incluído | Produto separado |
|---|
| Atualizações oficiais de incidentes e linha do tempo de GitHub | Incluído | Baseado em relatos |
|---|
| Saúde dos componentes e manutenções exibidas separadamente | Incluído | Limitado nas páginas públicas |
|---|
Rate this service
No reviews yet