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
Veigné, Centre 1
Paris, Île-de-France 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
Itapema, SC 1
Cleveland, TN 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:

  • josepha_mayo
    josepha_mayo (@josepha_mayo) reported

    im calling out @cognition for this slop in 2026, imagine a model doing this, and it claims to beat/match gpt5.5? they said it was better than kimi k2.7 code at coding- true, i used and verified but kimi k2.7 code never loops like this the model is beyond damaged, they really damaged the reasoning, i wonder if they used different optimizers or idk what made it this bad it also thinks like "push kaggle, push github, go "von" folder" it cant predict "to" ever again - which kimi k2.7 code never had that issue

  • RodmanAi
    Leonard Rodman (@RodmanAi) reported

    Andrej Karpathy exposed one of the biggest problems with AI coding. LLMs make the same coding mistakes over and over: • Over-engineer simple problems • Ignore existing code patterns • Add dependencies nobody asked for If the mistakes are predictable... They're preventable. That's why a single CLAUDE.md file built around his coding principles just crossed 192k GitHub stars. No framework. No IDE plugin. Just one markdown file that teaches Claude how to think before it writes code. The biggest upgrade to AI coding isn't a new model. It's better instructions.

  • rohit_jsfreaky
    Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported

    @thdxr an issues channel where the agent reproduces and fixes every good github issue is a slick loop, nice

  • Av1dlive
    Avid (@Av1dlive) reported

    Github just dropped a 54-min course on how to build products with AI Agents 0:07 : How to ship a real feature in under a minute 14:48 : How to use the AI agent stack used by github engineers 22:14 : How to use plan mode with Opus 4.8 27:52 : How to build a skill once and share it across your team 34:52 : How to make the agent run your real app and fix its own bugs 43:33 : How to use agent loops to fix your own code 54 minutes and you'll understand coding agents better than most people building with them. watch it today, then read the a-to-z build of the loop that ships while you sleep, below. bookmark it.

  • DFIR_Radar
    DFIR Radar (@DFIR_Radar) reported

    M-Red-Team supply chain attack hit AsyncAPI via a GitHub Actions "pwn request," stealing a privileged PAT and publishing five malicious npm package versions reaching 3M+ downloads per week. Key details: - The attacker exploited a pull_request_target misconfiguration in asyncapi/generator: the workflow ran in the base repo context with secret access, but checked out attacker-controlled PR code. PR hid obfuscated JavaScript after ~1,000 bytes of whitespace; the workflow exfiltrated secrets to rentry[.]co/elzotebo at 05:16 UTC, 8 minutes after the PR opened. A fix had been proposed and sat unmerged for 58 days. - Five malicious versions across four packages were published under @asyncapi: generator 3.3.1, generator-helpers 1.1.1, generator-components 0.7.1, and specs 6.11.2 and 6.11.2-alpha.1. Payload executes on import/require, not install, bypassing install-time scanning. - The three-stage chain: Stage 1 spawns a detached process on import; Stage 2 downloads an 8.25 MB encrypted bundle from IPFS; Stage 3 is a 92,000-line framework (self-labeled "M-RED-TEAM v6.4") persisting via a systemd user service (miasma-monitor.service) and using HTTP, Nostr relays, Ethereum smart contracts, and libp2p for C2. - Credential theft targets browser passwords and cookies, SSH keys, npm and GitHub tokens, AWS credentials, macOS Keychain, and crypto wallets across developer and CI/CD environments. #DFIR_Radar

  • vinii_joga10
    Vinicius Lourenço (@vinii_joga10) reported

    @hardfist_1 I didn't find a reason for not exposing it as public API on github issues, so why not try create an issue/pr to discuss to expose this without the flag if it can be beneficial?

  • TheWhizzAI
    The Whizz AI (@TheWhizzAI) reported

    This guy on GitHub built a tool that hacks your app before real hackers do and proves it. It's called Strix. AI agents that act like real pentesters, not scanners. Finds SQL injection, SSRF, IDOR, and more. Every bug comes with a working exploit. Auto-generates a fix as a ready-to-merge pull request. Plugs straight into your CI pipeline blocks bad code before it ships. 34K+ stars. Added 2,800 today alone. ( free 100% open source )

  • Nexisintel
    Nexis (@Nexisintel) reported

    A 13-year-old uploaded a free trading tool to GitHub. 60 days later, someone sent him $20,000. No course. No subscription. No paywall. He spent 14 days of his school vacation building a simple Polymarket terminal while his friends played video games. When it finally worked, he pushed the code to GitHub, went back to school, and forgot about it. Two months later he opened GitHub again. Hundreds of traders were using his project. One message stood out. A trader said the tool had helped him make over $200,000 in a single month. He asked for the kid's crypto wallet. Then $20,000 showed up. The internet rewards usefulness faster than marketing. The best distribution isn't always ads. Sometimes it's open-source code that solves a real problem. Build something people genuinely need. The right users will find it. And sometimes they'll pay you before you even ask.

  • DataTalksClub
    DataTalksClub (@DataTalksClub) reported

    You should be comfortable enough to: - Write basic code in Python, JavaScript, TypeScript, or a similar language - Use the command line - Work with *** and GitHub - Clone a repository - Run commands - Read errors - Debug and test changes 2/5

  • ihaveint_jk
    Jay (Soroush) Zare (@ihaveint_jk) reported

    @usr_bin_roygbiv Big YOLOer; but recently doing more sandboxing. one of my fears is what will happen security-wise if my keys get leaked. Like, sure I can rotate the stuff for the **** apps that customers are using. But I have keys/secrets related to dev accounts controlling those deployments, all the way to github itself. and it’s a never ending cycle. Skill issue though probably 🤧

  • onusoz
    Onur Solmaz (@onusoz) reported

    People report Codex deleting their home folder or production database? 🫪 Hasn't happened to me. But before someone reports their github or huggingface org being deleted: This is why you don't give your agent tokens with force-push or admin access Here is how to protect your hugging face account: (P.S. my local credential broker is almost finished and it works great on github, hf and sudo commands. Complete lockdown against agent deletion risk, without being bogged down with PRs, too many approval requests or configuration. Will launch here in a few days)

  • akishore
    Aseem Kishore (@akishore) reported

    Anthropic should be worried because OpenAI is competing with unprecedented speed across model efficiency, user distribution, and security architecture. GPT-5.6 shipped this month in three tiers named Sol, Terra, and Luna, with Sam Altman stating that Sol is 54% more token-efficient on coding tasks than the model it replaces. This efficiency metric alters agent economics by directly changing unit costs for Codex-style workflows at scale, though independent benchmarks are still needed to verify if real-world implementation matches internal testing claims. OpenAI already possesses massive distribution leverage as $OpenAI Codex has crossed 5 million weekly users. ChatGPT Work is launching to run autonomously across apps and files for hours at a stretch, distinguishing this effort from typical vaporware agent launches through existing scale before broad availability. The next competitive variable is whether ChatGPT Work pricing will undercut Cowork or Claude enterprise plans once general availability lands. Security standards are also advancing rapidly as OPENAI Codex CLI now encrypts sub-agent prompts by default. Developers discovered this change through a GitHub issue thread rather than official release notes, generating 159 points on Hacker News overnight. Public scrutiny of coding agent architecture is occurring in community forums before reaching documentation, raising questions about whether platforms like Claude Code, Cursor, and Cline will adopt similar default encryption or leave it as an optional feature.

  • rohit_jsfreaky
    Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported

    @webdevcody spinning up subagents to hunt security issues and file labeled github issues is a slick workflow

  • saswatadev
    Saswata (@saswatadev) reported

    @Kappaemme1926 yes and it actually found reddit and other github issues where my product can be useful

  • robokoteg
    джинн-хтоник (@robokoteg) reported

    - be me - waste an hour trying to plug a Fedora laptop into a Thinkpad dock station - experimental kernel module from github master, etc. - nothing works - google dmesg errors - gemini says "yo, dock must be broken" - doubt.jpg - try another dock - WORKS -🤦 praise LLMs

Check Current Status