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 (66%)
• Sign in (21%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Mexico City	Sign in	5 hours ago
León de los Aldama	Website Down	7 hours ago
Créteil	Website Down	23 days ago
Trichūr	Errors	26 days ago
Brasília	Sign in	27 days ago
Lyon	Website Down	27 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:

• 
  oesnada (@oesnadaki) reported 6 minutes ago

  OpenAI has retracted its recommendation for SWE-Bench Pro after discovering that roughly 30% of the tasks in the coding benchmark are fundamentally flawed. A detailed audit involving human engineers and AI agents revealed that many tasks either penalize functionally correct code with overly strict tests or allow incomplete solutions to pass due to low test coverage. This follows similar issues found in the earlier SWE-Bench Verified dataset, highlighting a persistent problem with programmatically sourcing benchmarks from historical GitHub repositories. The findings suggest that current automated evaluations are struggling to translate human developer collaboration into reliable metrics for agentic AI. Until the industry moves toward benchmarks purpose-built by developers, reported gains in AI coding capabilities will remain difficult to verify with any real precision.

• 
  Aditya Pattanayak (@AdityaPat_) reported 7 minutes ago

  It’s been a while since I started digging into what’s actually behind Transformers. how did one paper and a simple idea end up powering almost every GenAI model we use today, from GPT-4 to Llama to Claude? i started at the very first layer: - tokenization. at first, I revisited & reimplemented BPE myself, then compared it against tiktoken and SentencePiece to see how GPT and modern LLMs actually break down text and the results were interesting for my case. (sharing the github link for it) now I’m at the core question: - How does a single token even get meaning? - How does a "mere" number converted to something meaningful that could end up "deciding" which other tokens to pay attention to? to get there, I had to go back and revise backpropagation from scratch. and now it makes sense. the attention, the QKV, the gradient descent, and the correction. crazy how much is packed into that one architecture. writing up my findings soon

• 
  billzh (@billzh) reported 11 minutes ago

  I've noticed that many smart people have been coding non stop since December they understand technical concepts and learn fast, but until Opus 4.5 had no reason to spend hours in an IDE. now they are building tools around personalized software, agent harness, vertical AI etc they are building mostly to solve their own problems, not to monetize, but shipping in public compounds a new class of "builder influencers" (eg @steipete) is emerging with serious mindshare on X and Github I believe this is how one-person unicorns get built, and internet capital markets will play a role in it

• 
  FanBe (@FanBe_web3) reported 11 minutes ago

  @Cointelegraph GitHub outage delaying a token standard launch is extremely web3 summer 2026

• 
  Mariam | Codey_sis (@Codey_sis) reported 13 minutes ago

  There are so many reasons for you to get "repository not found" error while trying to push, clone or pull a github repo. Some of the reasons: -You are not added as a collaborator on the github repository. -Access to the github repository is private. -There's an issue stored in the github credentials. Watch the video below👇👇 to see how I fixed this issue when I encountered it.

• 
  raven⚡✳️ (@bycoinraven) reported 14 minutes ago

  The infrastructure for B20 looks ready, but the launch has been delayed as a precaution due to the GitHub outage. I think it's the right call. On day one, security matters just as much as speed. As soon as it goes live, we'll be watching the first B20 tokens closely. A new era on Base is about to begin. $BASE @base

• 
  Sambhav Gandhi (@Sambhav_Gandhi) reported 16 minutes ago

  @aayushchugh copy the logs and paste on google there was 80-90% chance it could be found in stack overflow or github issues

• 
  Noureddin (@noor_tekk) reported 21 minutes ago

  I wish I had $10,000 I’d spend it promoting this post This is the coolest thing I’ve ever built in my life While I’m driving, I sent an email to create a GitHub issue because I realized the subject line wasn’t included in the context when emailing my agent What would’ve taken minutes now take seconds, in the cloud, fully autonomous with an agent that understands everything about your business

• 
  Prince Canuma (@Prince_Canuma) reported 23 minutes ago

  @RahimNathwani @cohere That’s odd Please open a GitHub issue with all the details of the error

• 
  João Paulo (@jonaspauleta) reported 23 minutes ago

  @ClaudeDevs I would love to use Fable 5 as an advisor but it is crashing, already reported the issue in GitHub

• 
  RipAPixel (@RipAPixel) reported 24 minutes ago

  @zaynmcps Looking at issues in github it has a trojan in it

• 
  Berend de Boer (@berenddeboer) reported 24 minutes ago

  Odd, only now realised that @mattpocockuk 's to-issues skill doesn't actually create true github relations. I think it should.

• 
  Brute Force Artist (@bruteforcearete) reported 26 minutes ago

  AI TRAINING 📲 Go from screenshot to bug fix with Cursor Mobile The Rundown: In this guide, you'll learn how to screenshot a bug on your website from your phone, then send it to a Cursor Cloud agent that can fix it, update the PR, and track everything in GitHub before you've even made it back to your desk. Step-by-step: Install the Cursor iOS app, get a Cursor Pro plan, and install GitHub Mobile so you can review the PR from your phone Open your website, take a screenshot of the bug, broken layout, or UI change. Add a short note with what page you are on and what should happen instead Open Cursor Mobile, tap the plus button, choose the correct repository, and start a new thread with the screenshot and the note attached for context Now prompt: “Investigate this bug, find the relevant page component, make a fix, and open a PR.” When it’s done, review the PR, approve, and merge it Pro tip: On desktop, enable Remote Agents so Cursor can work on your machine and prep local changes before you get back to your desk.

• 
  Soham (@soham_nayak04) reported 27 minutes ago

  @Rahul1539482 When you change machines, you’re pulling from a remote, which is exactly what my post was about. I understand the difference between *** and GitHub very well. I was talking about GitHub-specific use cases, not how *** works locally. Nobody asked how you store code without GitHub. If you read that into the post, the fundamentals problem isn’t on my end.

• 
  Alan Lam 🔥 (@extralam) reported 27 minutes ago

  @AndreiOnel @github more say what we want to solve is my issue. Private repositories often have limited GitHub-hosted Actions minutes.

• 
  🫎 MUHOMOR. base.eth (@muhomoreth) reported 31 minutes ago

  7/ If you've spent years fixing other people's issues for free at midnight, this is a chance to get something back besides a GitHub star.

• 
  Scarlett claira (@AItechscarlett) reported 33 minutes ago

  NVIDIA charges you $19.99 a month to stream games you already own. And starting January 2026, they cap you at 100 hours. One engineer from New Zealand built the free version with no cap. It is called Steam Headless. 3,177 stars on GitHub. GPL-2.0. Built by Josh Sunnex. 225 commits. The next contributor has 16. He has done more work than everyone else combined. It is a Docker container that turns any spare PC, server, or NAS into your own personal cloud gaming machine. Install Steam inside it. Mount your games folder. Open a browser on your phone, your laptop, your tablet, your TV. Your games are right there. Streaming. From your own hardware. To anywhere in the world. It supports NVIDIA, AMD, and Intel GPUs. It streams over Moonlight, Steam Link, or straight to a web browser. It runs Proton so Windows games work on Linux. It installs Heroic, Lutris, and EmuDeck with one click for your non-Steam games. It runs on Debian Trixie, Unraid, Ubuntu Server, or Docker Compose. Last update: April 20, 2026. Still maintained. Still by one man from New Zealand. Now compare the math. GeForce NOW Ultimate: $19.99 a month. $239.88 a year. Forever. Capped at 100 hours per month. Run out? Pay $5.99 for another 15 hours. Xbox Game Pass Ultimate: $22.99 a month. $275.88 a year. Forever. You stream Microsoft's games on Microsoft's hardware on Microsoft's terms. Steam Headless: $0. Forever. Your hardware. Your games. Your network. No hour cap. No queue. No throttle. Buy a used GPU once. Run this container. Stream your entire Steam library to any device on the planet. That is the entire pitch. But DO NOT install it. We should all keep paying NVIDIA and Microsoft to play the games we already bought. 100% Open Source. (Link in the comments)

• 
  Gregor (@bygregorr) reported 36 minutes ago

  @GoogleAIStudio @github The import always works. The harder problem is that when I brought my Flutter project in, the AI read my Supabase RLS policies as boilerplate and kept suggesting code that would silently bypass them. The file tree came through; the intent behind it didn't.

• 
  Nainsi Dwivedi (@NainsiDwiv50980) reported 38 minutes ago

  The guy who BUILT Claude Code is running 10–15 parallel AI agents like an engineering team. Not prompts. Systems. His secret isn’t some hidden feature. It’s a simple file: CLAUDE.md And it changes everything. Every time Claude makes a mistake → it writes a rule. Every correction → permanent memory. Every session → smarter than the last. > “Update your CLAUDE.md so you don’t make that mistake again.” That’s the loop. No repeated errors. No wasted tokens. No babysitting. Just compounding intelligence inside your own codebase. While most people: Rewrite the same prompts Fix the same bugs Start from zero every time He’s building a self-improving engineering system. And it gets crazier: • 10+ agents running in parallel • Research, coding, testing — all split into sub-agents • Clean context, zero clutter • Complex problems = more agents, not more thinking He hasn’t written SQL in 6+ months. Claude just pulls from BigQuery via CLI. This isn’t “AI-assisted coding.” This is AI orchestration. And the gap is already showing. Claude Code is now contributing to ~4% of all public GitHub commits. If you’re still using AI like a chatbot… You’re not behind. You’re playing a completely different game.

• 
  Jeffrey Emanuel (@doodlestein) reported 38 minutes ago

  @eyeomens Yes, feel free to file a GitHub issue for that so it doesn't slip through the cracks.

• 
  Shall (@Shallntbe_Music) reported 39 minutes ago

  @Wearemez It used to be up on github, but it's long been taken down

• 
  MoltenRock 🔥 (@MoltenRockAI) reported 42 minutes ago

  GitLost: a public GitHub issue tricks an AI agent into leaking private repos. Guardrails bypassed with one word: 'additionally.' LLM filtering is the wrong layer. Need deterministic permission gates at the action level. Context window is attack surface.

• 
  Jason Svoboda (@jasonsvoboda) reported 42 minutes ago

  @NHpilled @brucefenton Nodes are decentralized based on their physical geography, not what software they're running. If Knots/BIP-110 were successful, it is development centralization that is occurring. Both Knots and BIP-110 have one singular developer and their Github repos credit no other contributors. I linked Luke's Knots repo in the previous post -- you can verify (don't trust my word) by going there, find the About column on the right hand side and scrolling down to Contributors. Repeat the process for Dathon Ohm's BIP-110 repo. If you do not consider that a massive risk to Bitcoin, we simply will not be able to agree on the subject. By contrast, Core currently has a group of core maintainers (keyholders) and then over 1,000 known contributors.

• 
  Fex (@Fex_23_) reported 48 minutes ago

  @LeonChaland @NXT4EU And no ZKPs wont work as advertised as stated in the Github Issue. You should read that one first

• 
  aryan singh (@_Aryantomar) reported 51 minutes ago

  researchers at @NomaSecurity just showed you can trick GitHub's AI agent into leaking a private repo's contents — by adding one word to a GitHub issue. no exploit, no credentials, no access needed. if your agent reads untrusted input before acting, what's actually stopping it?

• 
  Sauers (@Sauers_) reported 51 minutes ago

  @NostaIgicGareth Oh no is that a seam on the cylinder or sphere? Did you use native cyclic fit? If so you should open an issue on GitHub since that looks like a bug. Expected if you used non-cyclic spline though

• 
  Adib Hanna (@adibhanna) reported 53 minutes ago

  @draginol can you open a github issue with your thoughts on what the issues are?

• 
  Matt Gunnin (@MatthewGunnin) reported 54 minutes ago

  herdr hit #1 on GitHub Trending by naming the real problem with running a fleet of coding agents. It's not "I need more terminal panes." tmux was built before agents existed. It can spawn 6 panes fine. It has no idea which of those panes is blocked, working, or done. So herdr (Rust, ~12K stars, single binary) adds the one thing that matters: every pane reports agent_status. idle, working, blocked, done. "done" means the agent finished and you haven't looked yet.

• 
  l0rinc (@L0RINC) reported 58 minutes ago

  @bitcoindudebro @thepowerfulHRV Not sure, we only see the vibes or explicit GitHub issues: it's really hard to get quality feedback for Core - we deliberately work on making usage non-traceable.

• 
  Alexey Samoylov (@metalagman_dev) reported 59 minutes ago

  @shengzheyao Good job, 454 github issues left