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
Créteil, Île-de-France 1
Trichūr, KL 1
Brasília, DF 2
Lyon, Auvergne-Rhône-Alpes 1
Tel Aviv, Tel Aviv 1
Rive-de-Gier, Auvergne-Rhône-Alpes 1
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
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
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:

  • iainherd
    Iain Herd (@iainherd) reported

    @PrisonPlanet How can you ban text, eg open source code on GitHub, that I download and build freely (eg wireshark) and host on £4 virtual server, anywhere in the world. 10-14 yr old geeks (this is not difficult) will be doing this and changing there mates for access to their private VPN.

  • neogoose_btw
    Dmitriy Kovalenko (@neogoose_btw) reported

    I actually don't think that *** is great. It was designed for reviewing patches by mail which is actually still a way better experience than github. It implies a few problems: 1) your patches need to small 2) there is no built-in relation between commits (stacking patches = sending several emails in RE) when you do a pull request with 12 commits you do absolute bs according to original design 3) there is no seamless way to stack 2 branches on top of each other without mutating the state 4) there is no way to mutate arbitary commit in the history (don't try to tell me about fixup!) - *** was designed to send a single commit patch that is merged to the main - it was never meant to represent an ongoing feature branch work

  • pepeller
    Pedro Pellerini (@pepeller) reported

    If Mythos/Fable is so great why are there still 8386 open Github issues in Claude Code repository.

  • noisyb0y1
    Noisy (@noisyb0y1) reported

    OBSIDIAN IS USELESS WITHOUT THIS GITHUB REPO - AND WITH IT YOU CAN RUN 1,000 AI AGENTS WHILE YOU SLEEP without Obsidian Mine it's just a pretty note organizer - with it Claude Code reads the vault in real time, updates notes automatically and pulls data between sessions without losing context one skill connects Claude Code to all your vaults as a bridge - and unlocks everything described in the article below 1,000 agents in 30 days - orchestrator breaks the goal into tasks, delegates to specialists, a judge from a different model family verifies the result - all while you sleep the main rule: the orchestrator never does the work itself - it thinks, splits, delegates and checks verifiable task - the agent hill-climbs it overnight and you wake up to a solved problem clients pay $3,000-5,000 for research reports this system generates in 2 hours prompting was last year's skill - orchestration is the skill now full breakdown on how to connect Obsidian to Claude Code - in the article below

  • itspriionly
    Priyansh (@itspriionly) reported

    The IT market is broken, and nobody wants to admit it. Someone spends 6 months sending out resumes. Six MONTHS. They learn React, Next.js, TypeScript, AWS, Docker. They take courses, build projects, improve GitHub profiles, optimize LinkedIn. Nothing. Complete silence. Companies don’t just want programmers anymore. They want someone who codes, shines in meetings, makes memes on Slack, and lives the company culture 24/7. AI is replacing junior work. Seniors are holding onto senior roles. And somewhere in the middle are people with 2–3 years of experience who somehow still feel invisible.

  • StefanoMarchty
    Stefano Marchetti (@StefanoMarchty) reported

    The 5 steps that turn a voice note into a live product: 1. Talk out your idea like you're telling a friend 2. AI turns it into a 6-block spec 3. AI writes the instructions for the coding agent 4. The agent builds it autonomously (you go get coffee) 5. Test → GitHub → deploy No CS degree. Just real understanding of the problem you're solving. That barrier is gone. It's not coming back.

  • BruzWJ
    BruzWJ (@BruzWJ) reported

    @thdxr ngl im kinda tired of every funded lab shipping a github competitor, my read is the *** host was the easy part the part nobody rebuilds is the issues + CI + review muscle memory baked into the org

  • zaygranet
    Isaiah Granet (@zaygranet) reported

    @github we have been trying for 48 hours+ to get in touch with someone. We literally cannot retry our billing and are getting a 'doctype' error when trying. Please please reach out.

  • suraj_sharma14
    Suraj Sharma (@suraj_sharma14) reported

    If I had to build 5 projects to get hired as an Agentic AI Engineer. I'd do this. Project 1: Compliance Sentinel Agent Scans new regulations daily. Auto-audits code. Generates audit-ready reports. Saves legal teams 40+ hours/week. Stack: LangGraph + Playwright + Legal RAG Project 2: Autonomous Code Reviewer 4 agents debate every PR: Security, Style, Tests, Architecture. Cuts review time by 70%. Stack: GitHub Actions + Tree-sitter + LLM-as-a-judge Project 3: Research-to-Deck Generator Reads 50+ papers. Synthesizes key points. Exports editable PPT with citations. Turns 3 days of work into 5 minutes. Stack: Semantic Scholar API + python-pptx + RAG Project 4: Recruiting Swarm Parses resumes. Scores fit. Drafts outreach. Books interviews. Increases interview show-up rates by 40%. Stack: NER models + Vector search + SendGrid + Calendar API Project 5: Cost-Aware Agent Router Token budgeting. Model routing by cost/latency. Early exit on confidence. Reduces inference costs by 60%. Stack: vLLM + Prometheus + Dynamic model switching Most people build chatbots. Builders build systems that solve expensive problems. (Bookmark & Repost)

  • AtlanteanGnosis
    Atlantean Gnosis ☀️ (@AtlanteanGnosis) reported

    @DionysianAgent When I made an account it said I made it back in 2024, though I don't think I did, is this a glitch or a GitHub thing?

  • ChasmsCom
    CHASMS.COM (@ChasmsCom) reported

    Microsoft is routing GitHub through AWS. AI agents pushed demand past what Azure could handle — 275M commits/week, nine May outages, enterprise SLAs broken. The world's biggest dev platform had to call its cloud rival for help. follow @chasmscom #AI #Cloud #Dev

  • _xjdr
    xjdr (@_xjdr) reported

    @tolly_xyz @xlr8harder Sorry about that. I'll take a look. Looking with GitHub or Gmail should work but track this down and fix it asap

  • ooluwatobig
    Oluwatobi O (@ooluwatobig) reported

    More trouble for GitHub as Cursor has launched Origin, a product which is essentially GitHub for AI agents

  • ayonzontop
    Tommy Ayonz (@ayonzontop) reported

    @gdb I used to paste errors on Google and find the best blog, GitHub issue or stack overflow article that resolves it, now I just chat with an AI model on my IDE without needing to open my browser

  • LandTanin
    Tanin (@LandTanin) reported

    Week 2 of trying @MulticaAI , random tips Been using it for basically 2 weeks now. Week 1 was a lot of trials and errors. It's a brilliant tool that integrates well with existing tools via CLI (for other tools to control it) and has the basic connection to things like GitHub. Random tips/gotchas I have learned from the past 2 weeks - Spawning a job/autopilot from a ticket has to be explicit. Agents somehow ignore instruction to spawn jobs. But if I tell it right in the comment, it'll do it (and apologise that it overlooked the agent instruction) - The ticket comment thread ain't the place you fix bugs. Every comment is a new ai agent session. And there's no plan mode. So most of the time after the agent finishes the ticket, if I need to fix something, I'll just pick it up in Codex or Claude Code

Check Current Status