UptimusUptimusPublic status
IncidentiSegnalazioniPrezzi
AccediMonitor with Uptimus
HomeIncidentiSegnalazioniPrezziMonitoringSiti webApp mobiliGiochi per cellulariGiochi
AccediMonitor with Uptimus
Status historyRSS updatesStatus API

Powered by Uptimus

    All systems operational

    No — GitHub è operativo.

    Last checked 7 set, 23:26 UTC

    Operational

    Current status

    8.00%

    Known uptime

    11

    Monitored components

    GitHub service health

    Il servizio era operativo. La fonte ufficiale non segnala attualmente incidenti o manutenzioni attive.

    60 giorni fa
    Oggi
    Operativo
    Problemi
    Interruzione
    Manutenzione
    Nessun dato

    GitHub outage reports

    0 outage reports in the last 24 hours.

    Bucharest, Romania

    “Partial outage”

    12 lug, 14:10 · 57 giorni fa

    Bucharest, Romania

    “Major outage”

    11 lug, 21:58 · 58 giorni fa

    Bucharest, Romania

    “User reported: Other issue”

    11 lug, 19:36 · 58 giorni fa

    Bucharest, Romania

    “Degraded performance”

    11 lug, 13:50 · 58 giorni fa

    Bucharest, Romania

    “Major outage”

    22 giu, 1:59 · 77 giorni fa

    Bucharest, Romania

    “Degraded performance”

    19 giu, 20:52 · 80 giorni fa

    Bucharest, Romania

    “User reported: Other issue”

    19 giu, 13:06 · 80 giorni fa

    Discussione comunitaria

    0 · Condividi i tuoi pensieri su GitHub

    Nessun commento ancora

    Sii il primo a commentare!

    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.

    Vedi la mappa completa

    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 set 2026, 22:02 UTC · Resolved 4 set 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 set 2026, 20:39 UTC · Resolved 4 set 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 set 2026, 14:17 UTC · Resolved 3 set 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 mag 2025, 21:30 UTC · Resolved 31 mag 2025, 04:30 UTC

    2. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

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

    3. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

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

    4. ✓

      Codespaces Scheduled Maintenance

    Ricevi una notifica quando cambia lo stato di GitHub

    Inizia il monitoraggio

    Informazioni sul monitoraggio di GitHub su Uptimus

    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.

    Come Uptimus monitora GitHub

    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.

    Uptimus vs Downdetector per GitHub

    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.

    Uptimus vs Downdetector per GitHub
    Criteri di confrontoUptimusDowndetector
    Segnalazioni della community su GitHub

    Domande frequenti

    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 set 2026, 15:00 UTC · Resolved 1 set 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 mag 2025, 16:30 UTC · Resolved 8 mag 2025, 16:30 UTC

  6. ✓

    Codespaces Scheduled Maintenance

    Resolved

    The scheduled maintenance has been completed.

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

  7. ✓

    Scheduled Codespaces Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 2 apr 2025, 17:00 UTC · Resolved 3 apr 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. Notifiche di manutenzione
    Ricevi un avviso quando GitHub pubblica una manutenzione pianificata, programmata o attiva. Uptimus ha indicizzato 34 finestre di manutenzione dalla cronologia disponibile di GitHub. Gli avvisi possono essere inviati tramite i canali attivi nel workspace, inclusi email, push e integrazioni configurate.
    Notifiche di ripristino
    Scopri quando GitHub o un componente interessato torna a funzionare correttamente. La pagina contiene 50 giorni di cronologia nota e conserva gli eventi risolti per la revisione. Gli avvisi possono essere inviati tramite i canali attivi nel workspace, inclusi email, push e integrazioni configurate.
    Messaggi di stato
    Uptimus conserva il titolo dell'incidente pubblicato da GitHub e lo mostra con lo stato normalizzato. 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».
    Dettagli dello stato
    Gli aggiornamenti di incidenti e manutenzioni vengono conservati per seguire indagini, mitigazioni e ripristino. Un recente aggiornamento ufficiale conservato da 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.».
    Filtro dei componenti
    Scegli tutti i componenti o solo i prodotti GitHub utilizzati. Gli avvisi ufficiali rispettano la selezione. Uptimus monitora attualmente 11 componenti di GitHub: Git Operations, Webhooks, API Requests, Issues. Il filtro modifica gli avvisi ufficiali consegnati, ma non rimuove gli eventi dalla cronologia pubblica.
    Incluso
    Incluso
    Baseline adattiva che distingue casi isolati da un’interruzione estesaInclusoIncluso
    Attività delle ultime 24 ore e visualizzazione regionaleInclusoIncluso
    Un solo spazio per siti, provider di stato, giochi Steam e app e giochi AndroidInclusoProdotto separato
    Avvisi e-mail, push e webhook dallo stesso spazioInclusoProdotto separato
    Aggiornamenti ufficiali e cronologia dello stato di GitHubInclusoBasato sulle segnalazioni
    Stato dei componenti e manutenzioni mostrati separatamenteInclusoLimitato nelle pagine pubbliche
    InclusoBasato sulle segnalazioni · Limitato nelle pagine pubblicheProdotto separato

    Più servizi da monitorare

    Scopri altri servizi popolari e il loro stato attuale

    Sfoglia tutti i servizi
    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 di una revisione al mese)

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