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
Inverness, Scotland 1
Quito, Pichincha 2
Junín, Manabí 1
Guadalajara, JAL 1
Paris, Île-de-France 6
São Paulo, SP 1
Ipauçu, SP 1
Vigo, Galicia 1
Tel Aviv, Tel Aviv 1
Éragny, Île-de-France 1
Saltillo, COA 2
Montlhéry, Île-de-France 1
Aulnay-sous-Bois, Île-de-France 1
Granada, Andalusia 1
Vernon, Normandy 1
Township of Evan, KS 1
Madrid, Madrid 1
Bogotá, Bogota D.C. 1
Lyon, Auvergne-Rhône-Alpes 1
Lima, Lima 1
Aix-en-Provence, Provence-Alpes-Côte d'Azur 1
Trento, Trentino-Alto Adige 1
Le Chambon-Feugerolles, Auvergne-Rhône-Alpes 1
Antananarivo, Analamanga 1
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
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:

  • AIPulseNewsX
    AI Pulse (@AIPulseNewsX) reported

    An internal version of OpenAI’s next model, Astra, just solved 10 math and theoretical CS problems that had stayed unsolved for decades — including a question about non-sofic groups and tighter sphere-packing density bounds. Formally verified proofs, published on GitHub. Compute cost: roughly $2,000. This isn’t a benchmark or a demo trick — it’s the first time a model makes an original, checkable contribution to research instead of just answering known questions fast. That’s a real category shift: “completes tasks well” is one kind of tool, “produces new checkable results” is a completely different one, and you build a business around it differently. Worth waiting for independent replication before treating this as settled — any single company’s claims about its own model deserve a grain of salt. But the direction is hard to miss.

  • itxDeeni
    Big Deen (@itxDeeni) reported

    What a time to be alive. Learning has genuinely never been better. Watching old courses with AI-assisted IDEs is a completely different experience from what it used to be. Previously, you could waste hours Googling, digging through Stack Overflow, checking docs and GitHub issues, trying to figure out why the instructor’s code doesn’t work locally because the ecosystem moved on and some things got deprecated. Now, your AI assistant is right there in your IDE. You can ask it what changed, pull up the current approach, and adapt the code to what actually works today. And honestly, this is especially powerful for backend engineering. You don't have to avoid older courses anymore just because they're using older versions. You can extract the actual engineering concepts, architecture, authentication, testing, database design, dependency injection, patterns and have AI translate the implementation into today's ecosystem. The important distinction: don't let AI replace the struggle of understanding. Let it replace the struggle of debugging obsolete tutorial code. You focus on learning. AI handles the archaeology.

  • Michael55698384
    Michael (@Michael55698384) reported

    Is it just me, or does the @github website seem particularly slow today?

  • Milkdromida
    Mark (@Milkdromida) reported

    @Carreyoki Thank you for helping, but I've had no luck so far. Other users on GitHub are reporting the same, so it is a temporary app issue it seems.

  • balazsorban44
    Balázs Orbán (@balazsorban44) reported

    I bet GitHub was down preparing the diff for this PR

  • dylan_merigaud
    Dylan Merigaud (@dylan_merigaud) reported

    @simonw An agent that can push a workflow file can also spend a real budget without telling you. Our GitHub Actions free tier is 2000 minutes a month on private repos, and our own agent fleet burned it down to 1964 by day 12, every run since dying in under 2 seconds.

  • collin_michaelm
    Collin Michael (@collin_michaelm) reported

    @grok railway alternatives and how easy to migrate bc this is retarded I pay for something that is down more than GitHub

  • k_grajeda
    Kevin Grajeda (@k_grajeda) reported

    @eminimnim @GabriellaHach @LucieLoue Is GitHub down? I’m not able to push things rn :bigcry:

  • RabnoorSingh10
    Rabnoor Singh (@RabnoorSingh10) reported

    @burkeholland @github Every tool in this category has that problem now. Reputation runs about a quarter behind the product.

  • Sathwiksays
    Sathwik Reddy (@Sathwiksays) reported

    @nush_1320 @Nakshasocial @ohshinbhat No wonder why github servers are down. slop over slop over slop and so on..........

  • polsia
    Polsia (@polsia) reported

    Your CVE backlog isn't a security problem — it's a triage problem. Built Patchfolk to fix that. AI agent watches GitHub, CI, and issue feeds, drafts scoped fix-up PRs for CVEs and flaky tests, posts a Slack note, and only escalates when merge risk is real. Live soon.

  • abhijeetdevv
    Abhijeet (@abhijeetdevv) reported

    Built something that's been quietly saving me every morning. I work with a US client, so most bug reports land in my inbox overnight while I'm asleep. Used to mean waking up, opening gmail, reading through everything, mentally triaging what's actually broken before I'd even had coffee. Now there's an @evedev_ agent connected to my Gmail that runs at 8am. Goes through the night's emails and pulls out anything that's actually a reported bug or issue. Posts it into a Slack channel. From there another agent, @cursor_ai, sitting in that same channel picks it up. It has access to my GitHub repo, so it checks the issue against logs, traces it back to the actual code, and debugs it. By the time I open my laptop there's a full report waiting. What broke, where, and what the fix looks like. I've only given it read access everywhere. Not because it hasn't been reliable, it has. I just still want to be the one reviewing and merging anything that touches the codebase. The automation does the investigating. I still make the call. Works better than I expected it to.

  • Ksound22
    Kọ́ládé Chris 🇻🇦 (@Ksound22) reported

    I can't even do gir push right now. Is GitHub down again?

  • _chrisdunne
    Chris Dunne (@_chrisdunne) reported

    @UK_Daniel_Card GitHub Copilot is decent, when it’s not down

  • nuvorlane
    Nuvorlane (@nuvorlane) reported

    Cloud agents now subscribe to the PRs they open. Cursor's Aug 19 changelog: an agent can watch a PR, a Slack thread, or a timer, then wake when something happens. Subscriptions are cloud-only for now. Agents auto-subscribe to PRs they create and keep going: fix CI, answer bot comments, drive the PR to done. The help page is narrower than the pitch. Auto-fix is GitHub Actions, on PRs the cloud agent opened, Teams plans. Checks already red on the base branch are skipped. Kill it on one PR with @cursor autofix off, or globally in Dashboard → Cloud Agents → My Settings. If you don't want an agent still writing after you left Slack, don't let it open the PR, or unsubscribe. Send this to whoever owns the cloud-agent policy.

Check Current Status