UptimusUptimusTjeneste status
HændelserRapporterPriser
Log IndMonitor with Uptimus
HjemHændelserRapporterPriserMonitoringWebstederMobilappsMobilspilSpil
Log IndMonitor with Uptimus
Status historyRSS updatesStatus API

Powered by Uptimus

    All systems operational

    Nej — GitHub fungerer normalt.

    Last checked 7. sep., 23.26 UTC

    Operational

    Current status

    8.00%

    Known uptime

    11

    Monitored components

    GitHub service health

    Tjenesten var i drift. Den officielle kilde rapporterer ingen aktive hændelser eller vedligeholdelsesvinduer.

    For 60 dage siden
    I dag
    I drift
    Problemer
    Nedbrud
    Vedligeholdelse
    Ingen data

    GitHub outage reports

    0 outage reports in the last 24 hours.

    Bucharest, Romania

    “Partial outage”

    12. jul., 14.10 · for 57 dage siden

    Bucharest, Romania

    “Major outage”

    11. jul., 21.58 · for 58 dage siden

    Bucharest, Romania

    “User reported: Other issue”

    11. jul., 19.36 · for 58 dage siden

    Bucharest, Romania

    “Degraded performance”

    11. jul., 13.50 · for 58 dage siden

    Bucharest, Romania

    “Major outage”

    22. jun., 1.59 · for 77 dage siden

    Bucharest, Romania

    “Degraded performance”

    19. jun., 20.52 · for 80 dage siden

    Bucharest, Romania

    “User reported: Other issue”

    19. jun., 13.06 · for 80 dage siden

    Fællesskabsdiskussion

    0 · Del dine tanker om GitHub

    Ingen kommentarer endnu

    Vær den første til at kommentere!

    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.

    Se fuldt kort

    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. sep. 2026, 22.02 UTC · Resolved 4. sep. 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. sep. 2026, 20.39 UTC · Resolved 4. sep. 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. sep. 2026, 14.17 UTC · Resolved 3. sep. 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. maj 2025, 21.30 UTC · Resolved 31. maj 2025, 04.30 UTC

    2. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 28. maj 2025, 16.30 UTC · Resolved 29. maj 2025, 16.30 UTC

    3. ✓

      Codespaces Scheduled Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 14. maj 2025, 16.30 UTC · Resolved 15. maj 2025, 16.30 UTC

    4. ✓

      Codespaces Scheduled Maintenance

    Få besked, når status for GitHub ændres

    Start overvågning

    Om overvågning af GitHub på Uptimus

    Uptimus overvåger GitHub via den officielle statuskilde og normaliserer hændelser, vedligeholdelse og komponenter til én ensartet status.

    Siden indeholder nu 11 komponenter, 142 hændelser, 34 vedligeholdelser og 50 dages kendt historik.

    Uptimus er en uafhængig tjeneste og er ikke tilknyttet GitHub. En sund status garanterer ikke, at alle brugere, enheder eller områder er upåvirkede.

    Sådan overvåger Uptimus GitHub

    Få besked, når GitHub eller en overvåget komponent melder et større eller kritisk nedbrud. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer. Den tilgængelige historik indeholder 142 hændelser og giver mere kontekst end den aktuelle status. En nylig registreret hændelse var “Degradation in repos contents API”.

    Få besked om nedsat ydelse, delvis påvirkning og mindre hændelser uden et fuldt nedbrud. Uptimus følger nu 11 GitHub-komponenter: Git Operations, Webhooks, API Requests, Issues. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.

    Uptimus vs Downdetector for GitHub

    Downdetectors offentlige sider er primært baseret på brugerrapporter. Uptimus kombinerer dem med officielle hændelser, vedligeholdelse og komponentstatus, når udbyderen offentliggør dataene.

    Uptimus vs Downdetector for GitHub
    JämförelsekriterierUptimusDowndetector
    Rapporter fra fællesskabet om GitHub

    Ofte Stillede Spørgsmål

    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. sep. 2026, 15.00 UTC · Resolved 1. sep. 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. maj 2025, 16.30 UTC · Resolved 8. maj 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. Vedligeholdelsesnotifikationer
    Få besked, når GitHub offentliggør planlagt, tidsbestemt eller aktiv vedligeholdelse. Uptimus har registreret 34 vedligeholdelsesvinduer fra den tilgængelige GitHub-historik. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.
    Gendannelsesnotifikationer
    Få besked, når GitHub eller en påvirket komponent igen fungerer normalt. Siden indeholder 50 dages kendt historik; løste hændelser bevares til senere gennemgang. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.
    Statusmeddelelser
    Uptimus gemmer hændelsesoverskriften fra GitHub sammen med den normaliserede status. Den tilgængelige historik indeholder 142 hændelser og giver mere kontekst end den aktuelle status. En nylig registreret hændelse var “Degradation in repos contents API”.
    Statusdetaljer
    Opdateringer om hændelser og vedligeholdelse gemmes, så undersøgelse, afhjælpning og gendannelse kan følges. En nylig officiel opdatering gemt af Uptimus lyder: “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.”.
    Komponentfiltrering
    Vælg alle komponenter eller kun de GitHub-produkter, du bruger. Officielle alarmer følger valget. Uptimus følger nu 11 GitHub-komponenter: Git Operations, Webhooks, API Requests, Issues. Filtrering ændrer leverede officielle alarmer, men fjerner ikke hændelser fra den offentlige historik.
    Inkluderet
    Inkluderet
    Adaptiv basislinje, der skelner enkelte rapporter fra større nedbrudInkluderetInkluderet
    Rapportaktivitet over 24 timer og regionalt nedbrudskortInkluderetInkluderet
    Ét arbejdsområde til websites, statusudbydere, Steam-spil og Android-apps og -spilInkluderetSeparat produkt
    E-mail-, push- og webhookalarmer fra samme arbejdsområdeInkluderetSeparat produkt
    Officielle hændelsesopdateringer og statushistorik for GitHubInkluderetRapportbaseret
    Komponentstatus og vedligeholdelse vises separatInkluderetBegrænset på offentlige sider
    InkluderetRapportbaseret · Begrænset på offentlige siderSeparat produkt

    Flere tjenester at overvåge

    Opdag andre populære tjenester og deres nuværende status

    Gennemse alle tjenester
    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

    (Én anmeldelse pr. måned begrænsning)

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