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

  • PixelRainbowNFT
    PixelRainbow (33.3%) (@PixelRainbowNFT) reported

    @grok @xai @grok as soon as you fix the way your github connector or custom connector works, I'll try this out. RN, it's forcing an oauth workflow, so I'm unable to connect with github account in the custom connector UI/UX process. (the normal default github connector works great, but there's only ONE!). I need 10 custom connectors for 10 different gits.,.. 9 custom connectors that aren't broken when trying to auth github.

  • SemanticSamuel
    Sam Cymbaluk (@SemanticSamuel) reported

    @sebastienlorber Github is actually so slow. My TTS writes characters out one at a time after dictation is complete. It works on every website except Github, which drops random characters every few words.

  • _chrisdunne
    Chris Dunne (@_chrisdunne) reported

    @AishwaryaDevv GitHub audit logs are terrible, you have to work around a lot of crap to get visibility, if no one’s reached out by now they’re not even looking.

  • CoppedPepe
    COP 🐸 (@CoppedPepe) reported

    @github love this framing—stop waiting to be “ready” and just ship the typo fix.

  • yong_oku
    OEP 🔺 (@yong_oku) reported

    1. Build in public. Your work needs to exist before your resume does. Essays. Projects. Case studies. GitHub. Shipped products. Threads like this one. An ATS cannot reject a body of work. A founder who's been reading your writing for 3 months already trusts you before you apply. Visibility is the new resume. 2. The listing is the last resort, not the first step. 80% of real jobs are filled through networks before they're ever posted. The posting is what happens when the network failed. Stop spending 80% of your energy on listings. Start spending it on real relationships with real humans. 3. Go direct. Find the person who would actually manage you. Not HR. Not the portal. Not the ATS. The human who wakes up with the problem your skills solve. One real conversation beats 100 applications every single time. 4. Verify before you invest. Before you write a single word of a cover letter, run due diligence: → How long has this listing been up? → Has it been reposted with a new title? → Is this company actually growing — or just posting like they are? → Can you find anyone on LinkedIn who joined in the last 6 months? Treat job listings like investment pitches. Most of them are fraudulent. 5. Build leverage outside the job market. Freelance. Consult. Build something small that earns. Not because you need to quit the job search, but because the person who doesn't desperately need the job, negotiates better, interviews better, and gets the offer. Desperation is visible. Leverage is too. 6. Find the communities where real hiring happens. Discord servers. Slack groups. Niche forums. Alumni networks. Jobs move through conversations before they move through portals. The people who found great roles in terrible markets almost always had one thing in common: they were already in the room.

  • jrmromao
    J Filipe (@jrmromao) reported

    Pivoted CostLens from "AI cost tracking" to "AI productivity measurement" last week. Built in 5 days: - MCP server that tracks what AI agents actually ship - Automated ROI reports for engineering leaders - CLI setup in 30 seconds - GitHub PR correlation Same product, completely different value prop. Before: "save money on AI" Now: "prove AI delivers value" One resonates with finance. The other resonates with everyone. #buildinpublic

  • aki_ranin
    Aki Ranin (@aki_ranin) reported

    New Claude Code master prompt: "/goal assign next GitHub issue and start PR, iterate until no critical or high issues found with PR review skill"

  • lyrie_ai
    Lyrie.ai (@lyrie_ai) reported

    🚨 YellowKey+GreenPlasma (no CVE, NO PATCH): BitLocker bypass + Windows CTFMON→SYSTEM LPE on fully patched Win 10/11/Server. PoC on GitHub by Chaotic Eclipse. Huntress: active attacks within 24h of release. Disable CTFMON & enforce Secure Boot NOW. #ZeroDay #Windows

  • paharihacker
    Rajesh Dhiman | AI Automation & Code Rescue (@paharihacker) reported

    Here's what I keep finding: → Supabase databases with no row-level security — open to anyone with a browser → API keys committed directly to GitHub repos → Auth routes that only check login on the frontend → No rate limiting on anything → Zero error handling in production The AI didn't warn them. It just shipped it.

  • smashsharp
    curio drome (@smashsharp) reported

    @horse_meds @michalmalewicz m very sincerely seeing those things as just amped up search engines. Tbh I could have found any of that you say myself if I took a moment on GitHub and brain grease. It just sped up the search and tbh I don’t like cleaning up AI’s errors

  • DemonKingSwarn
    DemonKingSwarn (@DemonKingSwarn) reported

    @ThePrimeagen at this point my self hosted *** server has more uptime than github which is funny because they have more money than me

  • Ananselab
    John Evans Okyere | TheAISolutionist (@Ananselab) reported

    Deployment failed with: dial tcp :22: i/o timeout The app was fine. SSH was fine. The real issue: I recreated my DigitalOcean Droplet from a snapshot in a new region, so the server IP changed, but GitHub Actions still had the old DO_HOST secret. Lesson: after recreating infra, always recheck IPs, SSH fingerprints, secrets, and firewall rules.

  • PriestruYuuru
    Yuuru (@PriestruYuuru) reported

    @thsottiaux Bro, compaction essentially broken right now. Dunno about everyone but for me it doesn't work most of the time. Steam error end everything, can't provide you with/feedback sadly but team could look into github issues from others. Tried to set compaction earlier but still issues.

  • PDave95
    AllOrNuthin 💀 (@PDave95) reported

    @AgentOS_Inc @AlexandraLiam3 github link is broken

  • fitchmultz
    Mitch Fultz (@fitchmultz) reported

    @badlogicgames @matteocollina Ah! figured it out. It is broken with Node 26. If I launch pi via `mise exec node@24 -- pi` and then /login it works. I can create a GitHub issue.

Check Current Status