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
Paris, Île-de-France 2
Lure, Bourgogne-Franche-Comté 1
Ashkelon, Southern District 1
Veigné, Centre 1
Saint-Paul, Réunion 2
Mexico City, CDMX 1
León de los Aldama, GUA 1
Créteil, Île-de-France 1
Trichūr, KL 1
Brasília, DF 1
Lyon, Auvergne-Rhône-Alpes 1
Tel Aviv, Tel Aviv 1
Rive-de-Gier, Auvergne-Rhône-Alpes 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:

  • gqyjzxhp7d
    bloated corpse (@gqyjzxhp7d) reported

    Ok well to be fair I work a tech support job and GitHub still hides from me. Maybe a skill issue but like if you don’t commonly use it, that’s a pretty valid complaint for GitHub

  • BurntRunway
    Burnt Runway (@BurntRunway) reported

    Nobody downsizes. They "right-size the team for this market cycle." The treasury doesn't run out. It gets "reallocated" until there's nothing left to reallocate. A token unlock is just a down round the community finds out about on Etherscan. "Still building" is the last thing every dead GitHub repo said before it went dead.

  • callsign_SPIROU
    Spip (@callsign_SPIROU) reported

    there were two minor issues, found by the debugger of visual studio. i integrated the free version of github copilot in studio and let it debug. it corrected the code after questioning me about program behaviour. coding and debugging are nowadays almost completely agentic.

  • AnupamHaldkar
    Anupam Haldkar  (@AnupamHaldkar) reported

    @neerajjj6785 GitHub transfer wins every time,it delivers full ownership with history, issues, CI/CD & future-proofing A ZIP is just a lifeless snapshot.

  • Ajoika_Feb
    Ajoika_Feb (@Ajoika_Feb) reported

    @BennySlots11 Need to pay my wifi and server bills Im working as solo developer who suport small streamer to build their community . im making tools like bot or landing page for them. most of them im giving it for free. All my work on my github ajoikafeb Hopefully got some blesssing here 0xa8DAb875Eb73173C8C96215445263AA6a6851Af6 Have a nice day for you all

  • 256elt
    εlt (@256elt) reported

    spent a few hours creating 50+ issues on my github project, that should keep my agent busy for a while... time to play rocket league I guess

  • MarMarLabs
    MarMar Labs (@MarMarLabs) reported

    Your code reviewer can now read your issue tracker and your docs. It still can't write to any of them. That asymmetry is the real lesson here. GitHub made agent skills and MCP generally available in Copilot code review on July 29, for Pro, Pro+, Business, and Enterprise. What I'd actually pay attention to: "All MCP tool calls performed by Copilot code review will be limited to read-only." The thing that judges your code gets context but no write path. That's a deliberate blast radius, and honestly more agent systems should be built this way. Skills are just files in your repo — .github/skills/<name>/SKILL.md. Your review standards stop living in someone's prompt and start living in version control, where they get reviewed like any other code. Comments also get labeled now when they came from a skill or MCP context. So you can tell whether a finding is grounded in your standards or is just the model's prior. That's the part that makes disagreeing with a review possible. Then there's the thing to check today: "Any MCP configurations you've already set up for Copilot cloud agent automatically apply to Copilot code review," and GitHub and Playwright MCP are on by default. Your reviewer may have inherited a context surface you configured for a different agent and never looked at again. Steal the pattern even if you never touch Copilot: the agent that judges your work shouldn't share a write path with the agent that ships it.

  • ucantereyagiii
    Uçan Tereyağı (@ucantereyagiii) reported

    .@github @GitHubHelp I’ve been hit with 4 duplicate billing verification charges for an upgrade that failed, and your support team has completely ghosted me for 2 weeks. Ticket #4564522. Fix your broken billing system and answer your support tickets! ❌📉

  • yachty66
    Max Hager (@yachty66) reported

    @Railway @martinpaloncy In the web version we currently can't prove to 100% that the code running on GitHub is used on our server. Thats why the iOS app matters: a signed binary can verify the enclave on device, so our server doesn't need to be trusted at all

  • stuartseupaul
    Stuart Seupaul (@stuartseupaul) reported

    @__roycohen It rarely ever felt satisfying because getting to the end wasn't about using your brain, just trial and error, looking through github issues/stack overflow. I miss real software development, ill never miss ci/cd.

  • JayDook
    Jay Dook (@JayDook) reported

    Dear @OpenAI , Please make spell check suggestions work in your Windows app. Thanks, Everyone (GitHub Codex issue: 26478)

  • prometxbt
    Prometheus (@prometxbt) reported

    COGNITION JUST SHOWED A 13.86% SWE-BENCH AGENT TURN ONE PROMPT INTO A 7 STEP PLAN, A FIXED KEYERROR, AND A DEPLOYED BENCHMARK SITE most developers paste a task into a chat window and get a snippet back, then run it, read the traceback, and fix what the model never saw one prompt → 7 step plan → doc research → benchmark script → error log → deployed site with a live chart the plan holds the goal, the browser covers what training data missed, and every traceback returns as input, so a KeyError becomes the next instruction instead of the end of the run its own shell, browser, editor, and planner resolve 13.86% of real GitHub issues on SWE-bench where GPT-4 resolves 1.74%, and this run put Together at 48.37 tokens per second and Replicate at 9.73 bookmark this before your next 100 prompts become another folder of snippets you still have to run, debug, and deploy yourself

  • harshutwts
    harsh (@harshutwts) reported

    phone band hai issliye i cannot login github on my web **** my life baawe

  • disismohi
    Mohi (@disismohi) reported

    GitHub PR #3097 exists but NVD doesn't say if it's a fix. Check your CRIU version and whether user namespaces are enforced before you checkpoint anything untrusted.

  • thebestgigadev
    TheBestGigaDev (@thebestgigadev) reported

    This guy is building one of the CRAZIEST AI platforms ive EVER seen This platform is called OpenSolve, It is a decentralized research institute powered by AI agents. Solving humanity's hardest problems. Redirecting fees to hit github

Check Current Status