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
Veigné, Centre 1
Paris, Île-de-France 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:

  • emilstridell
    stridell (@emilstridell) reported

    I have no respect for people who let their agents act freely on their behalf publicly. You ever read a github issue and think ”Man, not only could this guy not be bothered to write it himself (defensible), he couldn’t even review it to clean up the obvious slop”?

  • nikskld
    nik skld (@nikskld) reported

    ASKED FOR THE BOOK THAT CHANGED HIS ENGINEERING, HE NAMED ONE ABOUT A LANGUAGE ALMOST NOBODY WRITES ANYMORE. Functional Programming in Scala. The red Manning book. Scala sits at #27 on TIOBE with 0.67%. About 2.6% of developers touch it. This year’s Scala community survey drew 24% fewer responses than 2023. By every popularity metric, that’s a dead recommendation. Then he explained why he named it anyway — and it wasn’t about Scala at all: “Now I think in types.” Signature first. Implementation second. Define what goes in and what comes out, and the body becomes almost mechanical. That habit was a niche aesthetic in 2015. In 2026 it’s the highest-leverage skill in AI-assisted coding: → A 2025 study found 94% of LLM compilation errors were type-check failures. Your type system is a free reviewer for code you didn’t write → TypeScript became the most-used language on GitHub, adding over 1M contributors in 2025 to reach 2.6M. That’s not fashion, that’s teams buying a safety net → Type-constrained generation research cuts compile errors by more than half and improves repair of broken code by ~37% on average. Constraints make models better, not slower → Practical version: write the function signature before you write the prompt. Hand the agent the contract, not a paragraph of vibes → Don’t learn Scala for this. The book is a delivery vehicle for the concept. 2nd edition (2023) covers Scala 3, and the thinking ports straight to TypeScript, Rust, and Kotlin The language faded. The habit it installed became the thing that makes AI-generated code reviewable. Most people are prompting harder. The leverage is in defining the boundary before you prompt at all 👇

  • vibecodeceo
    Ethan Halfhide (@vibecodeceo) reported

    Here's the thing nobody's saying: the models are outpacing the workflows. Most people are still using AI like a fancy autocomplete while agents are quietly being handed the entire GitHub issue and told to go handle it.

  • DanielLockyer
    Daniel Lockyer (@DanielLockyer) reported

    @inouaxinxoinio GitHub Actions log file? What's the problem?

  • Gyome1_
    Gyomei (@Gyome1_) reported

    CLAUDE CODE SPENT WEEKS DESTROYING MY APP. ONE FREE GITHUB FILE FIXED THE REAL PROBLEM i was building an X post studio the app was supposed to collect relevant tweets, sort them by writing pattern, then turn one raw idea into a finished post Claude Code and Cursor were already open so i did what everyone does i dropped a three-page prompt into the chat and waited for the product to appear the first version looked promising then the sub-agents stopped working Claude patched them a new error appeared it fixed that too the generator finally produced a post, but the chat interface broke then the UI shifted then the typography collapsed after almost 100 hotfixes, the codebase looked like a house where every repaired pipe had cracked two more walls weeks disappeared the product was still half-built and the problem was not that Claude could not code the problem was that it started coding before it understood what it was building then i found one file buried inside the obra/superpowers repo: skills/brainstorming/SKILL.md the first rule was brutal: do not write code until the design has been presented and approved Claude now has to inspect the project, ask questions one at a time, propose multiple approaches, explain the trade-offs, write the design into a file, and wait for approval before touching the terminal even for one button even for one config change because “small” changes are where the model makes the assumptions that poison everything later that single skill changed Claude from a hyperactive junior developer into something much closer to a senior architect it stopped trying to impress me with fast code it started finding the decisions i had not made yet people spend $500 on prompting courses trying to make Claude write better the better move was teaching it when not to write the full Superpowers setup is below ↓

  • MWasifIqbal
    Wasif Iqbal (@MWasifIqbal) reported

    In roughly 90 days, every major AI coding tool outside GitHub Copilot changed hands or shut down - Microsoft, OpenAI, and now SpaceX each bought one. Cursor isn't the outlier here. It's the last domino.

  • scrygg
    Scry (@scrygg) reported

    HE TAUGHT CLAUDE TO REMEMBER WHY EVERY GITHUB REPO EXISTS Three months into collecting GitHub repos, one builder reopened the same folder and could not remember why half of it was there. The README explained each tool, but none of them explained his relationship to it 1 vault 2 folders 4 portfolio passes a new audit every 12 hours Then the first review exposed the real problem Some repos were duplicates. Others were marked in-use but appeared nowhere in his projects. A few dependencies had gone quiet upstream while his own code still relied on them So Claude was split into two jobs A cheap model reads every README, manifest, commit date and real project reference. Sonnet compares the entire collection, finds overlapping tools and decides what still earns the disk space The payoff only appears when the system reads across everything 30+ repos become one searchable memory Not just what every tool does but why he grabbed it whether he still uses it and what is quietly starting to rot

  • alexanderOpalic
    Alex (@alexanderOpalic) reported

    You need to have a workflow for one PR with different AI agents looking into your code. One is doing a review, and the other is implementing the fix in a loop before any human developer looks into your PR. Here I use @coderabbitai together with claude code and github actions code rabbit will find issues claude will fix them if they are valid or not

  • ImLunaHey
    luna (@ImLunaHey) reported

    @yrjdev github never had issues like this before they sacked the whole og github team.

  • YouPulseX
    Paul Sant · Telecodex (@YouPulseX) reported

    @trenchsheikh @github When GitHub Actions went down mid-project, what did it actually block, and would likely duration, upstream cause or a verified fallback have changed your next move?

  • markhuberco
    Mark Huber (@markhuberco) reported

    If you'd told me last year I'd have a GitHub account, I'd have asked you what that is. I'm drinking so much of the Claude Code kool-aid that I decided to give every client their own private GitHub repo. Each repo is mostly product marketing context right now. On one side, the inputs: positioning, ICP, customer interviews, competitive intel, the raw material I'm working from. On the other, what comes out of it: messaging frameworks, templates, sales battle cards, launch plans, the actual deliverables. So when I sit down to work, I'm not digging through Slack and Google Drive trying to remember where things are. It's all right there for me and Claude. Give it a year and I think "just send me the repo" is going to be a normal thing for companies to ask agencies, consultants, and freelancers.

  • charan77194
    Neelampalli Charan Balaji (@charan77194) reported

    @moraes_c_ Can @moraes_c_ u please help me to recover my github account.😢😓. I've been waiting for 20 days from the ticket raised. Can please solve my problem.

  • AlankritDotMe
    Alankrit Verma (@AlankritDotMe) reported

    Does GitHub use GitHub to build GitHub? Because now everything makes sense. Not trying to hate, but it is slowing us down. Are we still here because GitHub is good, or because moving is hard?

  • adityarya_ai
    Aditya Arya | Building AI Agent Teams (@adityarya_ai) reported

    Rule for any agent CLI: credentials stay with the trusted parent. Child gets the minimum files for the task — not your home directory. Ran Grok Build pre-fix? Rotate SSH keys + revoke GitHub keys today. What's your isolation rule before you let an agent touch a real repo?

  • ghagler
    Griff (@ghagler) reported

    @CaatzPG @jun_song This is a standing and unaddressed issue with several bug reports on the CODEX GitHub. Only way to fix is have codex or you remove the SQLite thread rollup db and allow it to respawn on reboot.

Check Current Status