UptimusUptimusPublic status
IncidentesReportesPrecios
Iniciar SesiónMonitor with Uptimus
InicioIncidentesReportesPreciosMonitoringSitios WebAplicaciones MóvilesJuegos MóvilesJuegos
Iniciar SesiónMonitor with Uptimus
Status historyRSS updatesStatus API

Powered by Uptimus

    All systems operational

    No — GitHub está operativo.

    Last checked 7 sept, 23:26 UTC

    Operational

    Current status

    8.00%

    Known uptime

    11

    Monitored components

    GitHub service health

    El servicio estaba operativo. La fuente oficial no informa actualmente de incidencias ni mantenimientos activos.

    Hace 60 días
    Hoy
    Operativo
    Problemas
    Interrupción
    Mantenimiento
    Sin datos

    GitHub outage reports

    0 outage reports in the last 24 hours.

    Bucharest, Romania

    “Partial outage”

    12 jul, 14:10 · hace 57 días

    Bucharest, Romania

    “Major outage”

    11 jul, 21:58 · hace 58 días

    Bucharest, Romania

    “User reported: Other issue”

    11 jul, 19:36 · hace 58 días

    Bucharest, Romania

    “Degraded performance”

    11 jul, 13:50 · hace 58 días

    Bucharest, Romania

    “Major outage”

    22 jun, 1:59 · hace 77 días

    Bucharest, Romania

    “Degraded performance”

    19 jun, 20:52 · hace 80 días

    Bucharest, Romania

    “User reported: Other issue”

    19 jun, 13:06 · hace 80 días

    Discusión de la Comunidad

    0 · Comparte tus pensamientos sobre GitHub

    Aún no hay comentarios

    ¡Sé el primero en 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 sept 2026, 22:02 UTC · Resolved 4 sept 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 sept 2026, 20:39 UTC · Resolved 4 sept 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 sept 2026, 14:17 UTC · Resolved 3 sept 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 may 2025, 21:30 UTC · Resolved 31 may 2025, 04:30 UTC

    2. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

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

    3. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

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

    4. ✓

      Codespaces Scheduled Maintenance

    Recibe notificaciones cuando cambie el estado de GitHub

    Empezar a monitorizar

    Acerca de la supervisión de GitHub en Uptimus

    Uptimus supervisa GitHub mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.

    Esta página incluye actualmente 11 componentes supervisados, 142 incidencias, 34 mantenimientos y 50 días de historial conocido.

    Uptimus es un servicio independiente y no está afiliado con GitHub. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.

    Cómo supervisa Uptimus GitHub

    Recibe alertas cuando GitHub o uno de sus componentes supervisados informa de una interrupción grave o crítica. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas. El historial disponible contiene 142 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Degradation in repos contents API».

    Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 11 componentes de GitHub: Git Operations, Webhooks, API Requests, Issues. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.

    Uptimus vs Downdetector para GitHub

    Las páginas públicas de Downdetector se centran en los reportes de usuarios. Uptimus combina esa actividad con incidentes oficiales, mantenimientos y salud de componentes cuando el proveedor los publica.

    Uptimus vs Downdetector para GitHub
    Criterios de comparaciónUptimusDowndetector
    Reportes de la comunidad sobre GitHub

    Preguntas Frecuentes

    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 sept 2026, 15:00 UTC · Resolved 1 sept 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 ago 2026, 09:15 UTC · Resolved 31 ago 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 ago 2026, 10:04 UTC · Resolved 27 ago 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 ago 2026, 22:56 UTC · Resolved 27 ago 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 ago 2026, 20:40 UTC · Resolved 27 ago 2026, 00:51 UTC

  5. Resolved

    The scheduled maintenance has been completed.

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

  6. ✓

    Codespaces Scheduled Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 21 abr 2025, 16:30 UTC · Resolved 22 abr 2025, 16:30 UTC

  7. ✓

    Scheduled Codespaces Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 2 abr 2025, 17:00 UTC · Resolved 3 abr 2025, 17:00 UTC

  8. ✓

    Scheduled Migrations Maintenance

    Resolved

    The scheduled maintenance has been completed.

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

  9. ✓

    Scheduled Codespaces Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 28 feb 2025, 17:00 UTC · Resolved 1 mar 2025, 02:00 UTC

  10. Notificaciones de mantenimiento
    Recibe alertas cuando GitHub publica mantenimiento planificado, programado o activo. Uptimus ha indexado 34 ventanas de mantenimiento del historial disponible de GitHub. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
    Notificaciones de recuperación
    Entérate cuando GitHub o un componente afectado vuelve a funcionar correctamente. La página contiene 50 días de historial conocido y conserva los eventos resueltos para su revisión. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
    Mensajes de estado
    Uptimus conserva el título de la incidencia publicado por GitHub y lo muestra con el estado normalizado. El historial disponible contiene 142 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Degradation in repos contents API».
    Detalles del estado
    Las actualizaciones de incidencias y mantenimiento se conservan para seguir la investigación, mitigación y recuperación. Una actualización oficial reciente conservada por Uptimus dice: «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.».
    Filtrado de componentes
    Elige todos los componentes o solo los productos de GitHub que utilizas. Las alertas oficiales respetan esa selección. Uptimus supervisa actualmente 11 componentes de GitHub: Git Operations, Webhooks, API Requests, Issues. El filtrado modifica las alertas oficiales entregadas, pero no elimina los eventos del historial público.
    Incluido
    Incluido
    Línea base adaptativa que separa casos aislados de una interrupción ampliaIncluidoIncluido
    Actividad de reportes de 24 horas y vista regional de interrupcionesIncluidoIncluido
    Un espacio para sitios web, proveedores de estado, juegos de Steam y aplicaciones y juegos AndroidIncluidoProducto separado
    Alertas por correo, push y webhook desde el mismo espacioIncluidoProducto separado
    Actualizaciones oficiales de incidentes y cronología de GitHubIncluidoBasado en reportes
    Salud de componentes y mantenimientos mostrados por separadoIncluidoLimitado en páginas públicas
    IncluidoBasado en reportes · Limitado en páginas públicasProducto separado

    Más servicios para monitorear

    Descubre otros servicios populares y su estado actual

    Ver todos los servicios
    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

    (Límite de una reseña por mes)

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