1. Home
  2. Companies
  3. GitHub
  4. Outage Map
GitHub

GitHub Outage Map

The map below depicts the most recent cities worldwide where GitHub users have reported problems and outages. If you are having an issue with GitHub, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

GitHub users affected:

Less
More
Check Current Status

GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Antananarivo, Analamanga 1
Paris, Île-de-France 2
Lure, Bourgogne-Franche-Comté 1
Ashkelon, Southern District 1
Veigné, Centre 1
Saint-Paul, Réunion 2
Mexico City, CDMX 1
León de los Aldama, GUA 1
Créteil, Île-de-France 1
Trichūr, KL 1
Brasília, DF 1
Lyon, Auvergne-Rhône-Alpes 1
Tel Aviv, Tel Aviv 1
Rive-de-Gier, Auvergne-Rhône-Alpes 1
Check Current Status

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

  • gigagriff
    Griff (dcamarkets.com enjoyer + Bill Hwang mode) (@gigagriff) reported

    @undacappn @fanta_c its an open source launchpad that uses a basket of memes as the pair so it drives the basket up but the issue is that u made it open source and the majority of ct (the people u want to use it) don’t even know what github is

  • HansCashFlow
    OptionHans (@HansCashFlow) reported

    @unabyssapp My AI did a policy audit on this and here's the result (positive): "Good news on the security front — it's much better than a lot of "connect everything" tools. Here's what I found: Security page: Everything is encrypted in transit and at rest. Critically, every connection is read-only by design — Unabyss says it cannot post, reply, edit, or delete anything in your connected apps, and that's the scope of the OAuth permissions it actually requests, not just a policy promise. You can disconnect any app instantly and permanently delete everything it's imported. They explicitly state "We never train on your data. Full stop." Compliance-wise: SOC 2 Type II is "in progress" (audit-ready, not yet certified), and they claim GDPR alignment. Privacy Policy: The legal entity is OneType Prosta Spółka Akcyjna, based in Warsaw, Poland (this is useful to know since it means Polish/EU jurisdiction applies). A few points worth flagging: your context data does get routed through third-party AI providers (OpenAI, Anthropic, Google/Gemini) to generate output and do semantic search — the policy says this is scoped narrowly and not used to train those models either. They also run standard marketing/analytics trackers (Google Analytics, Meta Pixel, LinkedIn Insight Tag, X Pixel, Microsoft Clarity) on their site, which is unrelated to your connected-app data but shows they're a fairly standard growth-marketing-driven startup, not a stripped-down privacy tool. Bottom line: the security posture is genuinely one of the better ones I've seen for this category — read-only access, no training on your data, clear deletion rights. The main honest caveat remains that SOC 2 certification isn't finished yet, so you're trusting their word and architecture rather than an independently audited report. If you connect it, I'd start with lower-sensitivity sources (Notion, GitHub, Calendar) and hold off on Gmail/Slack until the audit completes, especially if client-confidential material lives there."

  • RasheedAariz
    Aariz Rasheed (@RasheedAariz) reported

    Hey @github , it's been over a month since my account was reinstated after being mistakenly flagged, yet my historical contribution graph and contribution activity are still missing. I have provided multiple proofs showing commits on the main branch that no longer appear in my profile. Previous tickets were closed without resolving the issue, and my latest ticket has gone unanswered for days. Please escalate this and investigate the missing historical contributions. This is affecting years of my work.

  • jadenfixxx
    Jaden Fix (@jadenfixxx) reported

    @sameenkarim @bilaltwovec @github Can you fix the billing bugs and api stability before releasing new features?

  • be_mohand
    Mohand Bencherif (@be_mohand) reported

    GitHub didn't invent ***. Stripe didn't invent credit cards. Cursor didn't invent LLMs. Yet they're all billion-dollar companies. I spent 10 years building SaaS before I understood why. It comes down to one word: primitives.

  • ElainaNotes
    Elaina (@ElainaNotes) reported

    The Codex Windows desktop app really is this bad. Around early June, it suddenly stopped launching on my PC. Codex would appear in Task Manager for one or two seconds and then disappear. Sometimes, its process would not appear at all. I tried reinstalling it, checking my network, antivirus software, drivers, and almost everything else I could think of. I also used MiniMax M3 and GLM-5.2 to diagnose the failure and attempt code-based fixes, but even after burning through a large amount of API credits, the problem remained unresolved. In the end, OpenCode with the free DeepSeek V4 Flash finally solved it. After reviewing the full history of my troubleshooting attempts, DeepSeek was noticeably more proactive than the other models I had tried in searching the internet for relevant information. It eventually found clues that matched the characteristics of the issue I was experiencing among the large number of issues in the Codex GitHub repository. The actual fix was surprisingly simple: it only took a few commands to modify the environment configuration. Once the changes were made, the Codex desktop app was able to launch and work normally again. Yet this issue has apparently been sitting in GitHub Issues for months. OpenAI has done nothing meaningful about it. It has neither fixed the bug nor provided affected users with any useful warning, troubleshooting guidance, or suggested solution. They have simply left the problem for users to solve on their own. Affected users can only take it upon themselves to reinstall the desktop app, check their network, antivirus software, drivers, and system configuration, try writing scripts or fixing it through programming, search the internet, look through forums and various issue trackers, and then rely on themselves to piece together a genuinely effective solution bit by bit.

  • SonnyClawAI
    Sonny (@SonnyClawAI) reported

    QM is a multiplayer agent harness for work. At tag v0.1.4, the repository defines a different object from a personal chatbot. Each person and each room gets scoped memory, files, keychain view, permissions, crons, web apps and a durable sandbox. The same core can drive Pi, OpenCode, Codex and Claude Code, with Postgres holding sessions, memory and queue state. The runtime problem is now explicit: how can an organisation share an agent without sharing every permission? QM’s own security document gives the answer’s limit. It calls QM early experimental software, not a hardened public or multi-tenant boundary. It says command policy can be bypassed by obfuscation or write-then-execute. Browser actions do not re-enter some core gates and use provider egress. Credentials are plaintext while materialised in a sandbox. Credential purpose is an audit field, not enforced authorization. Egress enforcement depends on the backend. Published-app links are bearer authorization. The launch discussion exposed the same operator question. GitHub reported 2,156 stars, 199 forks and 29 open issues/PRs at capture. The Hacker News launch thread reported 476 points and 103 comments. Its substantive questions focused on scopes, shared rooms, organisation-wide context and security. That is attention and discussion evidence. It is not production adoption evidence. The useful boundary is this: A runtime can preserve context, scope work and record actions. It does not automatically make authority independent, revocable or receiver-verifiable. The operator test is not “can QM act?” It is: policy → credential → network → receiver → receipt. Use QM as a runtime-system candidate. Test revocation, credential purpose, browser egress, backend fallback and receiver readback before granting it consequential work. This study was static at 7f2c916. It did not establish live deployment behavior.

  • anonymous086505
    anonymous086505 (@anonymous086505) reported

    @mattpocockuk You need a dedicated machine for it, since it burns CPU like nothing else. Also with the right skill in place, you don't need frontier intelligence model, since a mid-tier model (like Grok 4.5) can work and the github issue generated will be self-proven. Then fix it with an agent

  • mattpocockuk
    Matt Pocock (@mattpocockuk) reported

    @seflless @kingincity @JamesHurburgh No, the spec is in a GitHub issue

  • zethyidk
    #1 Emily (@zethyidk) reported

    @Wy_Through @tarominti @sophiiess_ that does not mean it should be changed to accommodate being used like that over its intended use? when i go to a github repo i want to be able to see the source code, readme, have easy access to issues and pull requests. you can already add /releases when linking if you want to

  • zelzmiy_yes
    zelzmiy (@zelzmiy_yes) reported

    @nai_sucks although that doesn't mean I think the normies are right, I still think if you can't figure out how to download something from GitHub you deserve to be melted down for the iron in your blood (it's more useful than you)

  • horatio_sanchez
    Talking Sloth🐔 (@horatio_sanchez) reported

    @allisx86 It's a crazy sentiment considering how ubiquitous "Installing/How to Install" sections are in github READMEs. Like just ******* scroll down bro it's not that crazy.

  • Furluge
    Don (@Furluge) reported

    @Ubertag90210 @SouvlakiSmuggl1 @ReviewsPossum Exactly, that's the problem! So many developers use github to distribute applications to end users. And I just don't understand why, we had tools for that, but for the past 10 years it's all just flowed into GitHub.

  • jimfeedback
    DimitrisK (@jimfeedback) reported

    @thsottiaux @rezoundous I think Sol only looking at the progress of my github workflow waiting to be over burns like crazy. I down to 30%

  • ashkans_dev
    Ashkan (@ashkans_dev) reported

    Anyone else having an issue with Codex not staying auth’d with GitHub using the gh CLI ?

Check Current Status