UptimusUptimusServiciu status
IncidenteRapoartePrețuri
AutentificareMonitor with Uptimus
AcasăIncidenteRapoartePrețuriMonitoringSite-uri WebAplicații MobileJocuri MobileJocuri
AutentificareMonitor with Uptimus
Status historyRSS updatesStatus API

Powered by Uptimus

    All systems operational

    Nu — GitHub este operațional.

    Last checked 7 sept., 23:26 UTC

    Operational

    Current status

    8.00%

    Known uptime

    11

    Monitored components

    GitHub service health

    Serviciul funcționa normal. Sursa oficială nu raportează în prezent incidente sau ferestre de mentenanță active.

    Acum 60 de zile
    Azi
    Operațional
    Probleme
    Întrerupere
    Mentenanță
    Fără date

    GitHub outage reports

    0 outage reports in the last 24 hours.

    Bucharest, Romania

    “Partial outage”

    12 iul., 14:10 · acum 57 de zile

    Bucharest, Romania

    “Major outage”

    11 iul., 21:58 · acum 58 de zile

    Bucharest, Romania

    “User reported: Other issue”

    11 iul., 19:36 · acum 58 de zile

    Bucharest, Romania

    “Degraded performance”

    11 iul., 13:50 · acum 58 de zile

    Bucharest, Romania

    “Major outage”

    22 iun., 1:59 · acum 77 de zile

    Bucharest, Romania

    “Degraded performance”

    19 iun., 20:52 · acum 80 de zile

    Bucharest, Romania

    “User reported: Other issue”

    19 iun., 13:06 · acum 80 de zile

    Discuție Comunitate

    0 · Împărtășește-ți gândurile despre GitHub

    Încă nu există comentarii

    Fii primul care comentează!

    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.

    Vezi harta completă

    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 mai 2025, 21:30 UTC · Resolved 31 mai 2025, 04:30 UTC

    2. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

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

    3. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

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

    4. ✓

      Codespaces Scheduled Maintenance

    Află primul când GitHub nu funcționează

    Începe monitorizarea

    Despre monitorizarea GitHub pe Uptimus

    Uptimus monitorizează GitHub prin sursa oficială de status și normalizează incidentele, ferestrele de mentenanță și starea componentelor într-un status unitar.

    Această pagină include în prezent 11 componente monitorizate, 142 incidente indexate, 34 ferestre de mentenanță și 50 zile de istoric cunoscut.

    Uptimus este un serviciu independent și nu este afiliat cu GitHub. Un status sănătos nu garantează că fiecare utilizator, dispozitiv sau regiune este neafectată.

    Cum monitorizează Uptimus GitHub

    Primești notificări când GitHub sau una dintre componentele monitorizate raportează o întrerupere majoră ori o problemă critică. Alertele pot fi trimise prin canalele activate în workspace, inclusiv email, push și integrările configurate. Istoricul disponibil conține 142 incidente indexate, oferind fiecărei alerte context dincolo de statusul actual. Un incident recent indexat a fost „Degradation in repos contents API”.

    Primești alerte despre performanță degradată, impact parțial și incidente mai mici care nu reprezintă o întrerupere completă. Uptimus monitorizează în prezent 11 componente GitHub: Git Operations, Webhooks, API Requests, Issues. Alertele pot fi trimise prin canalele activate în workspace, inclusiv email, push și integrările configurate.

    Uptimus vs Downdetector pentru GitHub

    Paginile publice Downdetector se bazează în principal pe rapoartele utilizatorilor. Uptimus combină activitatea comunității cu incidentele oficiale, ferestrele de mentenanță și starea componentelor atunci când sursa le publică.

    Uptimus vs Downdetector pentru GitHub
    Criterii de comparațieUptimusDowndetector
    Rapoarte comunitare despre problemele GitHub

    Întrebări firești, răspunsuri clare.

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

  5. Resolved

    The scheduled maintenance has been completed.

    Started 7 mai 2025, 16:30 UTC · Resolved 8 mai 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. Notificări de mentenanță
    Primești alerte când GitHub publică o mentenanță planificată, programată sau activă care afectează serviciul. Uptimus a indexat 34 ferestre de mentenanță din istoricul GitHub disponibil. Alertele pot fi trimise prin canalele activate în workspace, inclusiv email, push și integrările configurate.
    Notificări de recuperare
    Afli când GitHub sau o componentă afectată revine la o funcționare sănătoasă după o problemă ori întrerupere. Pagina conține 50 zile de istoric cunoscut, iar evenimentele rezolvate rămân disponibile pentru analiză. Alertele pot fi trimise prin canalele activate în workspace, inclusiv email, push și integrările configurate.
    Mesaje de status
    Uptimus păstrează titlul incidentului publicat de GitHub și îl prezintă împreună cu statusul normalizat. Istoricul disponibil conține 142 incidente indexate, oferind fiecărei alerte context dincolo de statusul actual. Un incident recent indexat a fost „Degradation in repos contents API”.
    Detalii de status
    Actualizările incidentelor și mentenanței sunt păstrate pentru a urmări investigația, remedierea și recuperarea. O actualizare oficială recentă păstrată de Uptimus spune: „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.”.
    Filtrarea statusului componentelor
    Alegi toate componentele sau numai produsele GitHub folosite. Alertele oficiale respectă apoi selecția. Uptimus monitorizează în prezent 11 componente GitHub: Git Operations, Webhooks, API Requests, Issues. Filtrarea modifică alertele oficiale livrate; nu elimină evenimentele providerului din istoricul public.
    Inclus
    Inclus
    Baseline adaptiv care separă rapoartele izolate de o întrerupere extinsăInclusInclus
    Activitatea rapoartelor din 24 de ore și harta regionalăInclusInclus
    Un singur spațiu pentru website-uri, provideri de status, jocuri Steam și aplicații sau jocuri AndroidInclusProdus separat
    Alerte prin e-mail, push și webhook din același spațiu de lucruInclusProdus separat
    Actualizări oficiale ale incidentelor și cronologia statusului GitHubInclusBazat pe rapoarte
    Starea componentelor și ferestrele de mentenanță păstrate separatInclusLimitat pe paginile publice
    InclusBazat pe rapoarte · Limitat pe paginile publiceProdus separat

    Mai multe servicii de monitorizat

    Descoperă alte servicii populare și starea lor actuală

    Răsfoiește toate serviciile
    WOW!Getting Over It with Bennett FoddyArch - AI Home Design
    Backspin Games: Win Real Money
    Pulumi
    Kickbox
    Blanco
    Flickr
    Shipcloud
    Mongodb
    Specops
    Make

    Rate this service

    How would you rate GitHub over the last month?

    No reviews yet

    (O evaluare pe lună)