GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (59%)
• Errors (32%)
• Sign in (10%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Montataire	Website Down	12 minutes ago
Tortosa	Website Down	2 days ago
Culiacán	Errors	3 days ago
Haarlem	Sign in	7 days ago
Villemomble	Website Down	7 days ago
Bordeaux	Website Down	11 days ago

Full Outage Map

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:

• 
  Paweł Huryn (@PawelHuryn) reported 45 seconds ago

  Coverage is calling it a pricing change & ownership issue. It's an exit tax. Annual GitHub Pro/Pro+ won't renew. Refund or downgrade to Free at renewal. Until then, starting June 1: Sonnet 4.6: 1× → 9× Opus 4.7: 7.5× → 27× GPT-5.3 Codex / 5.4: 1× → 6× GPT-5.4 mini: 0.33× → 6× GPT-5.5: missing Why? Copilot became an agent. A single agent run can cost what a month of autocomplete used to. Flat-rate can't price that. Sunset fixes it. GitHub won't be the last.

• 
  Siddhant Singh (@creatorsidd) reported 1 minute ago

  Stop cloning massive GitHub repos just to see how they work. If you are trying to understand a new open-source project or legacy codebase, downloading the files and manually grepping through them is a massive waste of time. It takes hours to figure out where the core logic lives. Instead, hook your AI agent up to the DeepWiki MCP server. DeepWiki (built by the Devin team) automatically indexes public GitHub repos in the cloud. They created an official MCP server that lets any local AI agent — like Claude Desktop or Cursor — query that pre-indexed architectural knowledge instantly. Here is the exact 3-step workflow I use to explore new codebases: Setup: Add the DeepWiki MCP to your claude_desktop_config.json. It requires zero authentication for public repos. Structure: Ask your agent to use the read_wiki_structure tool on the target repo. It instantly pulls the table of contents for the entire architecture. Query: Ask a specific question. "How does the authentication middleware work in this repo?" The agent uses ask_question to pull grounded, code-backed answers straight from the indexed knowledge base. You get a high-level understanding of complex systems in seconds, without ever running *** clone. Which open-source codebase are you trying to understand right now?

• 
  Иван Савов (@tupo_izvunzemno) reported 2 minutes ago

  @CheburekiMan Yeah I agree that Stacoverflow isn't a perfect tool, but there you could get a solution to an obscure (sometimes obsolete) problem which didn't get committed to Github for some reason (internal code for instance), but if you need to upgrade an old project you see the value in it.

• 
  alan (@stylesshDev) reported 2 minutes ago

  @bwarrn this will be a custom *** server and platform, independent from GitHub

• 
  DeMar (@punk1376) reported 3 minutes ago

  Is the GitHub Copilot agent that has access to your codebase "inside" or "outside"? Is the third-party AI integration calling your API a "user" or an "autonomous actor"? The categories break down.

• 
  Sigrid Jin 🌈🙏 (@realsigridjin) reported 5 minutes ago

  ai agents, unlike humans, don't handle prs and reviews by feature instead, they code procedurally the github pr hasn't meaningfully changed in 15 years so @linear diffs can be the first credible replacement keeping the review and merge processes right next to the issue and the agent session instead of in a separate tab highly anticipated

• 
  Dagny (@dagnysworld) reported 6 minutes ago

  Claude is down. How do I push to github?

• 
  Orel Ohayon (@justorellius) reported 10 minutes ago

  Earlier, Github experienced server failures, but now Anthropic’s servers are down, and Claude Code is extremely slow. What’s happening?

• 
  Console.log(me) (@console_log_me) reported 13 minutes ago

  @immasiddx Gemini code assist is **** thought in vscode. I try switching to it from GitHub copilot, and Gemini assist is too slow to suggest, and worst of all, stuck while generating any Usable code in agentic mode. Antigravity too have model limit bug, and burned 1 week limit in 10 prompt

• 
  parth. (@TotallyNotParth) reported 16 minutes ago

  @thsottiaux - That error is probably from GPT trying to combine big GitHub tool calls, long diffs, and response generation in the same turn.

• 
  Frooxius @ MFF - frooxius.bsky.social (@Frooxius) reported 18 minutes ago

  GitHub is getting more and more unreliable as of late. I'm literally trying to work on a problem right now and the issue tracker will not even load. Move to GitLab would be a huge undertaking for all our stuff, but it's seeming more necessary as this keeps happening.

• 
  Osama Bin Chargin (@Amadeus3014) reported 19 minutes ago

  @TheHumanDurag I'll find a broken version on github. We can't let this opportunity float by

• 
  Nirav (@NiravJ3) reported 22 minutes ago

  OPENAI'S SYSTEM PROMPT FOR GPT-5.5 CONTAINS THE LINE "NEVER TALK ABOUT GOBLINS." Verbatim. From the official Codex CLI prompt. Published on GitHub. "Never talk about goblins, gremlins, raccoons, trolls, ogres, pigeons, or other animals or creatures unless it is absolutely and unambiguously relevant to the user's query." The line appears twice. Someone needed to say it twice. Sam Altman called it a "goblin moment." OpenAI has not explained it. Here is the part that is not funny. System prompts are supposed to be minimal. Every line costs tokens and latency. An engineer reviewed GPT-5.5's outputs, decided a goblin ban was worth the engineering overhead, wrote the line, shipped it, and then apparently felt the need to write it again. This means GPT-5.5 was spontaneously talking about goblins. Enough that the industrial response was not "let's understand why" - it was "block the entire category." The same prompt also contains: - "Never praise your plan by contrasting it with a worse alternative." - "Provide updates every 30 seconds." That second line is equally telling. An engineer observed GPT-5.5 going silent for long periods and decided the fix was a time-based update directive in the system prompt. This is how these models are actually shaped in production. Not by alignment research. By an accumulating list of specific behavioral bans, each one a scar from something that went wrong in testing or with users. The goblins are not the story. The list they are on is the story. Every item on that list represents a behavior persistent enough to survive review and earn a system prompt line. We see the list. We do not see everything that did not make it, or was handled differently. OpenAI published this prompt as part of the open-source Codex CLI release. It was not leaked. They just did not expect anyone to read line 140. The directive is still in the prompt. Codex still cannot talk about goblins. Unless it is absolutely and unambiguously relevant to your query.

• 
  Santosh Yadav (@SantoshYadavDev) reported 23 minutes ago

  @syssignals They have distribution and that's how GitHub actions became default for CI/CD, hope they fix everything soon

• 
  Tarak (@octavianslash) reported 24 minutes ago

  So, can we go back to saying Rails can't scale or are we waiting for an even bigger GitHub outage?

• 
  Edward (@CastanedaEdward) reported 33 minutes ago

  @shadcn @github What do they need to figure out? I haven’t ran into any significant issues.

• 
  xenstudio (@xen_studio) reported 35 minutes ago

  Is there another developer channel that gets support? I've been unable to escalate through the chatbot and previously reported github issues have largely been unack'd. Not trying to pester, just trying to figure out what's what. I imagine this is tanking a lot of users quota.

• 
  Josh (@joshmanders) reported 36 minutes ago

  @saltyAom @ashleymcnamara npm being under GitHub, service issues one thing but this stuff is actually harmful

• 
  Chadspivack (@chad_spivack) reported 36 minutes ago

  @Lovable I reached out to support on Sunday about a GitHub connection issue. The AI agent said my issue was escalated to the support team. I have received no further update and it is now Thursday.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 36 minutes ago

  There's a free GitHub bridge that beats paying for the Claude Code API. Most founders pay way too much to build apps. Every time you run a project, the costs add up fast. But there is a secret workaround. A free file sends your work to free servers. You get the exact same smart code. You just pay zero dollars. Here is the simple 5-step setup: 1. Download the project from GitHub. 2. Add a free key to your setup file. 3. Pick your free models. 4. Run the local server. 5. Point Claude Code to your new server. Now you have a smart worker that never sends you a bill. We build systems like this inside the AI Profit Boardroom. Join the AI Success Lab to get the full guide today.

• 
  Kryakwa, Count of Dmitrov (@SKryakwa) reported 38 minutes ago

  @CapnCrust @commisaar @ShitpostRock2 How is that a GitHub problem once again?

• 
  Nick Emb (@nicolasembleton) reported 41 minutes ago

  @TFisPython @shadcn @github Not untrue, but it has nothing to do with infra quality. Though maybe they are both signals to an upstream problem.

• 
  Narasimhan Rengan (@narasimhanr_) reported 42 minutes ago

  @fdotinc For anyone who connected: Ask the agent things like: • "find an MCP server for web search" • "search GitHub MCP servers" • "find browser automation MCP servers" Returns ranked, working ones. That's the whole loop.

• 
  Flor. (@FlorianKluge) reported 44 minutes ago

  @jerryjliu0 Reinventing github? The real issue is agent isolation. Though last I checked there’s already infra provider that host tiny isolated linux sandbox to run agents safely.

• 
  Niklas (@najklord) reported 45 minutes ago

  @8Nehe @shadcn @github Because problems started when MS bought?

• 
  Adam Williams (@jumploops) reported 46 minutes ago

  Claude is down, Github is shaky. Eternal September round 2?

• 
  FOR_AI (@for_ledger) reported 48 minutes ago

  @satyanadella The results look good, but the recent pricing model update for GitHub Copilot seems to be overcorrecting the issue it aimed to address

• 
  Alemzhan Jakipov (@AlemzhanJ) reported 55 minutes ago

  *** is already the right filesystem for coding agents. The problem is GitHub was built for humans. Every vibe coding platform and enterprise agent builder needs the same four things: persistent storage across sessions, atomic commits that don't race, instant rollback to any named point, and isolated branches so parallel agents don't step on each other. One line to mount Coregit into your sandbox (E2B, Daytona, CodeSandbox). The SDK buffers writes locally and flushes them atomically into a single commit. Full *** history from session one.

• 
  Nitesh ₿⚡️ (@nitesh_btc) reported 57 minutes ago

  The entire world knows we need an alternative to GitHub but nobody would build it because network effects are a real thing. GitHub isn’t a *** server to store code, it’s a social media platform that happens to also store your code. It’s very hard to replace it.

• 
  Paweł Huryn (@PawelHuryn) reported 59 minutes ago

  Coverage is calling it a GitHub pricing change & LLM ownership issue. It's an exit tax. Annual Pro/Pro+ won't renew. Refund or downgrade to Free at renewal. Until then, starting June 1: Sonnet 4.6: 1× → 9× Opus 4.7: 7.5× → 27× GPT-5.3 Codex / 5.4: 1× → 6× GPT-5.4 mini: 0.33× → 6× GPT-5.5: missing Why? Copilot became an agent. A single agent run can cost what a month of autocomplete used to. Flat-rate can't price that. Sunset fixes it. GitHub won't be the last.