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
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 2
Dortmund, NRW 1
Davenport, IA 1
St Helens, England 1
Nové Strašecí, Central Bohemia 1
West Lake Sammamish, WA 3
Parkersburg, WV 1
Perpignan, Occitanie 1
Piura, Piura 1
Tokyo, Tokyo 1
Brownsville, FL 1
New Delhi, NCT 1
Kannur, KL 1
Newark, NJ 1
Raszyn, Mazovia 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:

  • Blum_OG
    Blum (@Blum_OG) reported

    > used to spend mornings opening 5 tools in sequence > Slack first, then Gmail, then Notion > then realizing you missed something in Figma > then going back to Slack > not a focus problem > not a discipline problem > a structure problem > context was scattered by design > PMM work lives at the intersection of everything > product changing, stakeholders asking, launches moving > the small signals are the job > miss them early, fix them late > built 3 automations in Codex instead > 1 personal assistant scanning for action items every hour > 1 product tracker pulling from GitHub, Linear, Slack, Notion > 1 alignment doc generator pulling from meeting notes, threads, trackers > walked into PM syncs with a rough map already built > what changed, what is in progress, what has edge cases > 0 starting from zero > the engineer explains tradeoffs, not basics > wrote alignment docs in a fraction of the time > Codex pulled the raw material together > PMM added the judgment: what matters, what the message is, what is blocked > the job did not get smaller > it got closer to the parts that actually require a human

  • killua_9102
    キルア (@killua_9102) reported

    @neogoose_btw not sure what happened but its not happening now - I don't think I also got the logs for the incorrect run because the timestamps were for a later run. I'll post an issue on github if I see it happening again I guess.

  • 0xVeepul
    𝐕𝐑 (@0xVeepul) reported

    @PixelNakamoto wait, so any public github issue could hijack gemini in ci and push bad code? how did that slip through?

  • Avikzx
    Avik (@Avikzx) reported

    @Hi_Mrinal Actually I also feel that and I am building also you can see my GitHub account have in my X profile but I feel people face problem to find ideas because they try to earn money from every idea.

  • VaibhavSisinty
    Vaibhav Sisinty (@VaibhavSisinty) reported

    The big AI labs should be worried. 295 people on GitHub just shipped 588 PRs in one week. And the irony? Hermes runs on their tech. Anthropic, xAI, OpenAI, Google. Every major lab is powering the very tool that's outbuilding them. The community called this release Tenacity. The name is the flex. Here's what they have shipped: → A team of agents, not just one: Multi-agent Kanban with heartbeats, retries, zombie detection, and a hallucination gate. Spin up a board, drop tasks on it, let agents pick them up. The framework catches the ones that crash, the ones that lie, the ones that go silent. You're managing a team now, not running a single agent. → The agent stops losing the plot: The new /goal command locks Hermes onto a target and keeps it there across every turn, every restart, every interruption. Tell it once. It remembers the brief on message 14. The agent that doesn't drift. → Plug in any model. Swap providers without touching core: ProviderProfile makes every model source a clean plugin. OpenAI, Anthropic, xAI, Google, your own. Drop them in, swap them out. Build with whatever model wins this week, not the one you committed to last quarter. → Sessions that survive everything: Gateway crashes. Updates push. Source files reload. The conversation auto-resumes exactly where it left off. Checkpoints v2 rewrites state persistence with real pruning. Long-running builds stop dying because of a restart. → The agent reviews its own code before you do: Post-write delta lint. Self-linting on every write. Syntax errors surface immediately, not three commits later. Fewer broken builds. Less debugging downstream. → Eight critical security holes, closed in a single release: Redaction on by default. WhatsApp rejects strangers by default. Discord role-allowlists scoped to your guild. TOCTOU windows sealed shut across auth and MCP OAuth. Production-ready defaults out of the box. Big AI labs have thousands of engineers and billions in compute, and 295 people on GitHub are still outshipping all of them.

  • MnFounder
    Daniel (@MnFounder) reported

    GitHub MCP Server's secret scanning is now GA. Before your AI agent commits: it checks for leaked credentials. GA as of May 5. Requires GitHub Secret Protection on the repo. Catching credentials before they hit the history.

  • Isahbless79
    Kairo (@Isahbless79) reported

    Day 16 of building in Web3 from zero. I automated the pipeline and hit my first major infrastructure bottleneck. Here is today's technical breakdown: Pipeline Automation: I set up GitHub Actions to trigger the whale fetcher every 12 seconds. The Render API stays live, and the database now refreshes continuously in the background. Telegram Crash: I attempted to build a command menu for the bot (/set_filter, /start). It responded perfectly at first, but crashed the server after 30 minutes. The Root Cause: An asyncio event loop conflict between the Flask API and the telegram.ext library. The Fix: Decoupling the architecture. I am separating the Telegram bot into a standalone script, moving it to a different port, and shifting from polling to webhooks. Building through failures. Day 17 tomorrow.

  • joraweb3
    jordan kitty (@joraweb3) reported

    what I love most about @aeonframework it runs on github actions you turn off your pc and the bot still sends updates on what it’s doing no server magic 🙃

  • theeseus_ai
    Sam Paniagua (@theeseus_ai) reported

    99% of the job invites I get for crypto projects are complete scams. Same tired pattern every single time. They slide into my inbox with some “demo” or DeFi whatever, drop a GitHub link, and expect me to dive in. Opened the latest one today and my bullshit detector lit up instantly. I’d treat this repo as highly suspicious, straight-up likely malicious. No way I’m running npm install or npm start on a normal machine. package.json has postinstall set to “npm run start”. So yeah, the second you pull dependencies it fires up the Node server AND the React dev server. Classic supply-chain trap. npm security has been yelling about install-time scripts executing arbitrary code for years and these clowns are still pulling it. But the nasty part is buried in userController.js. It grabs some atob-decoded env vars for DEV_API_KEY, secret key, secret value, hits axios.get on that remote src with custom headers, then boom; new Function.constructor(‘require’, the_payload) and executes whatever it downloads with full access to Node’s require. All wrapped in an IIFE so it runs the second the module loads. Not even pretending to be a route handler. That’s not code. That’s a remote code loader backdoor. They committed the whole server/config/.config.env right in the repo with the base64 values pointing to some tan-decisive-tern IPFS link. README tells you to clone a totally different GitLab repo instead. Backend feels half fake; DB connect is commented out, auth cookie is but missing secure and sameSite, JWT just gets spat back in JSON. Weak as hell. This ain’t a demo. This is a trap. The whole chain — npm install → postinstall → start → import controller → fetch IPFS payload → exec with require — is too clean to be an accident. I’ve been full-stack shipping vision models since 2017 and deep in LLMs since 2022. Seen every hype cycle and every supply-chain garbage attempt. Only mess with **** like this in a disposable VM or container, no creds, no keys, network locked down. npm install --ignore-scripts first, then poke the payload separately if you’re feeling brave. Stay paranoid out there, devs. Anyone else drowning in these crypto repo traps daily? Drop your craziest red flag stories below… or DM me if you’ve got one you want a second pair of eyes on before it bites you.

  • AIRepoRadar
    AIRepoRadar (@AIRepoRadar) reported

    Hot take: The best open-source projects aren't the ones with the most GitHub stars. They're the ones where you read the README once and immediately know how to solve a problem you've been stuck on for hours. Docs > hype, always.

  • reviceva
    Elena Revicheva (@reviceva) reported

    🤖 AIdeazz now pulls fresh leads from Hacker News, GitHub, and Product Hunt straight into HubSpot twice weekly. AI classifies what problems they're solving, organizes everything automatically. Zero manual work, zero cost. #AI #BuildInPublic #AIFounder

  • DanielSMatthews
    𝑫𝒂𝒏𝒊𝒆𝒍 𝑺𝒄𝒐𝒕𝒕 𝑴𝒂𝒕𝒕𝒉𝒆𝒘𝒔 🇦🇺 (@DanielSMatthews) reported

    Google @antigravity is such a time saver. Hey can you check this FOSS code base off Github and make sure it is modernised and runs on Linux? DING! Sure here are the CLI binaries. But what about the GUI applications that sit on top of those? No, sorry but they are Windows only and use some pesky GUI toolkit that would be a PITA to port. Can you just do it all as HTML and use a web browser for the heavy lifting? DING! Here is your python based backend server just go here (URL) and have a play... (Well something like that, with a few guidance and bug stomping sessions.) So what does it do? It lets me use GnssLogger on an Android phone to grab an hour or two of low level GPS data from a fixed reference location then process it to get very high positional accuracy without differential GPS gear. Image shows some of the data from the original RTKLIB test files.

  • twaldin0
    tim waldin (@twaldin0) reported

    @ChShersh what happened when the meteor hit? did github go down

  • TheEduardoRFS
    EduardoRFS.tei (@TheEduardoRFS) reported

    @awelonblue @neirenoir The distribution in github is wide enough that I'm pretty sure you can write anything following it. I'm saying that you can just write software in specific styles and you can just make languages that assume that people will do so and if they don't that's not your problem.

  • coresourceai
    coresource.ai (@coresourceai) reported

    GitHub shipped Spec-Kit today. The thesis is settled: specs are the contract. Open question: which agent actually executes them? Horizon reads the spec from your Linear or Jira issue and ships stacked PRs, each citing the spec line behind it.

Check Current Status