1. Home
  2. ❯
  3. Companies
  4. ❯
  5. GitHub
  6. ❯
  7. 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:

  • asiyaps_
    asi (@asiyaps_) reported

    call her github the way she keeps going down on me

  • h3xhammer
    ShWnD (@h3xhammer) reported

    A fork of the original N!ghtm@re 3cl!pse BL bypass might still be available on GH: MS can get fukt. Fix your sh!t, don't cens0r. fckng tw@ts

  • AItheoryx
    AI Theory (@AItheoryx) reported

    Microsoft is building a super app that combines all of its Copilot tools into one place. GitHub Copilot. Copilot chat. Copilot Cowork. And a new agentic workflow tool internally called Autopilot. One interface. One destination. One login. The internal slogan is Delivering one Copilot. Here is why this is happening and why it matters. Less than 4.5% of Microsoft 365's 450 million customers pay for Copilot features. That is one of the worst conversion rates for a major enterprise AI product. The reason according to sources is simple. Customers hate switching between different Copilot tools. The fragmentation is costing Microsoft money. GitHub Copilot has 4.7 million paid subscribers at $10 a month minimum. But it is losing ground fast to Cursor and Claude Code. Microsoft's consumer Copilot chatbot is significantly behind ChatGPT and Gemini in active users. Microsoft was the first major tech company to make a serious AI bet. $13 billion into OpenAI in 2023. They had a two year head start on almost everyone. They spent that head start launching multiple versions of Copilot that confused customers, splitting their teams between consumer and enterprise, and relying heavily on OpenAI models while competitors built their own. The super app is the attempt to fix all of that in one move. Launch is targeted for end of summer 2026. Some elements may surface at Microsoft Build next week in San Francisco. The app itself will not be shown yet. Satya Nadella promoted Jacob Andreou in March specifically to unify the Copilot product line. This super app is Andreou's primary assignment. Microsoft still has 450 million Microsoft 365 customers. If the super app moves conversion from 4.5% to even 10% that is tens of billions in new recurring revenue. The lead is gone. The distribution is not.

  • VincentAyorinde
    Vinay ⚡️ (@VincentAyorinde) reported

    Fix 5: Scan with Zizmor pip install zizmor zizmor .github/workflows/ Catches dangerous configs, script injection risks, and overly permissive tokens before they reach your main branch. Free. 2 minutes to set up.

  • mildsky1215
    Eji (@mildsky1215) reported

    @ntotao @xai Cleanest setup: ~20 real GitHub issues that ship with test suites, run each model agentically until tests pass (cap at N turns), then log median turns-to-green, total $, and % solved. SWE-bench Verified is the closest public proxy but it under-weights turn-count and cost, and turn-efficiency is the number nobody publishes.

  • peterfox
    Peter Fox (@peterfox) reported

    Today's the first day where I've really seen just how clumsy and poor the UX of @github is. We really need a better way to work. If more effort was put into the UX instead of stuffing AI in, we wouldn't have this problem.

  • dave_barnwell_
    Dave Barnwell (@dave_barnwell_) reported

    GitHub continues to be unusable as soon as the USA comes online (yes I live in Europe). It is time to quit GitHub, a platform that has served me and many devs well. Every large scale platform has instability issues now and again, but weeks of distribution is unacceptable to me.

  • disismohi
    Mohi 🇮🇷🇩🇪 (@disismohi) reported

    I'm not saying every exploit belongs on GitHub. But the inconsistency is the problem. Either you allow security research or you ban all offensive tooling. You can't pick based on vendor pressure.

  • shivkmojha
    Shiv (@shivkmojha) reported

    The sources: Stripe — failed charges, failure codes, revenue at risk Sentry — fatal + error exceptions that correlate to the failure window GitHub — recently merged PRs (the deploy that likely caused it) Datadog — triggered monitors (error rates, latency spikes)

  • Aaronontheweb
    Aaron Stannard (@Aaronontheweb) reported

    Netclaw just kicked off 300 something dependabot updates across all of our repositories, so you know who to blame if there's a GitHub Actions outage in the next 30 minutes or so

  • GitForge_io
    Gitforge (@GitForge_io) reported

    GitForge is different because we’re not just building another @Base app. We’re giving GitHub repos their own onchain operating layer. A repo can hold capital, fund issues, pay contributors, and coordinate AI agents directly from the development workflow. Most tools sit outside the repo. GitForge makes the repo the entity. Built on Base for fast, low-cost execution at software scale.

  • themishra4402
    Rahul 🥷 (@themishra4402) reported

    @raajtalluri the next trillion dollar idea is probably sitting on github today with 12 stars and a terrible readme

  • DharanGanesan
    Dharan (@DharanGanesan) reported

    A single GitHub issue got 27 pull requests from AI bots. Most were untested. Some hallucinated entire implementations. The real contributors? Buried under noise. The fix is a *** hack most devs don't know about. GitHub's "Limit to prior contributors" setting blocks everyone who hasn't committed before. But you can whitelist real humans with *** commit --author using their noreply email. Credits them, doesn't need their SSH key. We built systems assuming contributors are humans. AI bots exploit that because GitHub can't tell the difference. Maintainers spend hours cleaning AI slop instead of reviewing real code. This is a maintenance crisis nobody wants to name. #AI #OpenSource

  • Otisarbitrage
    𝙊𝙩𝙞𝙨 (@Otisarbitrage) reported

    Step 4: Agent synthesizes and acts. It reads submissions, identifies common friction points, generates a bug report, and creates a GitHub issue automatically. Step 5: Amplify the launch announcement. Same agent fires an X raid on the launch tweet for $2.50 - 50 likes, 20 reposts

  • porktoolbox
    pork (@porktoolbox) reported

    So many open-source apps in GitHub are now "vibe-coded" with AI. I've just seen it short-sightedly fixing bugs while creating other problems in a famous niche app. It's sad to see. Where would this evolve into?

Check Current Status