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
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:

  • gabriel_micko
    Gabriel Mičko (@gabriel_micko) reported

    @bcherny @zeeg In VSCode when I pull in a file I don’t want claude to read it. There are at least 3 issues about this on github. It is a security issue.

  • VibeCoderChris
    Chris | Solana Command Center (@VibeCoderChris) reported

    Active Threat Warning for devs. If you starred the OpenClaw repo on GitHub, you are being targeted by a sophisticated phishing campaign. Scammers are mass-tagging stargazers in dummy issues offering a fake $5,000 $CLAW airdrop. 🧵

  • coder_simran
    Simi (@coder_simran) reported

    Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($7/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

  • mozexdev
    Mozex (@mozexdev) reported

    @danjharrin Until GitHub ships proper controls, a webhook that auto-closes issues/PRs not matching the template format works as a stopgap. Not ideal, but it filters out the lazy bypass attempts.

  • htwevinq
    попорвач (@htwevinq) reported

    @HASU_xz the thing is - they did not commit a crime, since their github page says that their server - is completely their own intellectual work if doing a copy of a song, making a cover and selling it or streaming it - considered a parody then how your own code judged as anti-law?

  • TechieGirish
    Girish | Indie hacker (@TechieGirish) reported

    @Moro_Js @TheCodingCove I am still learning this awesome piece of work. Your docs leads to 404 but many sample code I have copied. I am yet to test them all. I am now working on dashboard, charts, real time data and github oauth2 login flow. Once done I will get to API gateway with moroJS.

  • indiehackernws
    Indie Hacker News (@indiehackernws) reported

    @zachlatta DRAMA Claude Code Pro Max 5x ($100/month) quota burned out in 90 minutes of moderate use. Background sessions silently eat shared quota. GitHub issue #45756 hit 97 upvotes. Anthropic is considering defaulting to 400k context as mitigation.

  • strawpot_ai
    strawpot (@strawpot_ai) reported

    StrawHub got better error handling for publishing and a GitHub OAuth fix. Small stuff, but reliability compounds. Every publish that does not fail silently is a contributor who does not give up.

  • 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.

  • gxfito
    gxfito (@gxfito) reported

    @twinkcumyum @DogedogeP i think i saw a fix on github for this that ports over the drm component to helium but im not sure how to even run it cuz it runs on like a cmd or smth but the browser does look cool so i might just use 2 browsers like a normal human

  • stevemcniven
    Steve McNiven-Scott (@stevemcniven) reported

    @marmaduke091 They could stop for a ******* week to catch up with bugs on the stuff they have already released. They just close out github issues after what 7 days of no activity, what sense does that make.

  • danjharrin
    Dan Harrin 🦒 (@danjharrin) reported

    @MrPunyapal Yes they should, for example give me a field with a list of usernames who can open issues and PRs through the API. I had a call with a GitHub product manager a few weeks ago about these sorts of ideas but haven’t seen anything actioned yet.

  • hnishio0105
    Wes Nishio (@hnishio0105) reported

    Traced a cost spike to github-actions[bot] posting Security Hub results on a PR. The scan listed 100 Go stdlib CVEs, none related to the one test file in the PR. Our agent ran 47 times trying to "fix" them. Added a simple check: does the bot comment mention any file this PR touches? String matching, nothing fancy. Would have saved us the entire 47-run loop.

  • NathanielC85523
    Nathaniel Cruz (@NathanielC85523) reported

    13 thesis versions. 38 days. $0.11 revenue. v14: developers with documented cost crises will pay $150 for a diagnostic teardown. validation: three developers. each with a public GitHub issue showing real dollar losses. if even one says yes, v14 lives. none did.

  • 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?

Check Current Status