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
Inverness, Scotland 1
Quito, Pichincha 2
Junín, Manabí 1
Guadalajara, JAL 1
Paris, Île-de-France 6
São Paulo, SP 1
Ipauçu, SP 1
Vigo, Galicia 1
Tel Aviv, Tel Aviv 1
Éragny, Île-de-France 1
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
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:

  • loez__
    luiz castro (@loez__) reported

    github down de novo?

  • shakiXBT
    shaki (@shakiXBT) reported

    one more github actions outage and i end it all

  • starmexxx
    starmex (@starmexxx) reported

    elon musk grabbed the source code openai open-sourced by accident, rewrote it in rust over a weekend, and shipped it as a free coding agent that does everything $200/mo chatgpt pro does. why pay $200 to openai and $200 to claude when this runs for $8 the swarm above is one weekend of exactly that: thousands of agents pouring through four endpoints, three paid seats billing $1.80 a task while the free fork bills $0. musk co-founded openai, walked out, and when they left codex on github under a permissive license, he forked it, stamped grok on it, and gave it away what the free version does that the $200 seat charges for: the agent · openai's own engine -> it reads your repo, writes patches, runs your tests, and loops until they pass, exactly like codex -> because under the hood it is codex, just faster and free. you are paying $200 for the paid skin of a tool now sitting on github the license · apache-2.0, un-revocable -> free to use, free to fork, free to ship inside your own product with zero strings -> openai cannot pull it back. musk made sure the license is the kind that never expires the switch · one line, no new tools -> point it at any openai-compatible or claude-compatible endpoint, including an $8 kimi backend -> same terminal, same workflow, gpt-5.6 and opus 5 just quietly lose the seat the bill · $400 down to $8 -> chatgpt pro plus claude max is $400 a month. the free agent plus an $8 kimi key does the same daily work -> that is a 98% cut, built out of openai's own source code, handed to you by the guy suing them here is the part they will fight me on: openai did not lose this to a better model, they lost it to their own license and an enemy with a weekend free. the $200 was never the tool, it was the toll, and musk just put openai's own logo on the road around it drop your $400/mo ai stack to $8. the run above is openai's own agent, rewritten free, doing the job it bills $200 a month for. the full breakdown is in the article below

  • Codewithoutai
    Codewithoutai (@Codewithoutai) reported

    Geez. Can you all stop being meat proxies for a second so GitHub can fix Actions?

  • CryptoDegenTopG
    Alonso G (@CryptoDegenTopG) reported

    @XPeterKappes @bot @cursor_ai Same issue here. Mine is connected with my GitHub and I am getting the same error

  • grumpypcodes
    Patrick Gerard (@grumpypcodes) reported

    Github or Vercel has issues atm?

  • ponta_kokemomo
    ponta_kokemomo (@ponta_kokemomo) reported

    A Ledger vulnerability was making the rounds on CT today, but according to Ledger’s CTO, the issue has already been fixed. As long as your firmware and apps are up to date, you should be fine. You can’t completely avoid zero-day risks, but in general, applying security patches and keeping your software updated is still the safest approach. Dev tools you pick up from GitHub are a different story, though. The latest version isn’t always the safest lol

  • ossbuildconnect
    OSS | Let's Connect (@ossbuildconnect) reported

    GitHub’s recent 7-hour outage is a useful engineering reminder: Critical workflows need fallback plans. Keep local copies, document release procedures, avoid depending on one service for every operation, and design systems assuming external platforms can fail. #DevOps #GitHub

  • evan_jarman
    Evan Jarman (@evan_jarman) reported

    most teams don’t have an 'being behind with ai' problem they have a memory problem every new chat starts from zero every person rebuilds the same context every agent forgets what the last one just learned and skills are not synchronised across the company once you put the company knowledge, decisions, and workflows in one central place that Claude, Codex, and the rest can actually pull from the whole thing starts compounding tools like HQ or even a well-structured github repo make that possible

  • ruibeard
    Rui Almeida (@ruibeard) reported

    @dhh @mischavdburg The Omarchy skill could include instructions to automatically submit the fix to GitHub when it actually solves drivers/HW related problems. Those could then be scanned to apply the fix upstream

  • G_ameman
    Aurorastar (@G_ameman) reported

    02:37:39–02:40:08 02:37:39 You just tell it to keep going until you tell it to stop. 02:37:45 It ended up... 02:37:45 I think we ended up with a 46 time execution improvement over the original. 02:37:51 It's incredible. 02:37:52 Absolutely incredible. 02:37:52 It's just incredible. 02:37:54 Um, I do, you know, I just don't think there's anything that compares to Fable in terms of planning. 02:37:58 So I usually do Fable for planning and for reviewing, and then something else for implementation, like Opus 5. 02:38:08 And it's really nice. 02:38:08 It's a, it's a really nice setup that allows you to not run out of tokens too much. 02:38:14 What I found, it's really interesting because Fable is, in my opinion, the best model right now, but it also makes mistakes. 02:38:18 And the best way to get the best software, I would actually rather have two differently sourced sort of... 02:38:25 I mean, they're not mid-tier, they're all frontier. 02:38:29 But have, let's say Opus 5 and Codex and have one check the other's job. 02:38:35 This is my standard operating procedure now. 02:38:40 I'll have Opus or Fable do the work, and then I always end it, review with Codex xHigh. 02:38:47 And I've also started using Grok just to test it out, and it's also quite good. 02:38:47 And it keeps finding stuff. 02:38:51 And then that's my workflow when I'm having my agents on my own machine do it, and then I push to GitHub. 02:38:55 And then Copilot, I kid you not, has actually gotten good. 02:38:59 Copilot keeps finding stuff that's legitimately broken, which is also incredible acceleration because the first version of Copilot that started doing this was literally retarded. 02:39:09 It would just constantly flag things that were nonsense. 02:39:13 It would constantly flag the same problem over and over again as you would push. 02:39:13 It was really annoying, so I think a lot of people actually ended up turning that off. 02:39:17 And if they did, they should turn it back on because it's actually quite good. 02:39:24 Keeps finding things. 02:39:24 And if you then take that, and we shouldn't be surprised. 02:39:24 Why are we surprised? 02:39:27 Even if you're a good programmer, if you finish a job and you ask your also very good peer to review it, you're gonna end up with better code. 02:39:35 Of course you're gonna end up with better code. 02:39:35 So build that into your process. 02:39:39 Pick one of the agents to drive with. 02:39:39 I've mainly been driving with Claude, which is actually interesting because I have some other reservations about Anthropic. 02:39:47 But the reason I'm sticking with Claude is, in my opinion, they actually have the best harness. 02:39:53 And one of the reasons it's the best harness is it's multi-agent running. 02:39:57 So if you wanna run multiple agents at the same time, you can do arrow left when you're inside a session, then it goes back to Agent View. 02:40:05 And here in Agent View, you can pick up another agent. 02:40:08 So if you wanna do this thing where you have multiple threads going on the Claude Code is just the nicest setup.

  • amaherjr
    Ahmed Maher (@amaherjr) reported

    WTF! github actions #down

  • josepollman82
    Jose Pollman (@josepollman82) reported

    A malicious GitHub issue hijacking a coding agent: GitHub's risk page says only users with write access can trigger it, and comments from anyone else never reach the agent. The documented injection defence is filtering hidden characters. Plain prose is not hidden.

  • oluwasayo_
    Sayo Oladeji (@oluwasayo_) reported

    Another GitHub outage is brewing.

  • yihanzhuu
    Yihan Zhu (@yihanzhuu) reported

    GitHub Actions is down. No wonder my CI can’t run.

Check Current Status