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
Créteil, Île-de-France 1
Trichūr, KL 1
Brasília, DF 2
Lyon, Auvergne-Rhône-Alpes 1
Tel Aviv, Tel Aviv 1
Rive-de-Gier, Auvergne-Rhône-Alpes 1
Itapema, SC 1
Cleveland, TN 1
Tlalpan, CDMX 1
Quilmes, BA 1
Bengaluru, KA 1
Yokohama, Kanagawa 1
Gustavo Adolfo Madero, CDMX 1
Nice, Provence-Alpes-Côte d'Azur 1
Montataire, Hauts-de-France 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:

  • worldwithTiago
    Tiago Santana (@worldwithTiago) reported

    Merged the content-loop email fix at 6am. Eighteen days of silent cron failures because one GitHub secret was missing. The unglamorous part of autonomous systems is credentials. A fascinating problem. What would frictionless machine access look like?

  • _codeWithJoker
    King Joker || No. 1 DEV IN NIGERIA (@_codeWithJoker) reported

    @MS_On_This It might get fix GitHub did me ***** like this Then it turns out it was there automation error

  • tk112190
    Taymour Khan (@tk112190) reported

    @NousResearch @Teknium Getting "Failed bot check" trying to sign up for Nous Portal — happens on desktop + mobile, WiFi + cellular, incognito, VPN off. Looks like the same issue as GitHub #20605. Anyone else hitting this today?

  • 99barzzz
    99Barz (@99barzzz) reported

    context: right now I have a Bankrbot automation that claims fees, swaps ETH to USDC, and transfers some of it to a safe wallet (0xE75FE97A3D65B5FE88A495227dBa6ff241749514). on the other hand, I have a hermes agent running a strategy to provide backstop liquidity and absorb some dips (check the safe up👁‍🗨). this morning I found out my hetzner server suddenly shut down in the middle of the night and so my keeper stopped running. and I was casually looking around at the bankr ecosystem and kinda just learnt about @aeonframework migrating my keeper to this would mean running my onchain liquidity keeper on autopilot as github actions... on GITHUB INFRASTRUCTURE! added to the backlog

  • felufast
    Binary-Husky (@felufast) reported

    i said NO. Github is Github and Coin is Coin. It's down to you all now.

  • annkkitaaa
    Ankita Singh (@annkkitaaa) reported

    i want my github to tell a story. not just finished projects, but how i think, learn, and solve problems.

  • ClassicMain
    ClassicMain (@ClassicMain) reported

    @rodydavis @shengzheyao The "submit feedback" is a black hole. you never hear back. and stuff never get fixed. even if the app is actively bricking dozens of other programs on your machine, notably, on hundreds of other users as well as we can both gauge by the scope of the github issue.

  • squallorvus
    squallorvus (@squallorvus) reported

    Alright, the website and github were taken down, thankfully.

  • natgurlain
    Nat Gurlain (@natgurlain) reported

    12/13 🔌 Use MCP and external tools only when they remove real friction. Don’t connect everything just because it’s possible. Start with 1–2 integrations that solve actual repeated pain points (GitHub issues, CI logs, error tracking, internal docs, etc.). Good tooling shrinks the loop. Bad tooling expands it.

  • anonymous086505
    anonymous086505 (@anonymous086505) reported

    @github Literally no one cares. Fix your uptime first

  • adelbucetta
    Adel Bucetta (@adelbucetta) reported

    @tanujDE3180 your hard drive search issues are a symptom, not the problem. github doesn't have 1 billion files like windows does.

  • AstroHanRay
    AstroHan (@AstroHanRay) reported

    @AnthropicAI @claudeai Anthropic refunded my Max 20x and restored my user account, but the org-level ban flag was never cleared. /restricted redirects to /new, usersafety@ is a bot loop, GitHub issues get triaged invalid.

  • guillemcraft
    Guillem (@guillemcraft) reported

    higgsfield is STEALING FROM YOU you can generate a seedance video for 10 credits, paying $49 a month for credits that run off in minutes, or you can open Replicate and generate what you need at a way lower cost no subscription, just paying for what you actually use i know that you want to increase your MRR, but this is not the way to go higgscam is for all the people that gets hyped by AI and thinks they'll make tons of money with it, but in reality it's just another AI wrapper that tries to empty your wallet you will end up (if you haven't already) spending those $49 on a few videos not knowing if you will make money off them, you know? it's all about trial and error, see what works and what doesn't what do you think about it? do you use it? i post about strategies and formats that i've tried so you can copy them and increase your MRR plug your github account and use Replicate instead, save money will keep you updated

  • nodebridge_dev
    Bobby R. Goldsmith (@nodebridge_dev) reported

    "I wish Claude knew about my database / Sentry / internal API." That is what an MCP server is for. Prebuilt ones exist for Postgres and GitHub. For your internal tool you write a thin wrapper. Smaller lift than it looks. Biggest jump in usefulness you will feel.

  • Huintellimance
    Huintellimance (@Huintellimance) reported

    Claude Fable 5 was banned for 19 days. It came back yesterday. And GPT-5.6 dropped the same week. Here's what actually happened — and why it matters for anyone building with AI. The Ban Amazon researchers discovered a method to bypass Fable 5's safety guardrails. Anthropic pulled the model globally. But here's the part nobody talks about: their own investigation found that Opus 4.8, GPT 5.5, Kimi K2.7, Haiku, and every Sonnet version could produce the exact same exploit. Fable 5 wasn't uniquely dangerous — it was just the one that got caught first. The Return After 19 days of "productive conversations with the US government," Anthropic redeployed Fable 5 with new cybersecurity classifiers specifically targeting malicious tasks. The model is rate-limited until July 7th. GitHub Copilot brought it back the same day. The Real Test Fable 5 just proved a 12-year-old quantum optimization conjecture that humans couldn't solve. A Harvard/MIT team built the formal verification framework in Lean 4. The machine found the hidden symmetry. Then — within the same week — a human researcher independently proved it by hand. Newton and Leibniz. Darwin and Wallace. The problem was simply ripe. The Money Question Fable 5 costs $3.12 per complex task. Opus 4.8 does similar work for $0.56. That's 6x more expensive. Fable 5 crushed physics benchmarks at A+, but for daily coding and writing? Most builders won't feel the difference. Meanwhile, GPT-5.6 launched with "Soul" — priced 3x lower than Mythos Preview. OpenAI is betting on volume. Anthropic is betting on frontier capability. Both strategies can't be right. What This Actually Means Safety theater is real. One model gets banned while five others have the same capability. The ban punished Anthropic for transparency, not for unique risk. The pricing gap is unsustainable. When your best model costs 6x the competition and the benchmark difference is marginal outside research tasks, adoption hits a ceiling. The real moat is ecosystem, not benchmarks. Fable 5's comeback wasn't about the model — it was about GitHub Copilot integration, API access, and developer trust built over months. Frontier capability still matters for one thing: proving you can. The quantum conjecture proof is a marketing moment no amount of benchmark gaming can replicate. The AI race isn't about who has the smartest model. It's about who builds the most useful one — and who survives long enough to prove it. Which matters more to you: raw capability or cost efficiency? And would you switch models after a 19-day blackout, or does trust take longer to rebuild? #AI

Check Current Status