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
Bordeaux, Nouvelle-Aquitaine 1
Ingolstadt, Bavaria 1
Paris, Île-de-France 1
Berlin, Berlin 2
Dortmund, NRW 1
Davenport, IA 1
St Helens, England 1
Nové Strašecí, Central Bohemia 1
West Lake Sammamish, WA 3
Parkersburg, WV 1
Perpignan, Occitanie 1
Piura, Piura 1
Tokyo, Tokyo 1
Brownsville, FL 1
New Delhi, NCT 1
Kannur, KL 1
Newark, NJ 1
Raszyn, Mazovia 1
Trichūr, KL 1
Departamento de Capital, MZ 1
Chão de Cevada, Faro 1
New York City, NY 1
León de los Aldama, GUA 1
Quito, Pichincha 1
Belfast, Northern Ireland 1
Guayaquil, Guayas 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:

  • galileowilson
    Galileo (@galileowilson) reported

    The OpenClaw era is over for me. Ever since Opus 4.6 stopped working on it, accounts kept getting banned, was spending more time fixing trouble than actually having it do tasks for me. meanwhile a basic VPS running Claude Code with Terminal, GitHub and Vercel does the same job for me which costs way less money and headaches.

  • skydaddysgg
    SkyDaddysGG (@skydaddysgg) reported

    @adamhjk GitHub issue name, description, and comments are becoming Spec, or AI "positive reflection". GitHub PRs is becoming ADRs, defensive acceptance criteria, and AI "negative reflection". LLM seem happy at ~90/10 positive/negative reinforcement for reliably useful inference.

  • uselooped
    Looped (@uselooped) reported

    1/ The problem isn’t using multiple tools. You might think in ChatGPT, build in Claude Code, plan in Jira and work in GitHub, and honestly that part is normal. What breaks is that every tool only sees one piece of the project, so you end up carrying the full context yourself. Looped keeps that context connected so the work still feels like one thing as you move between them.

  • Scrazelope
    Scraze (@Scrazelope) reported

    @closesttopurple I looked at the github. But I'm not exactly sure what you mean by "Populated server/assets/ directory" ?

  • Feiwu7777144805
    Feiwu7777 (@Feiwu7777144805) reported

    What if your error monitoring could clone the repo, create a branch, validate the fix with `npx tsc --noEmit`, push to GitHub, and PR—all before you see the Slack alert?

  • CodeAndAIHub
    Code & AI Hub (@CodeAndAIHub) reported

    🚫 Coding Mistakes Beginners Should Avoid: • Jumping between languages • Skipping fundamentals • Only watching tutorials • Ignoring problem solving (DSA) • Not using ***/GitHub • Copy-pasting code • Avoiding projects • Not asking for help Build consistently. Not randomly

  • defileo
    Defileo🔮 (@defileo) reported

    > 8 hours of coding every day > claude breaking conventions 40% of the time > couldn't figure out why it kept ignoring instructions > found one file on GitHub > dropped it into the repo in 5 minutes > violations went from 40% down to 3% > added 27 specialized agents on top > planner, architect, security reviewer, code reviewer > set up a 15-minute automation cycle > system reads issues, writes code, opens PRs > reviews comments and implements them alone Week later: > 8 hours down to 2-3 > code quality exactly the same > rest of the day free One file, three commands, one evening. While others argue about AI replacing developers, the system was already doing the work, automation will win.

  • indefatigabile
    ergophobian (@indefatigabile) reported

    @justalexoki openclaw feels like another terminal i need to babysit, but im going to keep trying at it to eventually be able to manage PRs Then i’ll verify myself if its actually getting work done. for me my biggest use case is it takes issues on github submits a PR prob runs greptile on it, then i go and verify and push it while im sleeping. on a loop. but i’m not there yet

  • Santosh74038967
    Santosh Kathira (@Santosh74038967) reported

    @cstanley Claude code is down?!! Then GitHub uptime will finally hit 99.9%

  • abdonrd
    Abdón Rodríguez (@abdonrd) reported

    @themcmxciv Do you have a GitHub issue for this? I can't find it, and I ran into the same problem updating from v16.1.6 to 16.2.3 on a self-hosted Docker setup.

  • MythThrazz
    Marcin Dudek (@MythThrazz) reported

    @a_lamparelli I know! You would think those are free/cheap - they arent. And never were. I think there is actually an issue on Github about it. It misses the KV cache completely afair

  • AlbahadlyIQ
    albahadly (@AlbahadlyIQ) reported

    @github I want to try it, but unfortunately I can't. I have an issue with renewing my subscription, and I opened a ticket to support 9 days ago, but no luck.

  • ElyasWahyain
    Abdullah Elyas | ع. إلياس (@ElyasWahyain) reported

    @icanvardar @zerohedge It’s actually a bug, disabling telemetry accidentally blocks the feature flag check that grants 1-hour cache to Max subscribers. It has been filed as an issue on GitHub. The 1h cache is a Max plan perk, not available to Pro users regardless of telemetry settings 🫠

  • ShashankB16052
    Shashank bindal (@ShashankB16052) reported

    @tengyanAI building production agentic systems on Claude Code daily. the "ignores instructions, claims completion against instructions" behaviour in that GitHub issue is exactly what I've been debugging for weeks thinking it was my fault. it wasn't my prompts. it was a silent nerf.

  • therollupco
    The Rollup (@therollupco) reported

    The CIO of Franklin Templeton Investment Solutions sat down with @andyyy and talked about evaluating projects by GitHub activity and contributor quality. A week later, Good Alexander tweets the same thesis publicly. Active GitHub. Founder hasn't quit. Token down 90%. Two completely separate conversations. Same conclusion. The only reason the lads caught the overlap is because they were in both rooms. That's the vantage point @robbieklages talks about. When you talk to enough people across enough of the market. Patterns surface that nobody else can see.

Check Current Status