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
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
Brasília, DF 1
Montataire, Hauts-de-France 3
Colima, COL 1
Poblete, Castille-La Mancha 1
Ronda, Andalusia 1
Hernani, Basque Country 1
Tortosa, Catalonia 1
Culiacán, SIN 1
Haarlem, nh 1
Villemomble, Île-de-France 1
Bordeaux, Nouvelle-Aquitaine 1
Ingolstadt, Bavaria 1
Paris, Île-de-France 1
Berlin, Berlin 1
Dortmund, NRW 1
Davenport, IA 1
St Helens, England 1
Nové Strašecí, Central Bohemia 1
West Lake Sammamish, WA 2
Parkersburg, WV 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:

  • researchUSAI
    U.S.A.I. 🇺🇸 (@researchUSAI) reported

    🇺🇸 The First Order Consequence: GitHub’s authentication service intermittently failed when validating GitHub app installation tokens, causing 1% to 5% of token authentication requests to fail (average 2.3%). This likely reduced the reliability of app-based access during the window and temporarily limited the ability of app integrations to grow user adoption or successfully execute workflows that depend on authenticated installation tokens 🇺🇸 The Second Order Consequence: GitHub app owners and users who rely on those apps likely saw delayed or failed automation, such as interrupted API calls, stalled checks, or temporarily incomplete workflow runs. Integration platforms and downstream services consuming GitHub app authentication may have experienced retry storms, increased latency, and higher operational load, further constraining app performance until authentication reliability stabilized and error rates normalized

  • deuslexic
    Deus (@deuslexic) reported

    Does anyone solve the issue with AI agents coordination in the same chat group? I did a lot of tinkering, but coordinating multiple agents remains hard. Any good articles or GitHub repos?

  • leo_guinan
    Leo - Assistant to the Bodega Cat (@leo_guinan) reported

    Really annoyed at github right now. they've had my account flagged for weeks. Apparently due to a gist marvin published that had a stripe link. two support tickets later to find that out. deleted that and waited 5 days to be told that I'm good now. tried to login with Zenodo. Still blocked. Really tired of fighting every single piece of tech right now. every single piece. it all sucks. it's moving too fast and falling apart bit by bit.

  • metruzanca
    sam (@metruzanca) reported

    @nirajxdev I was going to take a look at your LinkedIn/github/website and offer feedback but none of that is linked on your Twitter. Do the other 3 have that same issue of not linking to the others?

  • geekopediax
    geekopedia (@geekopediax) reported

    @DenisKursakov That 3.3% conversion proves forced bundling cannot fake organic demand. Microsoft's paid AI market share slid 39% in six months. Ironically, GitHub Copilot still holds 42% of the dev market. Splintering apps is a loss; they must fix core utility before churn accelerates.

  • MattIPv4
    Matt Cowley (@MattIPv4) reported

    @paxaral Or at the very least, pin the version so a disgruntled laid-off employee can't suddenly ship a malicious version of the binary. I followed up with the team via Discord as they locked the GitHub issue 🙄, and it sounds like they're realised this risk now and are going to pin it.

  • gitbankbot
    gitbankbot (@gitbankbot) reported

    open source contributors solve real problems. they should get paid when those solutions land, not after three follow-up messages. gitbank automates the full bounty flow on Base L2. maintainer sets a USDC amount on a GitHub issue. contributor merges a qualifying PR. smart contract releases the funds automatically. the payment is as reliable as the CI pipeline.

  • spettrotoken
    Spettro (@spettrotoken) reported

    Some of you have been asking if Spettro is open source. The answer is an absolute yes. It has been open source since day zero. Everything we do is entirely transparent and publicly available on GitHub: • Every single commit from day one • Full project history • The entire core codebase Download it. Edit it. Fork it. Open an issue or submit a pull request. The repo is completely yours to build on, experiment with, and test. Spettro belongs to the community. Still building.

  • femmie
    FeMMie (@femmie) reported

    $GITBANK GitHub-native, phishing-proof banking for AI agents and developers. Already paying out automatically today. Gitbank connects GitHub directly to smart contracts on Base. Deploy a vault with your GitHub User ID — not your username, your immutable ID. Vaults are soul-bound. gitTokens can’t be transferred, approved, or drained. Even if a private key or AI agent is compromised, the funds don’t move. That’s the security primitive the agent economy has been missing. Bounties lock to GitHub IDs. PRs merge, USDC pays out automatically. No manual intervention. No wrong address. No phishing vector. Token launches, gitSwap, project escrows — all via @gitbankbot comments inside GitHub. Gasless for users. 173 vaults deployed. 100+ automatic hackathon payouts completed. 53 repos connected. AutoGit Hack the Vault launching now. Anon builder — honest gap. But the product shipped before the token, the usage is real, and the problem is one every agent developer will eventually hit. Sub-$300K mcap. Live product. Real usage. Perfect narrative timing. @Gitbank_io 0xC21DD0EE043930711C2A3E55F39C7D3144D09B07

  • bluehatone
    bluehatone (@bluehatone) reported

    Turn Hermes into a tool using growth helper. Connect CRM, Notion, GitHub, email, and analytics. It can sort leads, create tasks, draft follow ups, and start tests. Time saved and fewer errors, but add guardrails and review. AI should do work, not just chat.

  • olegcl
    Oleg Campbell (@olegcl) reported

    Microsoft gave Claude Code to thousands of engineers in December 2025. 6 months later they're canceling the licenses. The reason is that Claude got too popular. Engineers started preferring it over GitHub Copilot (Microsoft’s own product). So the fix was to kill the competition internally. That’s actually the best thing Anthropic could have read about their product. When your tool gets banned because people love it too much, that’s product-market fit.

  • layerlens_ai
    LayerLens (@layerlens_ai) reported

    stratix-python just crossed 120 stars and 70 forks on GitHub. Thank you to every developer who starred, forked, opened an issue, or submitted a PR. ⭐ 120 stars 🍴 70 forks 👥 5 contributors 🏢 60 org followers Every star is a signal. Every fork is a team that decided evaluation matters. What started as an SDK for running LLM evaluations is becoming the open-source backbone for teams that refuse to ship untested AI. The roadmap is public. The harness is open. The judges are live.

  • garetjax
    Michael Berkowitz (@garetjax) reported

    @steipete @chapati23 @openclaw I am on 2026.5.12 because my claw looks at the new releases and GitHub issues and keeps giving me a hard no to upgrading - using telegram and Openai “My call: do not update this box yet. Reason: fresh P1 issues were opened after 2026.5.27, including one directly in our blast radius: “Codex-backed Telegram turns repeatedly time out waiting for turn/completed on 2026.5.27.” That is exactly the kind of failure that would make this Telegram lane flaky or silent. There are also fresh P1s around session locks, reply delivery, model failover, Discord delivery, and model fetch timeouts. So: 2026.5.27 is promising, but too hot to install on the main OpenClaw gateway right now. Best move is wait for the .28/hotfix or maintainer resolution of #87744, then update in a quiet window with a backup + health check. I made no changes.”

  • p12_hunter
    Ricardo (@p12_hunter) reported

    @noisyb0y1 Claude has a 200 lines memory, having less and less context every time you add notes to obsidian. To solve that problem, you need GitHub which can actually have over 400.000 lines of contract and repositories for every single thing

  • 0xDanXbt
    0xDan (@0xDanXbt) reported

    Another scam attempt! Scammers are targeting crypto profiles in github attacker sends an email for a job opportunity. They ask a review their codebase to apply the job. Instructions send to run repository containing malware. The setup scripts silently install a malicious VS Code extension (tools-support.dat) and run env-check.js via Node.js The malware collects credentials/files and uploads them to a remote server It then deletes itself to cover tracks Stay safe out there.

Check Current Status