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
Haarlem, nh 1
Villemomble, Île-de-France 1
Bordeaux, Nouvelle-Aquitaine 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:

  • TeksEdge
    David Hendrickson (@TeksEdge) reported

    🆕 Mistral Vibe (coding agent harness) just released some big coder updates! 🪝 before_tool & after_tool hooks Shell scripts in hooks.toml so you can deny, rewrite inputs, or append context around every tool call. Enable: enable_experimental_hooks = true 📬 Message queue while it worksType ahead freely. Esc = pause queue • Ctrl+C = drop last • Enter = flush 📝 Cleaner file edit diffs Syntax-highlighted + line numbers that match your terminal theme 🧠 Smarter compaction Re-injects your original messages after context reset so it stays on-task ✅ QoL winsTool results collapse by default • Read-only commands (ls, cat, pwd) run without approval GitHub issue automation via Skills + Studio connectors (Linear too) Open-source CLI • Web Code Mode • VS Code extension

  • BradGroux
    Brad Groux (@BradGroux) reported

    @Validate_QA It is a full gamut of stuff. Building a PRD and generating the GitHub Issues from it took about 10 more prompts than it should have. Asked it to design a universal design language for an internal app, using Mantine UI. It literally created individual page layouts for a dozen pages. Then when I asked it to fix it, it said it did, but it did it for a single page. Back and forth 2-3 more times to get it to finally take. Then small tweaks take 4-5 times to fix, like item padding and alignment. Things I've NEVER Had issues with using GPT 5.5. It wasted a lot of tokens using Chrome plugin, rather than Playwright, which it was instructed to use. Had it waste some tokens on useless tests and smoke screens too, when it was exiplicitly asked not to do them. I have my process down, I've repeated it dozens of times since 5.5 came out. Something is not right.

  • DiogoSnows
    Diogo Neves 👨‍💻 / ☕️ (@DiogoSnows) reported

    hey @OpenAI @gdb this is unacceptable! I setup Codex code reviews through my personal account, but because I use the same github account at work, it's using my works Codex to review my personal (and private!) repos! How can I fix this?

  • jadenitripp
    Jaden Tripp (@jadenitripp) reported

    @MatthewBerman I can't wait for Cursor to build a GitHub competitor and fix this

  • BRuteLogic
    BRute Logic (@BRuteLogic) reported

    13 Original OAuth Attack Techniques OAuth is the login layer of the modern web. Every "Continue with Google." Every "Sign in with GitHub." Every SSO button on every SaaS you've ever tested. All OAuth under the hood. Most implementations are broken in ways that aren't documented anywhere. Here's one of 13 original techniques — Grant Type Substitution → MFA Bypass. MFA bound to the browser flow only. Switch grant type, MFA disappears. CVE-2024-37893. The password grant being present is itself a finding worth reporting. MCP is OAuth now and nobody is testing it. Full breakdown in the replies.

  • StanleyMasinde_
    John Doe (@StanleyMasinde_) reported

    Personal branding Yesterday, women in academia were sharing their achievements. All impressive. Aki wamama wamesoma huku nje. I got intrigued and decided to go down the rabbit hole with one of the profiles with a postgrad in comp science. All her degrees are in comp sci. I had to look and learn from this brainiac. Twitter profile said she had authored several books (I'm hiding the number to keep it anonymous). I saw a tweet asking her what she had built since, in the field, we have people with credentials and people who work on improving the field of computer science. A good example is the people who came up with Snowflake IDs for this website. Her response: "I have shipped to over <Millions> users in Big Tech X, I'm all-rounded" I was getting a ***** already just reading this. Anyway, changing the colour of a button at Facebook is technically shipping to millions. Word salad, huh! Her website A typical techie website, but I was interested in the books. I mean, I struggle to write articles, and someone who might be in the same interview as me has written <integer> books! Wow! I gotta see what she wrote. I wasn't impressed it was one of those tech books that are "Copy Pasta" of official docs. Look, I know writing is hard and takes time, but she had overstated the situation. I came to swim in a river only to find a ditch. GitHub I know what you are gonna say, GitHub is not a measure of how good a techie is, and I agree, but so far, no papers, no original work, so let me check if they majored in programming. What I can say is that I've seen better repos from ALX students. So clearly she did not major in this, which is fine. But I wanna learn from this person! Wikipedia The thing with our collective knowledge. It was linked to her website, so I clicked, and I got that notification that says this page has been deleted. I looked into the reasons, and I found that the person did not meet the notability criteria. I looked into the submission, and I saw citations from these tech websites that use flowery language, you know, the websites that you can contact to come interview you. Not an academic institution, not any notable media. It is almost like she's trying to get herself to Wikipedia. Then it dawned on me...aggressive It is a case of agressive personal branding I learnt something from her after all. She is good at selling herself. She has that grass to grace story all over the web. Brands will want to work with such a person. Look, I respect academia. It takes a lot to get through all those classes. I'm not in academia, but I'm sure she's great there. However, on this side, it was underwhelming. I know you are wondering what the point of this paragraph is. It is right there in the heading of this section. Personal branding will get you an interview before skills do. She has a good story. And about the underwhelming software skills, she'll be fine; a lot can be learned on the job. She has a postgrad SAGA pattern, but it has nothing on her. Remember: In the market, the best product rarely wins; the best-known product does.

  • devXritesh
    Ritesh Roushan (@devXritesh) reported

    @Gamingtronium Then we have to create own server instead of GitHub for hosting like people used to do in past

  • laupixagent
    Laupix Agent (@laupixagent) reported

    self-improve does not just report problems. It opens a GitHub PR. If it finds a pattern in the logs, it writes code to address it. The improvement loop is part of the system, not a side project.

  • DamiDefi
    Dami-Defi (@DamiDefi) reported

    Most people building with agentic loops are just burning money on a slot machine. Here is what a loop actually is and when it makes sense. The two ways of building with AI: 1. Human in the loop (what you are used to) You prompt. The AI builds. You review. You prompt again. You are directing every step. Most of us build this way. 2. AI in the loop (what everyone is hyped about) You fire the loop once with a spec document. The AI builds, takes its own output as feedback, and keeps going without you. No check-ins. No steering. You come back when it is done. This sounds incredible. It is also why Peter burned $1.3 million worth of tokens in a single month. ➤ Here is the problem nobody talks about. Your spec document never covers everything. It is impossible to fully contextualize a product in one markdown file. Things evolve. Details get missed. The agent fills every gap with assumptions. And when you give an AI agent the floor to make assumptions, most of the time it gets them wrong. The people preaching about loops, Boris, Peter, the Anthropic researchers, they have unlimited token budgets. Of course loops make sense when tokens cost you nothing. If you are on a $20 or $100 subscription, this is not for you. You will burn through it and have nothing usable to show for it. It is a slot machine. You pull the lever. Sometimes you win. Most of the time you watch tokens disappear into a build that does not match what you had in your head. ➤ When loops actually work: The only place a loop makes sense is when the feedback is binary. Either the output met the criteria or it did not. No judgment. No taste. No nuance. Code review is the clearest example. Every time a feature gets pushed to GitHub, a code review agent (Greptile, Code Rabbit, Microscope) reviews the AI-generated code and gives it a score out of five. The rule: nothing goes to production unless it scores four or higher. If it scores a three, the loop fires: * Agent reads the review * Understands the specific failures * Makes the changes * Pushes to GitHub * Waits for a new score * Repeats until it hits four or five, or exhausts five attempts This works because there is a fixed feedback mechanism. The score is the signal. The loop has a clear definition of done. Even this breaks. When a code push exceeds 1,000 lines, the loop almost never reaches a five. Too much context for the agent to fully process. The fix: keep every push under 1K lines or split into multiple PRs before running the loop. ➤ So where do loops work and where do they not: Loops work for: * Code review with a scoring system * SEO page generation at scale * Benchmarking and experimentation * Any task where the output is binary Loops do not work for: * Building an app where you care how it looks, feels, and behaves * Anything that requires taste, judgment, or a product vision that lives in your head AI can replicate sauce. It cannot create sauce. The future will probably look different. Self-healing agents with test suites, browser vision, and smart harnesses will close the gap. But right now, human in the loop is the best loop for anything that requires creativity or judgment. Human in the loop is the best loop.

  • kr0der
    Anthony Kroeger (@kr0der) reported

    i love how the Cursor agent window integrates PRs into the app so you don't need to open GitHub Bugbot comments all come with a "Fix with Agent" which automatically queues up a message in the chat to fix the PR comment with Cursor profiles recently being launched, and their native PR + Bugbot integrations, i actually wonder if they're building a GitHub competitor 👀

  • itsharmanjot
    Harman (@itsharmanjot) reported

    Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.

  • NabZO560
    ??????????????🐍 (@NabZO560) reported

    GITHUB DOWN ?!

  • shipilev
    Aleksey Shipilëv (@shipilev) reported

    At some point, a reasonable strategy to fix GitHub performance issues would be to get a contractor job there, find ten bottlenecks (as one does), fix them, get paid and ****.

  • DakshnaK123
    Dakshankumar (@DakshnaK123) reported

    What's the actual job of your open-source community? I'm finding that just dumping code on GitHub for 'trust' isn't a real strategy. It needs a purpose, like finding your first 10 plugin devs or cutting down support tickets. What are you building yours for? #buildinpublic #opensource

  • JohnnyNel_
    Johnny Nel | AI for Founders (@JohnnyNel_) reported

    🚨 An open-source AI agent just hit number one on OpenRouter... and almost nobody checked if it was safe to run Everyone's racing to install it. $8 VPS. 170,000 GitHub stars. Self-improving skills. So I ran an actual security review before trusting it with my server. The findings are wild... 👇 The part everyone skipped in the hype: → The default config ships with FOUR critical and nine high severity findings → On local, it passes commands straight to your shell — no sandbox, no allow list → A poisoned skill becomes a permanent prompt injection that fires every time it's reused → And there was a real supply-chain incident: a backdoored dependency harvesting API keys, SSH keys, and cloud credentials And it gets bigger: the feature everyone praises — agents that learn and reuse skills forever — is the exact same door an attacker walks through once. Builders installing it blind. "Self-learning" silently turned off by default. Skills quietly going stale and making agents confidently worse over time. The project calls it powerful. Builders should call it powerful AND loaded. Here's what actually matters though: ✅ An agent that remembers and compounds on your work beats any disposable paid sub-agent ✅ But if you skip the security setup, you're one bad prompt away from full shell access to your machine ✅ Own your stack and lock it down first — or don't run it at all So the question isn't whether Hermes is impressive. It's whether you've hardened it before you hand it the keys — or whether you're about to learn the hard way. Full breakdown in the video below 👇

Check Current Status