UptimusUptimusServico status
IncidentesRelatóriosPreços
EntrarMonitor with Uptimus
InícioIncidentesRelatóriosPreçosMonitoringSitesAplicativos móveisJogos para celularJogos
EntrarMonitor with Uptimus
Status historyRSS updatesStatus API

Powered by Uptimus

    All systems operational

    Não — GitHub está operacional.

    Last checked 6 Gwen., 22:54 UTC

    Operational

    Current status

    8.00%

    Known uptime

    11

    Monitored components

    GitHub service health

    O serviço estava operacional. A fonte oficial não relata incidentes ou janelas de manutenção ativas no momento.

    Há 60 dias
    Hoje
    Operacional
    Problemas
    Indisponibilidade
    Manutenção
    Sem dados

    GitHub outage reports

    0 outage reports in the last 24 hours.

    Bucharest, Romania

    “Partial outage”

    12 Goue., 14:10 · 57 deiz zo

    Bucharest, Romania

    “Major outage”

    11 Goue., 21:58 · 58 deiz zo

    Bucharest, Romania

    “User reported: Other issue”

    11 Goue., 19:36 · 58 deiz zo

    Bucharest, Romania

    “Degraded performance”

    11 Goue., 13:50 · 58 deiz zo

    Bucharest, Romania

    “Major outage”

    22 Mezh., 1:59 · 77 deiz zo

    Bucharest, Romania

    “Degraded performance”

    19 Mezh., 20:52 · 80 deiz zo

    Bucharest, Romania

    “User reported: Other issue”

    19 Mezh., 13:06 · 80 deiz zo

    Discussão da comunidade

    0 · Compartilhe sua opinião sobre GitHub

    Ainda não há comentários

    Seja o primeiro a comentar!

    System status

    Official component health and availability history.

    11 tracked components

    90 days ago → Today

    GitHub outage map

    Geographic clusters from community-submitted reports.

    Regional activity

    See where reports are coming from

    Explore report activity by country and quickly identify regional service disruptions.

    Ver mapa completo

    Past incidents

    Official updates and resolved service disruptions.

    1. ✓

      Degradation in repos contents API

      Resolved

      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

    2. ✓

      Disruption with Copilot Code Review

      Resolved

      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

    3. ✓

      Incident with Grok Copilot AI Model Provider

      Resolved

      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

    Scheduled maintenance

    Planned work published by the official provider.

    1. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 29 Mae 2025, 21:30 UTC · Resolved 31 Mae 2025, 04:30 UTC

    2. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 28 Mae 2025, 16:30 UTC · Resolved 29 Mae 2025, 16:30 UTC

    3. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 14 Mae 2025, 16:30 UTC · Resolved 15 Mae 2025, 16:30 UTC

    4. ✓

      Codespaces Scheduled Maintenance

    Receba notificações quando o status de GitHub mudar

    Iniciar monitoramento

    Sobre o monitoramento de GitHub no Uptimus

    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.

    Como o Uptimus monitora GitHub

    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.

    Uptimus vs Downdetector para GitHub

    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.

    Uptimus vs Downdetector para GitHub
    Critérios de comparaçãoUptimusDowndetector
    Relatos da comunidade sobre GitHub

    Perguntas frequentes

    Services

    1. Git OperationsPerformance of git clones, pulls, pushes, and associated operationsHealthy
    2. WebhooksReal time HTTP callbacks of user-generated and system eventsHealthy
    3. API RequestsRequests for GitHub APIsHealthy
    4. IssuesRequests for Issues on GitHub.comHealthy
    5. Pull RequestsRequests for Pull Requests on GitHub.comHealthy
    6. ActionsWorkflows, Compute and Orchestration for GitHub ActionsHealthy
    7. PackagesAPI requests and webhook delivery for GitHub PackagesHealthy
    8. PagesFrontend application and API servers for Pages buildsHealthy
    9. CopilotHealthy
    10. CodespacesOrchestration and Compute for GitHub CodespacesHealthy
    11. Copilot AI Model ProvidersHealthy
    ✓

    Delays in commit processing

    Resolved

    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

  1. ✓

    Elevated rate of errors for OpenAI models provided by Copilot

    Resolved

    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

  2. ✓

    Incident with Copilot AI Model Providers

    Resolved

    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

  3. ✓

    Incident with Actions and Pull Requests

    Resolved

    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

  4. ✓

    Disruption with GitHub Billing

    Resolved

    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

  5. Resolved

    The scheduled maintenance has been completed.

    Started 7 Mae 2025, 16:30 UTC · Resolved 8 Mae 2025, 16:30 UTC

  6. ✓

    Codespaces Scheduled Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 21 Ebr. 2025, 16:30 UTC · Resolved 22 Ebr. 2025, 16:30 UTC

  7. ✓

    Scheduled Codespaces Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 2 Ebr. 2025, 17:00 UTC · Resolved 3 Ebr. 2025, 17:00 UTC

  8. ✓

    Scheduled Migrations Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 18 Meur. 2025, 21:00 UTC · Resolved 19 Meur. 2025, 05:00 UTC

  9. ✓

    Scheduled Codespaces Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 28 Cʼhwe. 2025, 17:00 UTC · Resolved 1 Meur. 2025, 02:00 UTC

  10. Notificações de manutenção
    Receba alertas quando GitHub publicar manutenção planejada, programada ou ativa. O Uptimus indexou 34 janelas de manutenção do histórico disponível do GitHub. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.
    Notificações de recuperação
    Saiba quando GitHub ou um componente afetado voltar ao funcionamento saudável. A página contém 50 dias de histórico conhecido e mantém eventos resolvidos para análise. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.
    Mensagens de status
    O Uptimus armazena o título do incidente publicado por GitHub e o mostra com o status normalizado. 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”.
    Detalhes do status
    As atualizações de incidentes e manutenção são preservadas para acompanhar investigação, mitigação e recuperação. Uma atualização oficial recente preservada pelo Uptimus diz: “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.”.
    Filtro de componentes
    Escolha todos os componentes ou apenas os produtos GitHub usados. Os alertas oficiais respeitam essa seleção. O Uptimus monitora atualmente 11 componentes do GitHub: Git Operations, Webhooks, API Requests, Issues. O filtro altera os alertas oficiais entregues, mas não remove eventos do histórico público.
    Incluído
    Incluído
    Linha de base adaptativa que separa casos isolados de uma interrupção amplaIncluídoIncluído
    Atividade de 24 horas e visualização regional de interrupçõesIncluídoIncluído
    Um espaço para sites, provedores de status, jogos Steam e apps e jogos AndroidIncluídoProduto separado
    Alertas por e-mail, push e webhook no mesmo espaçoIncluídoProduto separado
    Atualizações oficiais de incidentes e linha do tempo de GitHubIncluídoBaseado em relatos
    Saúde dos componentes e manutenções exibidas separadamenteIncluídoLimitado nas páginas públicas
    IncluídoBaseado em relatos · Limitado nas páginas públicasProduto separado

    Mais serviços para monitorar

    Descubra outros serviços populares e seu status atual

    Navegue por todos os serviços
    WOW!Getting Over It with Bennett FoddyArch - AI Home Design

    Rate this service

    How would you rate GitHub over the last month?

    No reviews yet

    (Limite de uma revisão por mês)

    Backspin Games: Win Real Money
    Pulumi
    Kickbox
    Blanco
    Flickr
    Shipcloud
    Mongodb
    Specops
    Make