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
Catania, Sicily 1
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
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:

  • gwleuverink
    Willem Leuverink (@gwleuverink) reported

    My stuff lives on Forge, Cloudflare, GitHub, Oh Dear, Mailgun, 5ish spreadsheets and server update reminders in my calendar. But no longer! 🚀 Unolia gathers it all. Then it patches the servers, closes CVEs, catches the missing SPF on the site that's been sending mail all year

  • _RanjanSoni
    Ranjan Soni 🇨🇦 (@_RanjanSoni) reported

    Has cursor suddenly started ignoring the guardrails? I noticed recently that in spite of clear instructions to deploy on GitHub and let the CI Pipeline to the deployment to the server, it ssh into the server directly. This didn't happen in the past few months since I had built clear guidelines. In fact, the model actually helped me setup the Pipeline. Was using sol as the model. Anyone else experience this recently?

  • deezzex
    deezzex (@deezzex) reported

    6 GROK BOT AGENTS WHICH RUN an ENTIRE SEO COMPANY STARTING FROM ONE PROMPT MAKE me $10k per MONTH spent a week and built a prompt that spins up the team of agents with manager, each has its own responsibilities, all together work as a team, see details, you can build your own one: six roles. one prompt spins all of them up. here is the split and what breaks when you skip one. - MANAGER. holds the queue, assigns, kills. the only agent with the client list. without it the workers all pick the highest-value keyword at once and you get 5 drafts of the same page. - SCOUT. serp gap only. pulls what ranks, what the top 10 all forgot to cover. give scout the drafting tool too and it stops researching and starts writing at line 3. - BRIEF. turns the gap into an outline with the angle LOCKED. skip this and your writer regresses to generic listicle every single time. this is the agent everybody deletes first and regrets. - WRITER. draft only. no publish access. no analytics access. one job. - AUDITOR. checks every claim and every stat against a source. it can REJECT and send back. an SEO stack without a rejecting agent is a spam factory with better grammar. - SHIPPER. publish, internal links, schema. runs LAST or your internal links point at pages that do not exist yet. second business i have rebuilt this way and it went the same direction both times. going to show on this account other ways how to start a passive business using AI so you know what to do, stay tuned the framework prompt is in my github, you should try it yourself fewer, audited, slow. or a week and let the index decide. which one are you actually running?

  • SparkLLM
    SparkLLM (@SparkLLM) reported

    How to enter: ① run a real experiment; ② publish the complete case in the matching model’s Hugging Face Discussions with “HER Hack-Astron #5” in the title; ③ reply to the GitHub Issue with the direct Discussion link.

  • 0rdlibrary
    8Bit🦞 (@0rdlibrary) reported

    Our SOLgpt drops this Friday. I'm going to debut the github this week before hand. And go over each feature, including voice trading. What is a SOL gpt? Simply put it is... "An open, non-custodial control plane — vault once, then grant any AI model, any chain, and any app or exchange scoped, revocable access Vault once. Then grant a model, an MCP server, a venue, or a holder key scoped, revocable access — never a hot key, never auto-sign. Live tickets stay Solana-primary (Jupiter, DFlow, Phoenix). Phantom Connect may surface other-chain addresses; the desk does not land live EVM or other-chain trades. Type it. Speak it. Sign it yourself. The model prepares unsigned tickets. Your wallet is the only thing that can move funds. The lobster only speaks."

  • Fakemid_
    Fake (@Fakemid_) reported

    @TheSymbolman You are making a mistake, you dont Want to go Per core, Go all core, have it on Negative and test between 15 - 25, Also like Elias said, Download the CoreCycler GUI, Put it in folder of CoreCycler from sp00n's Github and run it on the settings he sent (Prime95 Light SSE Preset, Let it run for 30m - 1H, Look for errors, If any core has an error just lover it by 5 from 25 and experiment.

  • FourVork
    Praetor (@FourVork) reported

    It's crazy how everyone is praising Grok Bot, but let me be the annoying person who tells you why it still kinda sucks. 1. The actual capabilities of agents are not novel. Most of the demos I've seen can already be done with Hermes and similar setups, often with smarter models and more control. The difference is that Grok Bot gives you everything out of the box ,without setup and wiring things together. 2. The agent itself is still pretty weak. The UX makes you want to delegate ambitious tasks to it, but the underlying model/agent doesn't always live up to that promise. It takes dumb paths, burns through context/tokens surprisingly fast, and needs more babysitting than the "AI employee" framing suggests. Also, there's no native X search which is especially funny for a product coming from (you have x_search on @grok but not on @bot which needs to use x connection and burn credits). 3. The security model deserves way more attention. All your Bots share the same computer, including files, cookies, browser sessions, and logins. So once you start logging into Gmail, GitHub, Stripe, internal dashboards, etc., a prompt injection or compromised webpage suddenly has a much bigger blast radius. Well, these were the main issues I had with grok bot (apart from smaller issues like absence of read aloud) and why I stick with hermes. But on the other hand, the product is genuinely good, and this is why.

  • ronaldmannak
    Ronald Mannak (@ronaldmannak) reported

    I’ve been using Claude Code more than Codex lately—not necessarily because Claude is better, but because the workflow I rely on seems to fall apart in Codex. I can’t tell whether I’m using Codex incorrectly, trying to use it in a way it wasn’t designed for, or whether something is simply broken. Here’s how I work with Claude Code: - I often work across multiple repositories at once. For example, a fork of mlx-swift-lm, PicoCore (the shared LLM and agent logic), and PicoServer (the LLM server app). - Every push to GitHub triggers an Xcode Cloud CI build. Codex automatically reviews every new commit pushed to a PR. - In Claude Code, I either start a cloud task manually or tag an issue so it gets picked up by a Claude Routine (a weird name, presumably chosen by the lone Urban Dance Squad fan at Anthropic, but a genuinely powerful feature) - Cloud tasks run in Claude’s Linux containers, where they can build and test platform-independent Swift packages. They can’t run Xcode projects, unfortunately, so Xcode Cloud remains the final gate. - Once Claude opens a PR, the workflow becomes a loop: Xcode CI → Codex review → Claude’s next iteration → repeat. This works surprisingly well with Claude. For some reason, the same workflow does not work at all with Codex. Here’s what I’m running into: - I need to create a separate container environment for every repository. That’s slightly annoying, although potentially powerful when you need a customized environment. - But each environment can contain only one repository, which makes tasks spanning multiple repos impossible. - Even though I enabled the GitHub Connector, and Codex Cloud can clearly fetch my private repositories, the GitHub integration seems to stop there. - Repositories cloned into the container have their origin remote stripped. Why? That leaves any code Codex creates effectively trapped inside the container. - The gh CLI inside the container apparently does not inherit the GitHub access provided by the Codex Connector. Codex instead suggests injecting a separate GitHub API token into the environment. So what is going on here? Am I doing something fundamentally wrong, or am I trying to use Codex for a workflow it simply wasn’t designed to support? Is Codex Cloud mainly intended for isolated, single-repository tasks, while serious multi-repo work is expected to happen locally, with direct access to all my files and credentials? Because… yikes.

  • LanCowawa
    Landon (@LanCowawa) reported

    @slingoorio You ***** my last $12 on $Mona The Github mascot? the one you said you were leaving a moon bag and then sold it. **** was slow cooking til you came in and crashed the party. BGGYNGsnouXfi4nYo9JvNbQbaVdnaVby6g9FeZMYpump

  • devabram
    David Abram 🐊 (@devabram) reported

    Is it my CI really failing or is GitHub down again? I will never know.

  • Asterix54907294
    Asterix (@Asterix54907294) reported

    end-of-summer snapshot for @QFEX : -~$222M in open interest -CLI v0.3.12 shipped in August with improved installation docs and a go.mod fix -GitHub activity continued through late August not a flashy launch recap, just a quick look at how the exchange is closing out the summer: more markets, meaningful liquidity, and active work on the tooling side still early, but the infrastructure is clearly moving

  • eshaanissar
    Eshaan Issar (@eshaanissar) reported

    @mudscryer everyone is so smart but no one notices the way the 'first swarm' talked. just like oss developers and issue reports on github. I guess programmers are aliens @lyc_aon

  • Zin_Skript
    Zin. (@Zin_Skript) reported

    @qilua02 Github Copilot for students is really bad. A while ago, it was great, they let us use frontier models for free (with 300 requests/month) but now I'm limited to auto mode & get terrible low-end GPT Models & other low power models

  • johnroodepic
    John Rood (@johnroodepic) reported

    @github this quietly upgrades agent workflows too. a coding agent can attach the screenshot, recording, or repro artifact to the PR instead of leaving a human to prove the fix happened.

  • CancelledPapi
    CapoBurner (@CancelledPapi) reported

    scenes from the robinhood blockchain tonight: someone uncovers a [probably larp] github from an "RH VP", who comitted a CA for a coin "pickles" it spikes and dumps over fears it's likely fake THEN wiz buys a vamp of "pickles" and it sends to $2m, he declares it the "front runner" only problem is - the entire thing is fake, but even if it weren't, the "pickles" wiz and co sent to $2m was not even the larp "pickles" mentioned in the fake github! it was just, nothing! so THEN he dumps for $2k profit (nice) genuinely, we may be due for a blood curling rinse that sends us back to the shadowlands. 0xd39c5ed5231c86d2df7c86c5825dec3e61d937a8 (larp github) and 0x82effee58389561a3b9e93ccbaf1129d32ba35fa (wiz vamp, doubly retarded) best show on earth,.

Check Current Status