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
Trento, Trentino-Alto Adige 1
Le Chambon-Feugerolles, Auvergne-Rhône-Alpes 1
Antananarivo, Analamanga 1
Paris, Île-de-France 2
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
Lyon, Auvergne-Rhône-Alpes 1
Tel Aviv, Tel Aviv 1
Rive-de-Gier, Auvergne-Rhône-Alpes 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:

  • snelstack
    Snelstack (@snelstack) reported

    3. You stopped reading the diffs At first, you checked every line. Now you just hit "approve" on massive patches without a glance. Walls of green on GitHub make your stomach churn. Fix: Limit changes to something you can read in two minutes. If it’s too big, the task was wrong.

  • richkuo7
    Rich Kuo (@richkuo7) reported

    i've noticed opus5 uses more context than 4.8 i'm usually around the 15-20% context usage when writing a new github issue

  • InfosecMinion
    InfosecGandalf (@InfosecMinion) reported

    @AikidoSecurity Github issue is deleted 😳

  • piecioshka
    Piotr Kowalski (@piecioshka) reported

    @jcubic @docusaurus Docsify doesn't require a server and can be hosted on GitHub Pages.

  • sandertenbrinke
    Sander ten Brinke | Microsoft MVP (@sandertenbrinke) reported

    @github Github stacks don't work on our github-hosted enterprise environment. On my personal account it works fine. Docs don't mention anything. The error is that stacks isn't enabled for the repo, but I can't find the setting. Any help? @JamesMontemagno

  • johncalhooon
    John (@johncalhooon) reported

    Interesting, no BSV, only EVM chains. Might have to cook a wrapped USDC/USDT on $BSV Then send github issue to Cloudflare repo.

  • quasa0
    (@quasa0) reported

    @tnm lmao!! "it needed spinning disks" that's crazy though ted can u go back and fix github ???

  • authorityvortex
    Dennis H (@authorityvortex) reported

    @currentbitsNET @grok Yeah ok cpanel doesn't support docker workers so it's more like a hybrid. Push it from GitHub and deploy it to a vps or server

  • qurisage
    Quri (@qurisage) reported

    The most viral repository in GitHub history doesn't contain a SINGLE line of code Just one file, CLAUDE.md, with about 50 lines of text. It contains no algorithms-only instructions for the neural network on what NOT to do. 140,000+ stars in total on the main repo. 00:00 - The story behind Andrey Karpathy's post and the phenomenon of 100k+ stars on GitHub. 00:24 - The 3 main challenges of AI models when writing code. 01:00 - A detailed analysis of the 4 principles of working in CLAUDE.md. 02:18 - Step-by-step rule setup (globally or via curl in a specific project). 03:16 - How to automatically resolve conflicts in CLAUDE.md with Claude Code. 04:50 - What's the difference between CLAUDE.md and skills (Superpowers / GSD / G-Stack): background vs. on-command invocation. 07:07 - The perfect workflow: combining CLAUDE.md's hard constraints with targeted skill invocation. 08:41 - Final tips for tidying up your instructions file. Error reduction from 41% to 11% in a test of 50 tasks across 30 projects. 4 golden rules from CLAUDE.md: Think first: no hidden assumptions. If you're unsure of the specifications, communicate the risks and ask the user before writing code. Simplicity is a priority: the minimum code required to solve the problem. No preemptive abstractions. If the problem can be solved in 100 lines, don't write 1,000. Target edits: change only what's requested. Don't try to "improve" adjacent files or the project style. Target-based testing: define success criteria and run tests in a loop until the task is 100% complete. Key takeaway: Models have long since surpassed the performance barrier. The problem isn't what the agent can't do, but what it does when no one is watching. The most popular tool for AI coding isn't a framework, but a "leash."

  • maskaravivek
    Vivek Maskara (@maskaravivek) reported

    I have a bunch of Codex automations running daily or weekly, but they all have the same single responsibility: Create a GitHub issue. None of them fix the issue or implement code changes. They just investigate, gather context, and create a well-scoped issue for me to review. This separation has been working really well for me.

  • heyharishbhatt
    Harish Bhatt (@heyharishbhatt) reported

    🚨 Stop building your own notification system. Meet ntfy. A free and open-source tool that lets you send instant push notifications to your phone or desktop using nothing more than a simple HTTP request. Whether it's a script, server, AI agent, or automation, getting notified takes just one API call. 🔥 Great for: AI agent task completion Long-running scripts CI/CD workflows Server health monitoring Deployments & backups Cron jobs Custom automations If your code runs unattended, ntfy is one of those tools you'll wish you had discovered sooner. Source 🔗: github(DOT)com/binwiederhier/ntfy Follow for more AI, Coding & Web Development tools. 🚀

  • BowlerDerek
    Derek Bowler (@BowlerDerek) reported

    GitHub indexes full commit history for search, not just the live branch. Leaked API keys, internal hostnames and old credentials can surface long after a "fix" commit removes them from view.

  • kamilkwapiszpl
    Kamil Kwapisz (@kamilkwapiszpl) reported

    Using unified agentic tools env shouldn't be optional but obligatory for company. Different agent harnesses leads to: - same errors propagating every time - Different styles of codes - Inconsistent review feedback across teams - Context lost between agent sessions One team uses Agent A, another uses Agent B, a third one pulls some random MCP server off GitHub at 2am because "it worked on their machine." Nobody knows what tools are actually running. Nobody can audit what data goes where. Nobody is responsible when things break. The fix isn't more tools. It's one environment, one set of approved MCP integrations, one agent configuration standard that every dev pulls from. Same guardrails. Same context window. Same tool access. If your team is juggling 3 different agent setups and calling it "flexibility," that's not flexibility, that's technical debt with a sticker on it. I help companies build unified AI agent environments for software development: - Standardized MCP integrations - Approved tool catalogs - Configuration templates your whole team inherits - Security and audit layer baked in - Documentation converted into LLM-ready format One harness. Every developer. It's not vibecoding, it's AI-based engineering

  • DevCalledFede
    Federico (@DevCalledFede) reported

    Renamed my GitHub account the other day. Went to push a project and the remote was still pointing at a handle from two renames ago. Not the one I'd just left, the one before that. Worked fine. GitHub redirects you. Then I read the docs properly. That redirect dies the moment someone claims your old username and makes a repo with the same name. GitHub says it themselves and tells you to go update your remotes. So nothing's broken. It's just quietly betting that nobody wants your old handle. *** remote -v Go look.

  • KingTofCrypto
    Lucky Luciano Polkadot (@KingTofCrypto) reported

    🚨The #Polkadot narrative is officially shifting to Positive! and anyone sitting on the sidelines is about to get left behind. For months the crowd slept on the relentless developer activity and the massive backend upgrades, but the market sentiment is finally flipping hard into the green. The data doesn’t lie, the massive spike in social media buzz and explosive social sentiment tracking across CoinMarketCap AI Analysis proves that the crypto community is waking up to what is happening here. We are talking about a complete overhaul that slashed staking unbonding times from nearly a month down to just two days, killed off slashing risks for everyday stakers, and systematically choked token inflation by enacting a hard supply cap of 2.1 billion $DOT. The smart money is noticing the sheer volume of code hitting GitHub—ranking #Polkadot number one in total developer commit activity and the sudden explosion in online momentum. This isn't a temporary pump, it is the calculated awakening of a sleeping giant that is primed to melt faces. If you aren't loaded up on $DOT before this train leaves the station, you simply aren't paying attention. 💯

Check Current Status