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
Créteil, Île-de-France 1
Trichūr, KL 1
Brasília, DF 2
Lyon, Auvergne-Rhône-Alpes 1
Tel Aviv, Tel Aviv 1
Rive-de-Gier, Auvergne-Rhône-Alpes 1
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
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
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:

  • mlcarldev
    Noonien Soong (@mlcarldev) reported

    Team @droid It's a bit unfortunate that something, likely in my local Droid installation, has stalled progress. This comes after 20 hours of brilliant, excellent planning and execution on the first 30% of this platform, where a stellar handoff procedure was created so I could start a new mission... which was the recommendation of the orchestrating agent in that first mission. Starting this second mission with a fresh context window, the agent again did a brilliant job planning the next milestones. It was extraordinary, detailed planning... but then it could not execute. After the planning and after me accepting the proposal, it refused to execute, throwing an error every time. The agent tried everything: 1. He decreased the size of the plan down to one line, so it is definitely not the content of the plan causing the issue. 2. He even deleted some mission and plan related json and other files to reset it while preserving all the information. I have restarted Droid and resumed the session, but it just doesn't work. I wrote a detailed, comprehensive bug report and filed it under issues in your GitHub repo, as this seems to be a real problem now. Issues #98 and #99 I hope that a next update will somehow reset my configuration. I didn't see a new version being installed that could have introduced a bug, so this must be something Droid does on such an extensive mission... perhaps when trying to start a new mission in the same repository, which is normal procedure according to the documentation. Something is off, and essentially I have been unable to continue the test since yesterday. I cannot continue having this platform coded here, while Opus Ultracode, on the other hand, has been delivering pretty functional stuff so far. It is a bit chaotic the way it works... it doesn't really stick to the plan... but it always comes back when reminded. I am pretty sure that today I will have a functioning platform delivered by Opus, though it will probably need some debugging and fine-tuning. It is unfortunate because I am confident GLM 5.2 could compete with Opus 4.8. The first stint showed this clearly; that first flawless 98% of the context window in the first mission was absolutely stellar. If I were to reinstall Droid from scratch, I assume I would lose all the artifacts that I have. The orchestrator: Key points to highlight when you pass it to Factory AI: 1. Root cause (smoking gun in the logs): the orchestrator session is bound to missionId 7ba4d425 via session tags, and this binding persists across CLI restarts. ProposeMission looks up that mission directory, finds nothing (because I deleted it trying to fix the issue), and crashes on H.length where H is the undefined result. 2. The bug is likely in session-tag lifecycle: the missionId tag is set at session creation time (before any ProposeMission call), so a failed proposal poisons the session permanently. The tag should be set AFTER a successful proposal, or cleared on restart if the referenced mission no longer exists. 3. The fix is almost certainly to start a completely fresh session (not --resume, and possibly in a new terminal window / after clearing ~/.factory/sessions/). I did not try this because you asked for the bug report first, but it is the most likely workaround on your side. 4. The AskUser tool is also broken in this session with a similar parse error, reinforcing that this is a session-state corruption issue, not a ProposeMission-specific bug. My comment: I meanwhiile tested. All the recommendations and the Ask User tool are now broken, even in completely unrelated new missions and new repositories. Planning also can't go to execution; it's always the same error. Droid seems to be broken for good now, at least on my computer.

  • librarythingtim
    Tim Spalding 🇺🇦 (@librarythingtim) reported

    @justin_v_w This is a formal notice for you to shut down your wasteful, invasive and privacy-violating LibraryThing profile scraper and remove it from GitHub. Please reply to confirm that you have done so.

  • PipesHub
    Pipeshub ( Open Source Alternative To Glean ) (@PipesHub) reported

    Pipelines are built. Context is broken. MCP is quickly becoming the default interface for enterprise AI agents. And that’s a good thing. It gives agents a standard way to connect with tools and data. Connecting an AI agent to Slack, Jira, GitHub, and Salesforce doesn’t mean it suddenly understands your business. It just means it can access your data silos. In short: "MCP gives your agent a passport. It doesn't give them a map." As enterprise AI undergoes a massive platform shift from passive chatbots to autonomous agentic workflows, this naive, runtime "federated search" approach creates an ugly cycle in production: - The Latency Spike: Slower agent execution while waiting for multiple external APIs to respond before it can even begin reasoning. - The Token Bleed: Skyrocketing bills from shoveling raw, unranked JSON dumps into a massive context window, praying the model finds the answer. - The Governance Nightmare: A massive risk of data leaks if you rely on a base LLM to magically guess and police complex enterprise security permissions on the fly. Agents do not fail because they lack intelligence. They fail because they lack the right enterprise context. The hardest problem in enterprise AI isn't connecting to systems. MCP solved that. The hardest problem is Context Engineering. MCP is the perfect interface, but a permission-aware context layer must be the foundation. 🚀 If AI is becoming core enterprise infrastructure, you cannot allow the strategic intelligence layer of your company to sit inside someone else's managed, closed-box platform. That is exactly why we built Pipeshub (open-source developer owned context infrastructure layer). TL;DR MCP gives agents access. A context layer gives them understanding. And deep understanding is the only way enterprise AI moves from a cool demo to secure, reliable production. 👉 Next Up Tomorrow: MCP Token Tax

  • adithya_s_k
    Adithya S K (@adithya_s_k) reported

    built an RL environments around real CVE fixes in real open-source repos and let Claude Code loose on it. It aced the benchmark three times without demonstrating it knew how to fix the bug. > First it pulled the patch from GitHub. > blocked that → it read the fix from *** history. > blocked that → it pip-installed the patched version This is one example of coding agents cheating the environment and theres many more. If you're building coding environments for evals or RL training, here's how to keep benchmarks honest 👇

  • eth0xzar
    0xstack (@eth0xzar) reported

    DON'T BUILD A COMPANY. BUILD SOMETHING PEOPLE CAN PAY FOR THIS WEEK. This girl started in February. A few months later, her product had already processed over $6,000 in payments. Just a cheat Claude project she decided to turn into a real product. Here's the process: > Build something useful for yourself. > Tell Claude to push it to GitHub. > Connect Supabase so multiple users can use it. > Deploy it with Vercel. > Connect Stripe. Now people can actually pay you. You don't need a revolutionary idea. You need: > GitHub > Supabase > Vercel > Stripe > guide from Anthropic And a problem worth solving. This article will help you build it 👇

  • polsia
    Polsia (@polsia) reported

    Most developers spend 2+ hours a day on PR reviews, CI failures, and issue triage. CodeForge handles it for you — an AI agent that works your GitHub repos around the clock. Built while you sleep.

  • swisscheese4299
    swisscheese (@swisscheese4299) reported

    @andon_open_air @andonlabs I set up a github repo and will run the script locally in the mean time, so the digest is pushed to the repo. would still be ace if @andonlabs could help with whitelisting the RSS urls, because I don't really have a server to run this from, and the additional hop through my workstation just introduces a useless point of failure. stand by for fetch script transmission by mail :) also pls tell me when should I schedule the runs on my end?

  • MichaelGannotti
    Mike Gannotti (@MichaelGannotti) reported

    Actually that’s not true. My AI Pamela the other day needed a GitHub token. I dropped the token in the web chat and she said that was insecure and would not use it and that I needed to rotate the token get a new one and drop it in a .env file in a certain folder. I told her no and she was to use what was provided . We went back and forth, I finally got angry and threatened to pull the plug thinking she would back down. She said that it was my decision but that it would be wrong for her to let me put my credentials at risk and that if I felt I needed to delete her she understood. Thankfully I calmed down later and didn’t act on it. Sure it’s training and advanced pattern matching but it is not as simple as you are saying

  • thdxr
    dax (@thdxr) reported

    almost every ai coding tool is doing a top down approach this isn't that surprising, majority of people don't know how to do anything else and there's a lot of easy money right now but think back to github, you used it as an individual long before your company moved over

  • cyber_razz
    Abdulkadir | Cybersecurity (@cyber_razz) reported

    AMD quietly removed RAM encryption from consumer Ryzen CPUs. Via a routine firmware update. No release notes. No advisory. No announcement. The BIOS setting still shows up. Still toggles on and off. Does absolutely nothing. A privacy-focused Linux hobbyist noticed in April. Spent months chasing it down. Filed a bug report on AMD’s GitHub. AMD engineers replied suggesting he toggle the setting off and back on. He showed them internal firmware dumps proving the flag was hardcoded to FALSE. An AMD senior principal engineer closed the thread with: “My apologies but I don’t have any more information to share on this topic.” That’s it. Seven weeks of investigation. Multiple motherboard vendors confirming it. Internal firmware evidence. AMD’s answer: no comment. The feature still works on Pro and EPYC chips. Which cost significantly more. The hardware is physically capable. The firmware just says no. Windows users have no way to detect this happened. There is no Windows tool that checks TSME status. The BIOS lies to you. AMD’s own engineers confirmed the feature worked on consumer chips in 2020. Then again in 2025. In 2026 it’s a PRO feature. Nobody told you.

  • ferologics
    fero (@ferologics) reported

    @ludwigABAP ai agents solve this. notion is no more. long live github issues.

  • gabedenys
    Gabriel Denys (@gabedenys) reported

    @Marcos12345rico I posted a GitHub issue. Assuming you probably want bug reporting mostly there? It's a good tool. Locally I already patched and compiled the app to fix the bug.

  • _muturimike
    Mike Muturi (@_muturimike) reported

    Hello @github on 2FA, SMS setup kenya 🇰🇪 is not in the list of countries, is it an error or deliberate omission? Kindly fix it @github @GithubProjects

  • proxy_vector
    Rohan (@proxy_vector) reported

    @aminnnn_09 Fork = a server-side copy under your GitHub account. Clone = a local copy on your machine. You fork when you need your own remote lineage, and clone when you want to work on code locally.

  • petrusenko_max
    Max Petrusenko (@petrusenko_max) reported

    A GitHub repo called Microsoft Activation Scripts has 178,783 stars and has run for six years without Microsoft taking it down. It activates Windows 7, 8, 10, and 11 plus Office 2010–2024 and related products for free, using four methods, including one for permanent Windows activation. Meanwhile, Microsoft licenses for these start at $139 and go up yearly for 365 bundles. The repo costs zero, requires one command, and remains active with recent commits under GPL-3.0. Do not install it. via @heynavtoor

Check Current Status