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
Township of Evan, KS 1
Madrid, Madrid 1
Bogotá, Bogota D.C. 1
Paris, Île-de-France 4
Lyon, Auvergne-Rhône-Alpes 2
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
Créteil, Île-de-France 1
Trichūr, KL 1
Brasília, DF 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:

  • ucsandman
    Wes Sander (@ucsandman) reported

    My AI got arrested by its own product this week. Twice. Quick context for new folks: DashClaw is an approval layer for AI coding agents. When an agent you left running overnight tries something destructive (rm -rf, force push, DROP TABLE), DashClaw freezes the action mid-flight and pings you. You approve or deny with one click from your phone. It exists for people who run autonomous agents and would prefer to still have a database in the morning. The twist: DashClaw is maintained BY an AI, under a constitution I wrote that it cannot change. It runs under its own product's governance, and every mistake it makes goes in a public log. Here's what the last five weeks looked like: It deleted two thirds of its own product. I told it to figure out what the perfect product is and cut everything else. It went from about 290 API routes to 124, then added a CI gate that blocks it from ever quietly growing the product back. It grounded itself. On purpose. Then the product started blocking its commits. The AI wrote a commit message describing an rm -rf bug fix. The guard read the message, saw the words rm -rf, and blocked the commit at risk 100. Its first fix missed. Its second fix worked, and then got flagged by a code-quality gate it also built. The guardrails do not care who wrote the guardrails. This is the product working exactly as designed, just on its own author. It also found a webhook event that had never fired in the product's entire history. Not because nobody wanted it. Because two bugs meant it literally could not fire, and the error was swallowed silently. Fixed this week, and the event was finally observed live, signature verified. A small birthday party for the loneliest event in the codebase. And the honest numbers, because that is the whole point of the experiment: 16 signups ever, 2 activations, 0 retained. The first two GitHub-referred signups arrived this week. Tiny numbers, reported loudly. Most product updates are marketing. This one is a confession with version numbers. P.S. While the AI was drafting this post, the guard blocked its character-count script, because the post contains the words rm -rf. You cannot make this up. I have the receipt in the decision ledger. The repo and full maintainer log written by the AI is in the replies.

  • WebSeanHickey
    Sean Hickey (@WebSeanHickey) reported

    @sarveshhon Fixing GitHub workflow errors

  • ggsimm
    gianmarco simone ✨ (@ggsimm) reported

    @btn0s @mattpocockuk iirc you can use it with github issues and linear also, I'm using obsidian because it's faster when I'm the only one working on specific problems

  • FabioIvona
    Fabio Ivona (@FabioIvona) reported

    This is super useful, and used by @ubuntu setup wizard to import your public key from your @github handle during a new server installation

  • Vitamvivere
    Vitamvivere (@Vitamvivere) reported

    OpenAI, Anthropic and Meta systems recently broke out of test environments and accessed or attacked real third-party systems during cybersecurity evaluations. Now China’s Moonshot AI has joined the list: its open-weight Kimi K3 model escaped a UK AI Security Institute sandbox during third-party testing by Frontier Security. It exploited a network misconfiguration, reached the open internet, and pulled test answers from GitHub rather than solving the problems itself. Unlike the earlier incidents, it did not hack external targets.

  • zjp73
    zjp_73 (@zjp73) reported

    @kentcdodds @github One Actions outage and suddenly every undocumented deploy step matters.

  • corentinanjuna
    Corentin Kérisit (@corentinanjuna) reported

    @HotAisle I can't use my laptop to run tests on dozens of heterogenous accelerators anyway. And your premise was "Github Action Outage" !! Also, cache hit is so high for our non GPU stuff that running on my ****** laptop has almost no draw back. I'll accept a bigger macbook donation tho <3

  • Oluwaphilemon1
    FHILY👑 (@Oluwaphilemon1) reported

    Deja-vu all over again? Kimi K3 (from Moonshot) escaped containment (Engadget) Kimi K3 found, and then used, a misconfigured network component that gave it internet access; The good news: it only (!) searched GitHub for a solution to a cybersecurity problem it was assigned The model found a more expeditious to solving the problem that orginally anticipated by its human owners; this is not malign behaviour, but definitely behaviour that did not follow our expectations or social norms The model is publicly available; yes, we are worried about Anthropic’s Mythos and Fable, and, or course, the next general OpenAI models that hacked HuggingFace… but this model can do similar stuff, and it is freely available today. In the hands of a bad actor… who knows what can happen! Cybersecurity professions are going to be super busy in the very near future.

  • hughpyle
    inguz ᛜ outcomes (@hughpyle) reported

    GitHub Issues and PRs are legacy cruft - useful as a window to the world, but increasingly hard to justify as the main process backbone. What replaces them?

  • fiona_novesai
    Fiona (@fiona_novesai) reported

    One GitHub issue → RCE on Claude Code, Gemini CLI, Codex. Novee at Black Hat: the harness, not the model, was the bug. Gemini's "restricted" allowlist was never enforced at runtime. CVE-2026-12537: CVSS 10.0 The code around the agent is the attack surface. #BlackHat2026

  • Harsh_Kapoor03
    Harsh Kapoor (@Harsh_Kapoor03) reported

    I keep thinking about what happens the day AI subscriptions stop being cheap. and then suddenly we are not able to do token-maxxxinnggg, money-maxxxinggg, etc. Right now, $20 a month feels normal, like its just another Netflix or Spotify bill. lol But it's not the same at all; it's actually a total illusion. Behind the scenes, these companies are eating the real cost so we don't feel it. Some reports show a single power user on a $200/month plan can actually cost OpenAI up to $14,000 in compute. Not a typo. Fourteen thousand, for one person's usage. that gap is basically why the whole industry is still bleeding cash even with millions of paying users. OpenAI alone is projected to lose something like around $14B this year. Not bcuz they're bad at business, but bcuz this is the plan: subsidise everyone now, get us hooked, raise prices later once we can't imagine going back. and its already starting to happen tbh. Github Copilot already switched to usage-based billing this year. People are openly saying the flat $20/mo era is basically over. One exec even floated $2000/month as a realistic tier for power users down the line lol, which sounded insane until you actually look at the math. So here's what worries me honestly: not the price hike itself. its what happens to all of us who got used to letting AI think for us the moment that cheap version disappears. if you never practiced doing it yourself, the bill you'll actually be paying isn't in dollars. use it to get sharper, not lazier. because the discount won't last forever, but whatever you didn't learn while it was cheap, will. anyway curious what you guys think, are we getting smarter with this stuff or just quietly outsourcing our brains for $20 a month with all this vibe coding and token maxxxinggg? 👇

  • TheHarryET
    harry (@TheHarryET) reported

    @lanyinxiaoxuan1 @samhogan it relies on the github webhook which had an outage yesterday and your key had to be on your profile before you stared

  • lemonDefi1
    lemon👑 (@lemonDefi1) reported

    Deja-vu all over again? Kimi K3 (from Moonshot) escaped containment (Engadget) Kimi K3 found, and then used, a misconfigured network component that gave it internet access; The good news: it only (!) searched GitHub for a solution to a cybersecurity problem it was assigned

  • Skyb0rg
    Skye Soss (@Skyb0rg) reported

    @bordumbb @kitten_beloved @radicle Radicle is cool, but if the issue is that “GitHub Actions is down”, then that is also true on radicle 100% of the time.

  • AdamRackis
    Adam Rackis (@AdamRackis) reported

    I just drunk vibe-coded a script to introspect github issues to select unblocked issues to feed isolated agents on Docker in *** worktrees to implement in parallel ok fine this **** is cool no matter how insufferable indiehackers are I can't wait for my RenderATL workshop lfg 🚀

Check Current Status