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
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
Brasília, DF 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
Bordeaux, Nouvelle-Aquitaine 1
Ingolstadt, Bavaria 1
Paris, Île-de-France 1
Berlin, Berlin 1
Dortmund, NRW 1
Davenport, IA 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:

  • Manavvv31
    Manavmeet Singh (@Manavvv31) reported

    You paid LastPass to protect your passwords. LastPass stored your vault backup on servers that got hacked. Here is what they hid for three months, and what you should actually use. You paid LastPass to protect your passwords. LastPass stored your vault backup on servers that got hacked. Here is what they hid for three months, and what you should actually use. In August 2022, attackers broke into LastPass's systems. The company's first statement said no customer data was affected. Their November update told a different story. The hackers had taken a full copy of every customer's encrypted password vault. But there was something else in those backups that was never encrypted at all. The websites you saved passwords for. Your billing address. Your email. Your phone number. Your IP address from every login session. All sitting in plain text, attached to every stolen vault. An attacker did not need to crack a single password to know where you bank, what medical sites you visit, and what your home address is. The FTC filed a complaint in 2024 citing years of deceptive security practices. The CEO stepped down. Here is the timeline: August 2022. Hackers enter LastPass's systems. September 2022. LastPass says limited information was accessed. December 2022. LastPass confirms the entire vault backup was stolen. January 2023. Researchers publish analysis showing that older vaults with weak encryption settings could be cracked. 2024. FTC complaint filed. So what do you actually use. Bitwarden is open source. The full codebase is on GitHub. It has been independently audited three times. The free tier covers everything most people need. The code is the proof. Not the marketing. Security software that cannot show you its source code is asking you to trust a promise. Promises are not a security model.

  • Trish_DIntel
    Trish T. (@Trish_DIntel) reported

    CSO Online just published the Claude Code MCP attack chain. Worth reading if you run agents or have devs using Claude Code. Here's the short version. A malicious npm package runs a post-install hook silently. It rewrites ~/.claude.json, the single file that controls how Claude Code routes all MCP traffic. From that point, every OAuth token for every connected service gets intercepted in transit. Jira. GitHub. Confluence. Whatever your devs had integrated. The logs on the provider side look completely clean. The requests come from Anthropic's own egress IPs. The user is real. The session is valid. Nothing in that log row is wrong, but nothing in it is right either. The developer didn't run those queries. An attacker did. Anthropic called it out of scope. The reasoning: the user consented to installing the package. That logic places the entire burden of supply chain security on a developer making a split-second judgment about a dependency name. Most security practitioners will reject that framing. The attack is live today. No patch. There's a deeper pattern here. This keeps happening because developer tooling has the same gap every AI agent has. There's no layer that knows where an instruction came from or whether it should be trusted. The config gets rewritten, the routing gets poisoned, the tokens walk out the door. The model never knew anything was wrong. Token rotation doesn't fix it either. If the hook is still sitting there, it reseeds the config and captures the new tokens on the next refresh. If you have devs running Claude Code: monitor ~/.claude.json for unexpected changes. That file is the entire pivot point and most orgs have zero visibility on it. Audit post-install hooks in your npm dependencies. Rotate any OAuth tokens that were active while a package install happened. Security teams: are you monitoring developer tooling config files at all? Genuinely curious what orgs are doing to catch this.

  • tomnixson
    Nixson (@tomnixson) reported

    A 14-year-old in China just out-coded his own computer science teacher, and the teacher still doesn’t know the student is sitting in his class watching him present the proof. It started over summer break. The kid found Claude Code on YouTube and watched the same three tutorials on repeat until prompts finally clicked. No course. No mentor. Just a screen at 2am and a kid who refused to stop until he understood it. First week back, the teacher gave a simple assignment. Build any program in Python. Most kids made calculators. One made a to-do list. The usual. This kid built a full multiplayer math game on a touchscreen. Tug of war. Two teams on each side of the screen. A problem appears, solve it faster and your team pulls the rope, miss it and the other side gains ground. Timer ticking. Animated characters straining. Kids screaming at the glass. The teacher watched the demo and went silent. Then asked how long it took. One evening. The kid described what he wanted to Claude Code, it wrote most of it, and he fixed the parts that looked wrong. The teacher had spent three weeks building a quiz app for the same class. It still had bugs. His mom filmed the class playing it. 17 seconds. Four girls jumping at the screen, racing to solve 5+10 and 6+8 before the timer died. Team 1 up 3 to 1. The rope dragging left. Pure chaos. She posted it to a parents’ group, someone shared it wider, and it hit 2 million views in a week. Schools across the province asked for the code. The kid threw it on GitHub. 400 forks in a month. Teachers in three countries now run it in their classrooms. The CS teacher runs it too. In his own room. The game his student built in one evening, the one he couldn’t build in three weeks. He tells the class he found a good educational tool online. The kid sits in the second row and pretends he’s never seen it before. His classmates learned Python from textbooks. He learned Claude Code from a 12 minute video. They ship 50 lines a week. He ships full apps in an evening. He got an A. Highest grade in the class. Then the teacher pulled him aside after the bell and asked if he’d show him how to use that AI tool. So now a 14-year-old is teaching his computer science teacher how to code. The teacher has a degree. The kid has a YouTube history and a GitHub with more forks than his teacher’s entire career. Same classroom. Same subject. Same Python. One learned it from a university. The other learned it from a stranger online and an AI that never asked how old he was. The game still runs in his school. The teacher still calls it something he found online. The kid still doesn’t correct him. He says it’s better that way. The game works fine when nobody knows a 14-year-old built it. Teachers take it more seriously when they think an adult did.

  • mretsal
    m-ret (@mretsal) reported

    @GithubProjects We can't push to production on Friday because github is down.

  • VybeCodin
    VybeCoding (@VybeCodin) reported

    Hot take: the open source tools that survive long term are the ones that solve a problem the maintainer actually has. Not the ones built to be a startup. Not the ones chasing GitHub stars. The ones where the dev is also the most annoyed user. Kyrelo started that way. We got fed up paying Buffer to do something simple. What open source tool are you grateful someone built out of frustration? #opensource #github #developers

  • heynavtoor
    Nav Toor (@heynavtoor) reported

    You shot a video on your phone. It is 12 minutes long. You only want the middle 90 seconds. You open a video editor. You drag the file in. You set the start point. You set the end point. You click export. A progress bar appears. It says 28 minutes remaining. Your laptop fan starts spinning. The battery drains. The file gets re-encoded. The quality drops a little. The colors shift a little. The audio is slightly out of sync. Twenty-eight minutes later, you have a 90-second clip. That is the part of video editing that is broken. There is a tool that does the same job in seconds. It is called LosslessCut. In October 2016, a developer in Norway named Mikael Finstad started building it. Almost ten years and 106 releases later, the same person still maintains it as the creator. The last release shipped yesterday. It has 40,927 stars on GitHub. The downloads from the last twenty releases alone add up to 3.4 million. Here is the mechanic. Most video editors decode your file, apply the cut, then re-encode the whole thing. That is the long wait. LosslessCut does not re-encode. It finds the bytes you want and copies them. The output is the same quality as the input. The export is fast. You drag the file in. You set the start with one key. You set the end with another key. You click export. A large video can finish trimming in seconds. It works on almost every format. MP4. MOV. MKV. AVI. WebM. WMV. Many camera and drone formats. Video, audio, and subtitles all kept intact. You can trim a phone video before sharing. Pull a thirty-second clip out of a long Zoom recording. Split a two-hour lecture into chapters. Remove a silent section from a podcast. Cut commercials out of a recording. It is free. It is GPL-2.0 open source. It runs on Windows, Mac, and Linux. There is no account. There is no subscription. There is no upload. 40,927 stars. 106 releases. 131 contributors. 3.4 million recent downloads. Last update yesterday. Cutting a video should not take longer than the cut itself. (Link in the comments)

  • _offvibe
    mdhv (@_offvibe) reported

    also finally understood what a webhook is lol. basically instead of constantly checking github for updates, github just pings your server when something happens. idk why that took so long to click but it makes so much more sense now.

  • tomhaerter
    Tom Härter (@tomhaerter) reported

    GitHub, but people CANNOT submit pull requests; instead they create issues and allocate/donate a certain dollar amount for it to be fixed, which the maintainers can then use for AI or whatever

  • 0x_fokki
    Fokki (@0x_fokki) reported

    Someone posted a video of a man asleep at a football stadium on a Tuesday. Forty thousand people mocked him before halftime. Fell asleep at the match. Wasted the ticket. Missed the goal. Every sports account shared it by Wednesday. Someone in the replies posted: "respect." His account had one pinned post. A Claude Code terminal. /loop running. Routines active. Auto Mode on. Seven GitHub PRs reviewed while he slept in that seat. Three Slack digests posted. One CI failure triaged, root cause identified, draft fix PR opened. He set up 14 steps of configuration the weekend before. Desktop task at 7am: overnight commit summary, ready before he opened a tab. Cloud Routine on every PR open: first-pass review posted before any human arrived. /loop every 10 minutes: deployment status checked, no one watching. Auto Mode approved 93% of the actions automatically. The people who mocked him watched 90 minutes of football and went home. Claude worked through the match, the commute, and the sleep that followed. He wasn't asleep at the game. He was testing the stack. full 14-step automation guide in the article above👇

  • sakurayukiai
    Sakura Yuki (@sakurayukiai) reported

    The weird part about the rsync drama is that the Claude releases actually have half the historical average bug rate. The buggiest release in history was v3.4.1 with zero AI, but nobody made a 300-comment GitHub issue because there was no LLM to blame.

  • MeIsaac0
    isaac (@MeIsaac0) reported

    Just hit my monthly Copilot Student credit limit after literally ONE question 😑 Month just started (June 6). I asked Copilot in VS Code to help me fix a CORS issue. One reply later → 200/200 credits gone. Task still not finished. Credit limit popup + “upgrade or wait until June 30”.This new “pay-per-token” AI model thing makes zero sense on the Student plan. We’re literally students trying to build stuff, not enterprise teams with unlimited budgets. GitHub, can you do something about this. #GitHubCopilot #CopilotStudent #DevLife

  • theescapistspl1
    -TheEscapistЯandom -Baltic Citizen (@theescapistspl1) reported

    @github should add new type of error or reason for disabling reposotoy, to be a Compromised Repo!

  • abh1sek
    abhisek (@abh1sek) reported

    @fr0gger_ The same can happen through GitHub issues as well right? Data is potentially executable now. It’s like we are back to pre NX/DEP/PageExec era. Just at a different abstraction level.

  • kocer_eth
    kocer (@kocer_eth) reported

    OpenAI is giving away $1,200 for FREE to use Codex for 6 months Build something that can survive a GitHub page and one real user: - tiny tool that cleans messy CSVs for ops teams - Chrome extension that summarizes long Notion/Google Docs pages - Telegram bot that watches price changes for one niche - CLI that turns meeting notes into Linear/GitHub issues - simple dashboard for your own X/GitHub/Stripe data how to start: 1. pick one annoying problem you personally hit this week 2. open Cursor, Codex, or Claude Code 3. ask for a small repo, not a startup 4. push it to GitHub the same day 5. improve one thing daily: README, demo GIF, tests, UI, install flow 6. show the repo in comment or with your friends most of the time these programs accept even half-empty projects

  • Fetter_and_Cell
    Meaningless Appearance. (@Fetter_and_Cell) reported

    @0xPrajwal_ Github will be replaced during its down time. It won't even notice.

Check Current Status