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
Saltillo, COA 2
Montlhéry, Île-de-France 1
Aulnay-sous-Bois, Île-de-France 1
Granada, Andalusia 1
Vernon, Normandy 1
Township of Evan, KS 1
Madrid, Madrid 1
Bogotá, Bogota D.C. 1
Paris, Île-de-France 4
Lyon, Auvergne-Rhône-Alpes 1
Lima, Lima 1
Aix-en-Provence, Provence-Alpes-Côte d'Azur 1
Trento, Trentino-Alto Adige 1
Le Chambon-Feugerolles, Auvergne-Rhône-Alpes 1
Antananarivo, Analamanga 1
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
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:

  • tubezillauk
    hexagonone.eth (@tubezillauk) reported

    Calm down or we will put your tech on github

  • CoreyGallon
    Corey J. Gallon (@CoreyGallon) reported

    Personal apps break the cloud architecture we've spent 25 years building. That's the single point @KentonVarda makes in "Gadgets: Personal app vibe coding that is actually safe," on @aiDotEngineer's YouTube. Kenton is a Principal Engineer at Cloudflare and started the Workers project in 2017. The talk walks through a working platform he built to test the idea, and it's specific about the sandboxing that makes user-modified code safe to run. - The plugin-system death spiral. A developer drowning in one-off feature requests decides to rewrite around plugins, the rewrite never ships, and neither do the features. - The alternative is users editing their own copy. The developer ships a clean core app, and anyone who needs a feature asks an agent to add it, just for them. - Server-per-user is the blocker. One blessed version of an app running on your server is convenient for developers and makes customization impossible, which is exactly what today's vibe coding platforms are built on top of. - Gadgets work like documents, not deployments. Think Google Docs: hundreds of gadgets, each one an app with its own code, each one shareable. - Sharing lives in the platform, not the app. Because a gadget is a single shareable thing, access control is implemented underneath it, so the app can't get it wrong. - Blueprints are code without data. Export a gadget you like as a blueprint, and other people instantiate their own gadget from it. - The agent modifies the app, not just the content. Asked to build a slide deck, Claude added strikethrough, text centering, and an SVG paste box to the Slides app itself when the features it needed weren't there. - Security by containment, not by correct code. The client runs in a null-origin iframe sandbox under CSP that can only postMessage to the parent; the server runs in a dynamic worker sandbox. Neither can reach the outside world, so an XSS bug leaks nothing. - Cap'n Web RPC connects the two halves. The postMessage channel carries an RPC session through to the gadget's server code, written as a durable object. - No containers, no database. The whole thing runs on dynamic workers and durable objects, and the entire demo ran locally on his laptop on workerd, the open source Workers runtime. He also explains why the code isn't on GitHub yet, which he'd promised in the abstract. I'm working through the published talks from AI Engineer World's Fair sharing summaries and takeaways. Follow for more!

  • Sami_Sytela
    Sami Sytelä (@Sami_Sytela) reported

    Submitted my first ever bug-report related to Codex, with a solution. If anyone else is having trouble with Codex freezing the entire computer, have a look at reported issues on Github/Codex.

  • Noro_Ex
    Jorge Galvis (@Noro_Ex) reported

    @github @githubstatus Hi, I don't wanna bother you, but I opened a ticket to github support and it's been a while, and I haven't yet recieved help nor is the issue resolved, I'm getting kinda desperate, can anyone help me?

  • 2happyCSGO
    Prophet Joel (@2happyCSGO) reported

    @xPraveen07 VSCode, VStudio, Github CoPilot GUI and Grok Build, depending on what I'm going to do and how much credits I've got left. CoPilot Max and SuperGrok Plus is way cheaper than paying for extra credits on one of them. Also use llama-server as much as I can to save credits or when the cloud AI's refuse to do what I need.

  • axlegrurt
    Vogon Poet (@axlegrurt) reported

    @XFreeze I use Grok to solve all sorts of technical issues. Point it at a github repo and tell it to install it. Let the model dig through the documentation an dependencies.

  • maskaravivek
    Vivek Maskara (@maskaravivek) reported

    1. Vercel → Cloudflare + AWS Amplify I had around 10 projects on Vercel Pro, andthe fixed Pro cost plus builds and runtime usage was costing me a lot. I moved the static sites to Cloudflare Pages and connected ***, so every push triggers a build and deployment without needing a separate GitHub Actions workflow. For some sites, SSR routes failed inside workerd and I ran into issues with legacy Pages Router/Emotion dependencies, and Node runtime and CSS bundling so I moved those apps to AWS Amplify. Learning: Cloudflare Pages & workers is lower cost, but its opennext adapter might not handle everything. Make sure to test SSR and auth before moving.

  • tonytonggg
    Tony Tong | Founder | Ancient Systems x AI (@tonytonggg) reported

    @KiraFeed The gap between a demo and a shipped agent is a pile of small bugs nobody films. I once filed a QA report against two of our own real GitHub PRs, cross tab navigation was broken and the nav bar height was inconsistent. That's the part these clips skip.

  • makneidinger
    Mario Kneidinger (@makneidinger) reported

    @dhh @github Time for Cursor Origin? That aims to solve exactly this issue. A github alternative for agentic use.

  • Advyth
    Advyth (@Advyth) reported

    @cap100x People like you are the reason why I continue to post content 90% of the people who make money don't acctually teach the basics. Simple terms like tech, GitHub, research, vamping etc are things that most people don't even know how to do, on top of that i post news related content about meme coins and crypto so that it reaches the normie side of social media simple stuff like bundler icons, fresh funded wallets, sniper wallets are things needed to be broken down for people who have no idea how to trade you clearly haven't looked at any of my content i post on tik tok respectfully bro, if you don't make content don't tell me how to make content

  • ArtyGrand
    アルティ (@ArtyGrand) reported

    @LLMJunky Hm, this github issue still open

  • officialdev_bml
    DEV BML (@officialdev_bml) reported

    @Colosteve2000 @thsottiaux @Colosteve2000 I honestly don't understand why you're going through all of this with Hermes Agent when GPT Work can already handle the workflow you're describing. From what you've explained, you want an agent that can inspect your project repository, create an in-depth plan, execute it, run the tests, identify failures, fix them, and continue iterating until the task is completed. GPT Work can handle that workflow. You can connect your GitHub repository, give it the task, and let it work through the implementation and testing process. It can also automatically dispatch sub-agents when necessary to handle different parts of the task. The extra configuration and environment setup with Hermes could simply be unnecessary for what you're trying to achieve. I'm not saying Hermes is bad. I'm just questioning the additional complexity. If GPT Work can already handle the workflow you need, why introduce another agent and all that extra configuration in the first place?

  • GaryDevenay
    Gary Alexander Devenay (@GaryDevenay) reported

    @poteto @bot GitHub login gives me a 500 after MFA

  • ritiksahni22
    Ritik Sahni (@ritiksahni22) reported

    My Mac's battery was dying way too fast (100 to 10% in less than 3hrs) Activity Monitor blamed Ghostty, and I believed it. There were even GitHub threads of people complaining about the same thing, so I assumed it was the latest version. Switched to Alacritty but the problem persisted. After tinkering around, I found the real culprit. Back in May, a Claude Code session started a shell loop to tail some logs and never stopped it. It sat there restarting a Node process, over and over, for three months. I killed the process, and battery went back to normal.

  • imaskie
    askie (@imaskie) reported

    On the morning train, I send DeepSeek Harness the day’s goal before I reach the office. It starts working, asks questions in Grix, and I make the early decisions from my phone. By the time I sit down, the work is already moving. #DeepSeek #DeepSeekHarness #Grix Search GitHub: askie/grix

Check Current Status