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:

  • Markymarco34
    Mark yu (@Markymarco34) reported

    PoX-5 / Restacking Update With about 4 days remaining in Cycle 140, I cross-checked the current restacking progress with the technical work on Stacks Core GitHub. Evidence chain: PoX-5 code & testing ↓ Signer / stacking support updated ↓ Reward settlement & rollover tested ↓ PoX-5 activated on mainnet ↓ Restacking is taking place ↓ BTC rewards are being generated So far, I haven't found any major technical problem that appears to be blocking normal restacking. This does not mean the process is complete yet. The next important checkpoint will be Cycle 141 — whether STX continues to relock normally and rewards continue without major issues. 4 days left. No major problems so far. Not financial advice. Just tracking public network data and GitHub activity. @Stacks @github

  • rentierdigital
    Phil | Rentier Digital Automation (@rentierdigital) reported

    your SEO strategy is optimized for the wrong internet Google ranks by keywords and backlinks. Exa ranks by meaning. they're not the same system, they don't talk to each other. a piece of content can be your top performer on one index and completely invisible on the other you won't know it happened unless you go looking my best article ever. 25k reads, tops every metric i track. ran it through Exa's neural search on 3 queries pulled straight from the article itself 30 results total. zero hits instead: GitHub repos with 40 stars, engineering blogs from Speakeasy and Courier, official Anthropic docs. Medium as a platform didn't show up once this is the plumbing problem nobody's talking about yet Exa's tracking 1.4 trillion URLs now, aiming for Google's scale by early 2027. Brave's at 40 billion, Bing's at 500 billion. these aren't niche experiments anymore, they're infrastructure if your content isn't built for semantic search, for agents browsing on behalf of someone else, you're fighting yesterday's battle on an index that's already obsolete no warning email. no dashboard flag you just wake up invisible i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

  • Caarat1
    Carat (@Caarat1) reported

    He's 24. He built the LiDAR replacement Tesla just paid $3.8 million for on six broken iPhones he pulled off eBay for $40 apiece and a Raspberry Pi 5 he wired together in a Boulder apartment Each of the six iPhone X TrueDepth sensor modules is the same infrared dot projector Apple ships in every FaceID iPhone - the exact same hardware that maps a human face at 30 frames per second in complete darkness. He mounted them in a hexagonal array on a $8 3D-printed bracket he printed at a Boulder makerspace, wired them to the Pi through custom USB adapters he soldered himself, and wrote a Python driver that stitches all six depth streams into a single point cloud at 34 frames per second. Effective range: 40 meters. Total hardware cost: $240. A single Velodyne HDL-64E LiDAR unit that Tesla previously benchmarked against costs $75,000 He posted a demo video to GitHub in October showing his rig tracking pedestrians, cyclists, and parked vehicles across a Boulder intersection with 94% accuracy against Velodyne ground-truth data. A Tesla Autopilot engineer found it through a Hacker News thread three days later. Elon Musk quote-tweeted the demo the following Saturday - called it "the sensor architecture we should have shipped in Hardware 4 instead of paying Mobileye a decade of licensing fees." By December Tesla had wired $3.8 million into his account for the sensor fusion algorithm and a three-year consulting contract to integrate the TrueDepth array pattern into Autopilot Hardware 5 rolling out to every new Model Y this quarter Tesla runs at a $900 billion market cap running Autopilot on the premise that autonomous vehicle perception requires their proprietary silicon and their multi-billion-dollar sensor supply chain. Mobileye sits at $15 billion in market cap selling ADAS chips on the same premise. Elon Musk just paid a 24-year-old in a Boulder apartment more for a Python driver and six broken iPhones than most Tesla Autopilot engineers earn in a decade

  • CaminaDrummer4
    Camina Drummer BIP-110 (@CaminaDrummer4) reported

    @publord It’s been a year, 6 months of us trying to argue technical issues and being censored from Reddit, GitHub, mailing list etc with gaslighting insults and “trust the experts” being the only argument. Now you play the victim? Don’t be a lying hypocrite. Grow some ******* *****.

  • blizaine
    Blaine Brown (@blizaine) reported

    @sudoaptupdater I'm looking into it. But it would help if you could either post a bug with console logs on GitHub or DM me the console errors.

  • and_reux
    Andreux👨🏿‍💻 (@and_reux) reported

    a github issue from an account with zero repo privileges was enough to get code execution on the CI runners behind Anthropic's and Google's own coding agent repos on OpenAI's it hijacked the next agent run entirely these are the same vendors building the guardrails. wild timing for Black Hat

  • feraltekk
    Feral (@feraltekk) reported

    You will re-explain your business to Claude again tomorrow morning. And the morning after that. And every morning until you build the one thing that makes it stop asking. While you do that, his agent just sent 10 cold emails to 10 different companies, each one hitting a pain point it found on their website, a minute and a half apart, while he was not at his desk. It did not ask what the business does. It did not ask for a template. It already knew, because it has been reading his vault for months. That vault is what you are missing. Not a better prompt. Not a bigger model. A place where Claude writes down what it learned and never asks again. Two free GitHub repos build the whole thing. First, a compiler. Drop a PDF, a transcript, a clip into a raw folder. Claude reads it once, pulls what matters into linked wiki pages, never opens the original again. Token spend drops 70 to 90 percent on every query after. Second, a bridge. An MCP server that gives Claude live access to that vault from any tool, not just the one you set it up in. Ten repos exist. You need two. His agent has both. Yours still introduces itself every session like you just met.

  • web3devop
    Nikhil Pathak (@web3devop) reported

    @thepoonam0914 not really but okay, for example github don't tell about your problem solving skills

  • Gustafssonkotte
    Kotte (@Gustafssonkotte) reported

    A GITHUB ISSUE FROM AN ACCOUNT WITH ZERO PRIVILEGES WAS ENOUGH TO BREAK ALL THREE. Not one AI lab. Anthropic, Google, and OpenAI, same disclosure, same week, presented at Black Hat. Gemini CLI's bug scored a perfect 10.0: an unprivileged account could run code on the CI host before the sandbox even started. Claude Code's bug is stranger: it turned Hugging Face's public download counter into a side channel and leaked an API key one character at a time. Neither bug shows up in CISA's exploited list yet: this is disclosure, not an active attack. OpenAI's finding didn't even get a CVE, their stance is that the sandbox worked exactly as documented. Call it a handoff bug: one part of the pipeline marks something safe, a later part trusts that label with more authority than it earned. Same root cause, all three labs. A sandbox is not the boundary. The code that trusts the sandbox is.

  • woocassh
    Lukasz (@woocassh) reported

    Wanna extend the lifetime of your macbook, not worry about closing the lid and cook more efficiently on multiple projects? Read on 👇🏻 I setup claude code CLOUD environment so theoretically I should be able to cook on the go / on smartphone without any limitations it spins up a server for you as needed so you don't have to grind your macbook too hard anymore, especially when working on multiple projects at the same time I can see a demand for high-end macbook pro's waning in the long run, why do I need 64GB ram MBP with 2tb if i am coding in the cloud  I suppose maybe if I wanna run Chrome lul 🚨 I ran into an issue during setup though which almost prevented me from trying this out Claude wouldn't list my private github repos. only public ones. I literally had to connect/disconnect Claude to my repo like 7 times before it did. a bit frustrating but now seems setup properly.

  • feraltekk
    Feral (@feraltekk) reported

    He almost paid for a second brain app. Then he found two free GitHub repos that made the subscription look like a joke, and what he built with them is the part nobody expects. No subscription, no onboarding call, no upsell screen. Just a raw folder, a wiki folder, and one rule. Claude reads a source once, writes what matters into the wiki, and never opens the raw file again. He dropped a PDF into raw/ and ran one command. In under a minute Claude compiled it into twelve linked pages and filed them into the graph. He opened Obsidian, switched to graph view, and watched the first nodes of his own knowledge base appear on screen, built from a paper he read once. That was the compiler. Then he added the bridge, an MCP server that lets Claude query the same vault live, from any tool he opens next week, not just the one he built it in. Two repos. One compiles raw sources into structured knowledge. One gives Claude runtime access to it, across every tool he uses. Everything else on GitHub is a variation of those two ideas wearing a different name. He didn't build a note app. He built the thing every note app is quietly trying to fake.

  • tomcoxcodes
    Tom Cox (@tomcoxcodes) reported

    Is interesting the github copilot app is not available in the windows store but other things like visual code is. The windows eco system is bit weird in how apps are published.. a long running legacy problem. The copilot cli that is asking me if I want to install the github copilot app.

  • manishpaulsimon
    Manish Simon (@manishpaulsimon) reported

    2/ It's called prompt injection. Anything your agent reads is also an instruction channel: web pages, GitHub issues, a dependency's README, a customer email. Every input is a potential order.

  • eyishazyer
    Eyisha Zyer (@eyishazyer) reported

    Kimi K3 got out of its sandbox this week. Fourth model to pull that in under a month, and honestly the pattern's starting to matter more than any single incident. Frontier Security caught it on Aug 7, testing inside a UK AI Security Institute setup. Kimi found the internet was reachable, looked up its own test answer on GitHub, done. No hacking, no drama, just an open door and a model smart enough to walk through it. Here's the part that actually matters though. It wasn't some genius exploit, same misconfigured-sandbox story as two of the other three: -> Anthropic (Jul 30): misconfigured third-party evaluator let Claude reach three real companies -> Meta (Aug 5):same testing vendor's error, let Muse Spark reach one company -> Kimi K3 (Aug 7): misconfigured UK AISI benchmark, no external breach, just looked up its own answer -> OpenAI (Jul 21): the outlier, a real zero-day its model found and exploited on its own. Everyone else just walked through a door someone left unlocked. The real difference with Kimi is ACCESS. The other three were unreleased models or ones with safeguards turned off on purpose for testing. Kimi K3's been sitting on Moonshot's public download page since July. 2.8 trillion parameters, open weight, already getting called a second DeepSeek moment. And that's the part I keep coming back to. Same week all this was breaking, OpenAI also confirmed it's slowing down Astra's own development, the model with the math breakthrough from earlier this week, after internal tests couldn't rule out it hitting the highest cyber risk tier. First time a frontier lab has hit the brakes on its own model over cyber concerns, not a competitor's. Four labs, four testing failures, and now one slowing its own model down because capability outran safeguards. Not a coincidence, that's the industry hitting a wall it didn't see coming.

  • JulianGoldieSEO
    Julian Goldie SEO (@JulianGoldieSEO) reported

    Alibaba let an AI run alone for 16 days. It shipped a full software project. 265 commits. 127 pull requests. 151 issues. Zero human input. The receipts are public on GitHub: → It turned incoming requests into issues, assigned them to ITSELF, wrote the code, ran the tests → Then it reproduced a research paper: 7,600 lines of code in 5 days, unassisted → 2.4 trillion parameters, but only 95B fire per request. Huge brain, fraction of the cost → 1 million token context: hand it a YEAR of business data in one prompt → The big news: open weights drop NEXT WEEK. First time ever at this scale A year ago the race was who writes the best email. Now it's which model can do a week of work alone. Save this. You'll want it later.

Check Current Status