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

  • Timur_Yessenov
    Timur Yessenov (@Timur_Yessenov) reported

    @siloagents @trq212 I’d separate two layers: remote control from Telegram is easy; reliable Claude Code channels are really about auth, session resume, and permission prompts not getting lost. if GitHub issues are piling up, the UX problem is probably state, not chat.

  • iamkazihasanali
    Kazi Hasan Ali (@iamkazihasanali) reported

    Most users when they love the product, mostly say nothing or give a 5 star rating. this guy wrote me a 1 page long email, compared it to competitors and github projects, mentioned he tried building it himself in Python 2 years ago and gave up then still took time to report a small DST bug. That kind of feedback is worth more than any 5-star review. The fix is shipping.

  • Karanjotdulay
    Karanjot Singh (@Karanjotdulay) reported

    Day 3 of building in public. Shipped my first MCP server: wiki-hub-mcp. Your LLM reads a source once and writes structured wiki pages to a GitHub repo you own. No vector database. No RAG pipeline. Plain markdown files that grow over time. 18 tools: 1) Add sources (URLs or text) 2) Search with BM25 3) Track contradictions 4) Run health checks npx -y wiki-hub-mcp

  • phineasGuo
    Phineas Guo (@phineasGuo) reported

    @github I just reported this error, and hope it can be fixed

  • jaditya8889
    aditya Jindal (@jaditya8889) reported

    @Hollylovestech Tried your website, faced a couple of issues. OpenAI error while parsing resume, do you have a fallback setup? retries? When I try connect GitHub, it redirects to GitHub OAuth with: client_id=undefined So client ID is missing. Looks like the GitHub client ID env/config is not set in production.

  • Nalderman37
    Nathan Alderman (@Nalderman37) reported

    @bcherny Yes, it’s true but with a couple of caveats. Chrome has browser timeouts so what worked for me is the stealth browser GitHub repo and that solved a lot of browser automation problems for me. With that tool +cowork, you can do anything.

  • jpschroeder
    Justin Schroeder (@jpschroeder) reported

    @ThePrimeagen If you look into it this is actually another GitHub issue

  • marlbor_bro
    Big Al (@marlbor_bro) reported

    @EricRichards22 Sounds like a joke but asking my boomer manager to engage in some requirements analysis through a GitHub issue thread instead of countless meetings is like asking a Roman soldier to use a gun

  • dbmikus
    Dylan Mikus (@dbmikus) reported

    Built an agent on top of @amikadev to auto-implement every Linear issue in a project in parallel It spins up a bunch of sandboxed coding agents on @daytonaio, then makes a PR for each issue and watches Github Actions and auto-fixes any problems Doesn't one-shot every issue, so I can SSH into each sandbox and run Claude or Codex to finish things up

  • felipfernands
    Felipe Fernandes (@felipfernands) reported

    @alexwtlf lmao claudevirus sounds like a github issue that escaped into the wild

  • FarmingWithYHWH
    Failure is an option (@FarmingWithYHWH) reported

    @Hesamation Yup - just this morning, GitHub was down again.

  • imdevPU23
    Priyanshu (@imdevPU23) reported

    - Claude for coding. - Supabase for backend. - Lovable for frontend. - Vercel for deploying. - Namecheap for domain. - Stripe for payments. - Resend for emails. - GitHub for version control. - Clerk for auth. - Cloudflare for DNS. - PostHog for analytics. - Sentry for error tracking. - Upstash for Redis. - Pinecone for vector DB. You can literally ship a startup from your bedroom now. It’s not even cost much many of them give free initial credits

  • anshumanjazz
    Anshuman J. (@anshumanjazz) reported

    Hot take: in 2026, your GitHub profile matters less than whether you've shipped an AI agent to ****. Knowing how to build one, handle tool failures, manage context, and keep costs sane, that's the new senior engineer checklist. The devs who figure this out now won't be looking for jobs. They'll be turning down them. have you shipped one yet?

  • wutronicai
    Lukasz (@wutronicai) reported

    mixed results on other tests though: it trails Claude at 58.6% vs. 64.3% on SWE-Bench Pro for GitHub issue fixes

  • Anas_is_me
    Anas (@Anas_is_me) reported

    5/6 Note: In a real pipeline, you don’t want to see every tiny issue. You only want to stop the build for big stuff. Using --severity HIGH,CRITICAL --exit-code 1 tells Jenkins or GitHub: "If you find a major hole, stop the deployment right now."

Check Current Status