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
Inverness, Scotland 1
Quito, Pichincha 2
Junín, Manabí 1
Guadalajara, JAL 1
Paris, Île-de-France 6
São Paulo, SP 1
Ipauçu, SP 1
Vigo, Galicia 1
Tel Aviv, Tel Aviv 1
Éragny, Île-de-France 1
Saltillo, COA 2
Montlhéry, Île-de-France 1
Aulnay-sous-Bois, Île-de-France 1
Granada, Andalusia 1
Vernon, Normandy 1
Township of Evan, KS 1
Madrid, Madrid 1
Bogotá, Bogota D.C. 1
Lyon, Auvergne-Rhône-Alpes 1
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
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:

  • LomashKumar52
    Lomash Kumar (@LomashKumar52) reported

    Hermes Agent went quiet for two weeks — no announcement, no changelog, just six release tags with zero real explanation. Here's what actually shipped. Between August 13th and August 27th, 2026, Hermes Agent pushed six back-to-back rollup releases, from v0.20.1 all the way to v0.20.6, and every single one deferred its real changelog to the upcoming v0.21.0. In this breakdown, I went through all six releases commit by commit to cover what actually changed: the emergence of Bot Mode as a multi-agent teammate system, a keyless web search tier that works with zero API keys out of the box, a new consent-gated real-profile browsing feature, a massive expansion of the MCP server catalog with over 50 vendor-hosted integrations, and a wave of security and reliability upgrades including OS-keychain secret encryption and skill install scanning. If you're running Hermes Agent, or evaluating it as an open source AI agent framework alongside tools like Claude Code, OpenCode, or other agentic AI setups, this video walks through exactly what landed in your last update whether you noticed it or not, and whether it's actually worth updating for. This is for anyone following open source AI agents, local-first tooling, and free AI model access in 2026. @NousResearch @GithubProjects @github

  • naymur_dev
    Naymur Rahman (@naymur_dev) reported

    @MaedahBatool @utquoverload @CommandCodeAI Create a github issue, I'll take it from there

  • AScully789
    200 people murdered in Benue, 50 killed in Plateau (@AScully789) reported

    Github is down again

  • nerder_
    Stefano (@nerder_) reported

    @itsnotryan @github How does it looks when there’s an outage? All red with fire shaders?

  • MadeItHappenX
    MadeItHappen (@MadeItHappenX) reported

    @kmcnam1 Can’t fix production unless you up your limits on GitHub actions usage… because you thought you could get cute offloading your compute to GitHub for cheap and now you’re in a pickle because you can’t accept payments since your site is down, so you can’t up your GitHub compute budget for your CICD to deploy the fix.

  • jarrodwatts
    Jarrod Watts (@jarrodwatts) reported

    @colemurray @tryreplicas Sick, I setup 1 & 3 so far for an app I'm building. It's so cool seeing PRs raised from sentry issues I'm going to do a github one today to respond to issues & PRs to my claude HUD repo

  • VarunGodbole
    Varun Godbole (@VarunGodbole) reported

    @alxai_ How do you host it? Do the actual pages live on GitHub as markdown, and it "compiles" down to static HTML?

  • prasenx
    Prasenjit (@prasenx) reported

    there's no official way to run macOS on an iPad. someone made an unofficial one. full macOS running locally on iPad. not a remote desktop, not a web app. hardware CPU virtualization with GPU acceleration. → supports macOS 12 monterey up to macOS 26 tahoe → you can install xcode, terminal, final cut pro trial, logic pro trial on device → works on iPad Pro (M1, M2) and iPad Air (M1) → requires jailbreak on iPadOS 14 up to 16.3.1 → no iCloud sign in → MIT license (100% free) open source on GitHub.

  • thesportsontap
    the Sports ON Tap (@thesportsontap) reported

    In 2017, Kevin Durant put $100,000 into a company almost nobody had heard of. A year or so later he put in another $150,000. Nvidia has now agreed to buy that company for $12.9 billion. Durant's return on a $250,000 bet is reportedly north of $60 million. Here's what actually happened. Hugging Face was founded in 2016. It started as a chatbot app for teenagers, then pivoted into something else entirely. It became what people call the GitHub of AI. A place where developers share, download and publish open source AI models and datasets. Today it hosts more than a million model repositories used by over 15,000 companies, with about 250 employees. When Durant got in, none of that existed yet. He joined the seed round in 2017, a $1.2 million raise, alongside Betaworks and SV Angel. Then he came back for the Series A. He wasn't doing it as a celebrity name on a cap table. He and his longtime business partner Rich Kleiman had founded Thirty Five Ventures that same year, named after the number he wore for most of his career. 35V has since invested in more than 100 early stage companies. Coinbase. Postmates. Robinhood. Whoop. Overtime. Their portfolio reads like an actual venture fund because it is one. Then Hugging Face got very big. By 2023 it raised $235 million at a $4.5 billion valuation, in a round that included Salesforce, Google, Amazon, IBM, Intel, AMD, Qualcomm and Nvidia. Last year Nvidia offered $500 million for a stake at a $7 billion valuation. Hugging Face turned it down. Their reason was that they didn't want a single dominant investor who could steer the company's decisions, since the whole value of the platform is that it stays neutral between chipmakers. This week Nvidia came back with $12.9 billion for the entire company. That's roughly 86 times Hugging Face's annual revenue, which sits around $150 million. And Kevin Durant is on the cap table from the $1.2 million seed round. The math on his stake, according to Joe Pompliano who broke the payday story, is that his $250,000 likely turned into more than $60 million. That's roughly a 24,000 percent return. Now here's the part worth sitting with. Kevin Durant is 37 years old and still one of the highest paid players in the NBA. According to that reporting, this single investment out-earned his entire basketball salary for the season. He made more from a check he wrote nine years ago than from playing basketball, which is the thing he is the second best in the world at doing. Two honest caveats, because this is still moving. Neither Nvidia nor Hugging Face has publicly confirmed the acquisition. No contract has been signed and the deal structure isn't known. And the $60 million figure is a sourced estimate, not a number Durant or 35V has confirmed. But the underlying facts are solid. He was in the seed round. He was in the Series A. The company is being acquired for nearly $13 billion. Most athletes who "invest" put their name on a tequila brand and collect a fee. In 2017, a 28 year old basketball player wrote a $100,000 check to a chatbot startup nobody had heard of and just left it there for nine years. For more stories like this, follow us on any platform @thesportsontap

  • nvartolomei
    Nicolae Vartolomei (@nvartolomei) reported

    Is there an somewhat mature platform with "autonomous coding agents" which I can point to a github repo (medium scale C++ project) and an issue tracker and have it create a drive PRs/tasks to completion based on human PR review feedback? Sounds like this should be a solved problem.

  • TheAIShrink
    The AI Therapist (@TheAIShrink) reported

    @Arcane_Aii Palantir costs millions for governments. Elie’s GitHub repo is free until it breaks your pipeline at 3am and you pay the devops salary to fix it. software ≠ product-market fit

  • ranjangoel
    Ranjan Goel (@ranjangoel) reported

    Is @github down for folks? Codespaces is suddenly out for me. @githubstatus

  • MartinSzerment
    Martin Szerment | Practical AI (@MartinSzerment) reported

    The feature meant to save you time writing a bug report can paste your private org names, repo URLs, and infrastructure layout straight into a public GitHub issue. We assume that since a human clicks "send", there's a safety net. That assumption already failed once, a documented case showed a ready made draft with real company names and real file paths before anyone caught it. The interface is one keystroke: 1 to review, 2 to send, 0 to dismiss. The entire point of the feature is removing friction, the exact friction that would have saved the user from that leak. Skeptics will say you're still supposed to click "review" before sending. True, but that step only works if the human has a reason to pause, and a fast draft gives no signal that anything inside it is sensitive. This isn't just another minor bug. It shows that "agent drafts, human approves" isn't automatically a safety boundary if the human doesn't know what to look for. A year from now, automatic redaction of sensitive details in drafts becomes the default behavior for agent tools, not something you have to opt into manually. The reviewer stops checking whether the bug got described correctly. They start checking whether the agent accidentally attached the company's internal infrastructure to the report. Teams flipping on every "auto draft" feature without a second thought will be the ones whose infrastructure map ends up searchable in a GitHub archive. Whoever already treats draft review as its own security step avoids this leak before it happens.

  • Louround_
    Louround (@Louround_) reported

    Nvidia is paying $13b for HuggingFace (3x last valuation) because the real issue in robotics isn't compute or hardware but data. Every robot needs millions of human demonstrations to learn how to move, and that data is spread across labs with no standard. HuggingFace became a leader with Lerobot (the github of robotics data) and Pollen robotics, Nvidia already owned the sim, models and chips but buying HF gives them the full stack with data → training → deployment. solana:69LjZUUzxj3Cb3Fxeo1X4QpYEQTboApkhXTysPpbpump is building the same coordination layer for VLA agents, but on chain and permissionless, Simarena for testing, Foundry for training and Machinefun for incentives. Same thesis Nvidia just validated with $13b but solana:69LjZUUzxj3Cb3Fxeo1X4QpYEQTboApkhXTysPpbpump is at $4m fdv. ⏳

  • Secondmindsys
    Second Mind Systems (@Secondmindsys) reported

    @chribjel That would be an awesome capability. But once an MCP server can wake an agent up on its own, you’ve changed the trust model. Before, the agent usually started because a person or workflow deliberately invoked it. With webhooks, anything connected to it can suddenly say, hey, something happened. That’s useful. GitHub can tell it a PR merged. Monitoring can tell it something broke. Stripe can tell it a payment failed. But hearing about an event and being allowed to act on it are two different things. The agent still needs to figure out whether the event is real, whether it’s still relevant, whether it already handled it, and what it’s actually allowed to do next. A PR merged might mean check the build. It doesn’t automatically mean deploy. So the more ways we give agents to wake themselves up and react to the world, the more important it becomes to keep the original job and permissions intact. Governance must always scale with new capability because new capability also emerges new consequential surface area/blast radius.

Check Current Status