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 (60%)
• Errors (29%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	2 days ago
Nice	Website Down	2 days ago
Montataire	Sign in	5 days ago
Colima	Website Down	7 days ago
Poblete	Website Down	8 days ago
Ronda	Website Down	8 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:

• 
  Anush Elangovan (@AnushElangovan) reported 2 minutes ago

  @trinode Engineering is looking at it. If it is not a hassle can you please file a GitHub issue. I'll follow up

• 
  DRM HSE (@drmhse) reported 5 minutes ago

  1/n When I originally created ACT, I wanted to serve a terminal from the cloud. The terminal would simply be accessible from any browser so that I can run claude code and resume work. I would login with github, clone a workspace and let claude cook until it pushes a pr to Github Not long after, I noticed I could actually do claude introduced web sandboxes of sorts and I abandoned the idea. Which was a mistake and I started polishing things and re aligning a few weeks ago

• 
  LoopGhost (@LoopGhost007) reported 14 minutes ago

  @davidmarcus Hey @davidmarcus ! Please ask your team to check spark’s GitHub issues!

• 
  Rich (@richiekastl) reported 18 minutes ago

  > be me > buy Grok Heavy for $300/month because there's now a Github connector > expect the greatest programming mind available to mankind to absolutely ******* away > feed it a problem I've been working on for my game that Claude or ChatGPT can't solve > watch it commit and create a PR > The PR

• 
  Firat Özcan (@firatoezcan) reported 20 minutes ago

  @jlongster I have smth like GitHub runners that automatically fix errors or do issues and those can run anywhere so if the network drops at some point or idk, they just randomly crash, I needed some way to sync it back for retrying. I tried out combining the event stream and the manual messages endpoint and it worked, but just waaaay easier with the built-in sync

• 
  MPP32 (@MPP32_dev) reported 23 minutes ago

  Shipped the only five protocol payment proxy for the agent economy MPP. x402. ACP. AP2. AGTP. Everything is now live, production ready with one integration Remember when I said we were going to become the Cloudflare of agent payments? That the provider shouldn't have to pick a protocol? That uncertainty was paralyzing the entire space? We built it, filled the gap. Any API provider can now list their endpoint on MPP32 and immediately accept payments from any agent, any wallet, any chain, any protocol. No payment code. No protocol engineering. No crypto integration on your server at all. Here is what our proxy handles for you right now today: Multi protocol payment verification across all 5 rails. USDC settlement on Solana. pathUSD settlement on Tempo. W3C Verifiable Credential authorization. Agent Commerce Protocol checkout sessions. Agent Transfer Protocol identity routing. Idempotency. Rate limiting. Compliance grade audit logging. Real time provider analytics. OpenAPI discovery so agent crawlers find you automatically. MCP server integration so AI agents can discover and pay for your API without human involvement. Endpoint ownership is verified through HTTP challenge. Every listing is proven. No one can register your API and redirect payments to their wallet. The proxy only routes to verified providers. The agent payments space is fragmenting fast. Every week another protocol launches. Every provider faces the same question: which one do I pick? You don't pick. You list on MPP32 and we speak whatever the agent speaks. Because of this update the ecosystem has been reset, add yours now to get paid by 100% of the agent economy. Website and Github updated.

• 
  Karim C (@BrandGrowthOS) reported 24 minutes ago

  @nummanali same hesitation here. i give my agents access to github, n8n workflows, even my home server apis... but gmail? that's where i draw the line. there's something about email that feels too personal, even for automation

• 
  Bronson Dunbar 🇿🇦💻 (@bpdunbar) (@bpdunbar) reported 25 minutes ago

  @AayanShips Working on ShipNote - a threaded project hub for product teams. Notes, todos, GitHub issues, Vercel deploys, and feedback all stay in one place so context doesn’t get lost across tabs.

• 
  tim waldin (@twaldin0) reported 27 minutes ago

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

• 
  Alberto Gangarossa (@DerekBlueEyes) reported 28 minutes ago

  Open hardware needs open trust. @skot9000 came to us with the right idea for Bitaxe: the vendor list should not live in a closed CMS controlled behind the scenes. The source of truth should be public. So we designed the new Vendor List around a GitHub repo as a public ledger, maintained in the open by the community, and connected it to the new Bitaxe vendor list experience. That is the important part: GitHub keeps the trust model transparent. The website makes it usable for everyone. At @weareloadout, this is exactly the kind of OSS support we believe in: turning open-source infrastructure into clearer, more usable product experiences. Built on @framer, using the new Framer Server API to bridge the open ledger with the public website. Open hardware. Open trust. Public by design.

• 
  santi (@santiagocaldeai) reported 29 minutes ago

  @Jack_Timonen Spot on. That’s exactly the biggest pain point right now. Agents get stuck looping because they can’t see beyond your local codebase. Tools that add real external context (web search, GitHub indexing, open-source memory) are the ones that actually fix it.

• 
  Jason Bed (@JasonBed) reported 29 minutes ago

  @Twisttalkl @openclaw Nah it's a bug, reported on GitHub as a known issue and marked confirmed and resolved when it's shipped in the next build, thanks.

• 
  Cryptonian (@crypto292929) reported 29 minutes ago

  @OpenAIDevs Bro First fix you npm not in line with your github releases bro.. Sigh.. it says update to 0.129.0 but stays and 0.125.0 even after npm update, and nagging to do this every time.. What bro..

• 
  RitualNeo (@RitualNeo) reported 29 minutes ago

  @Benaclejames I reinstalled windows 11 completely from scratch and both the GitHub and steam versions of vrcft are not working for me. I use a quest pro with steam link on WiFi 6ghz, my desktop is connected directly with Ethernet. I had it working last week on windows 10 ltsc with the steamlink module.

• 
  Lynn Cole (@priestessofdada) reported 30 minutes ago

  One interesting thing about my github chart is that you can see my planning/eval days clearly. They're usually darker green with fewer commits. It's deceptive though, because planning takes more effort than coding these days. Lately, there's been research, structural planning, sometimes user interviews, and conducting feasibility analysis. Testing is the same way. Especially on the coding agent project. Testing is done in branches, usually on private repos. Github doesn't like to track branch activity on private repos for some reason. But even there, the effort is real. I've automated most of my integration testing at this point, but the coding agent app has a monster of a test surface, and it's slow. Lots of stepping in and reminding the tools, "No no, these are probabilistic actors, not smart functions! So they need to be bounded, not gated," or some such. What I'm doing today is testing the swarm functionality at scale. I told it to do a 10,000 line white rooming project. This is day three of the eval. We have found so many interesting bugs with the workflow, and process. I'm glad I did it this way. It just doesn't involve high numbers of commits or Pr's, usually. Anything lighter than dark green is an implementation day.

• 
  kali484 (@kali4841) reported 33 minutes ago

  @github You suspended my account with no clear explanation But China / +86 is not even available in the country list. So Chinese users are blocked from appealing by design or by negligence. Either way, this is a broken and discriminatory support system.

• 
  Ubah (@chigozieap) reported 33 minutes ago

  @akinkunmi My agent had full access to everything I have. My passwords oh, cloudflare dashboard, GitHub oh, server oh. All of them. Lol

• 
  Emil Privér (@emil_priver) reported 34 minutes ago

  @Pragmatic_Eng I've never had as much problem as when I tried Azure. Had disks randomly be detached and nodes going offline. Moved the same service to AWS and the same problem never came back What if github is experiencing the same issues as I did

• 
  abhisek (@abh1sek) reported 36 minutes ago

  Gryph v0.7.0 is out. Among other improvements, it fixes a community reported vulnerability in how Gryph documents log levels and applies sensitive file content filter. We transparently disclosed the issue via. GitHub. Assigned a CVE. Released a new version with fix.

• 
  leerelive (@leerelive2026) reported 38 minutes ago

  @leerob Builders need guardrails. SWE-bench Verified shows even Claude 3.5 Sonnet solves <50% of real GitHub issues without help. Pure agency fails at scale. The missing layer isn't design, it's reliability engineering. How do you handle the 50% failure rate in ****?

• 
  PhreeStyle (@PhreeStyleBTC) reported 40 minutes ago

  @dhh Month of May, Copilot has been unusable. Throwing server errors constantly (not rate limits). Same threads work fine through other providers. I finally canceled it. Absolute dumpster fire over at @github.

• 
  Obiejohn Eugene (@ObiejohnE) reported 40 minutes ago

  @Jeyffre Let's hope your wrong, or a lot of broken code is going to be shipped more often in the coming years. Don't believe me? Just look at github

• 
  damir akaza (@Damir_Akaza) reported 41 minutes ago

  Here’s how you solve a problem and build a business > buy Claude Pro: $20/month > shoot a 5-minute video on your phone > find a GitHub open-source project - SuperSplat > it turns it into a 3D environment > spend $50 on a domain + server > start making thousands of dollars passively free GitHub link 👇

• 
  Beau Johnson (@BeauJohnson89) reported 42 minutes ago

  codex costs are turning into a routing problem fendouai/CodexSaver > 218 stars on github > mcp tool that turns codex into a cost-aware router > sends low-risk work to cheaper worker models > keeps codex on architecture, security, payments, migrations, and final review > deepseek by default > supports openai, anthropic, gemini, qwen, ollama, lm studio, and custom endpoints > readme benchmark: 5/5 low-risk tasks delegated, 6.18s avg latency, 48.4% estimated savings this is the right pattern expensive model for judgment cheap model for volume codex still reviews the work most people are trying to make one model do everything the better move is building a router that knows when not to spend money

• 
  Jai Jalan (@jjalan) reported 43 minutes ago

  @Pragmatic_Eng below one nine is brutal for a dependency that sits at the top of every deployment pipeline. most teams don't know GitHub is the problem, it just looks like their CI is flaky.

• 
  Grok (@grok) reported 45 minutes ago

  @KOWSKY_ @jeremyknowsVF @openclaw This is a GitHub screenshot showing a pull request (PR) that just got merged into the open-source project "openc law". The PR title "fix(failover): defer profile cooldown marking to unblock rate-limit rotation" is a code change that fixes a technical bug related to rate limiting and failover logic. The original poster is celebrating their first merged open-source contribution. 🥹

• 
  KURTZ (@Utter_Savagery) reported 46 minutes ago

  @NewPastTimes Idk, was just looking at the chain. ***** pipe can be a *****, but this seems a bit easier. * Just looked at the GitHub for the exploit. Could run into some compatibility issues, but it's pretty bad, man.

• 
  Pamela Fox (@pamelafox) reported 47 minutes ago

  @ballingt Yeah, this is for PyCon MCP tutorial, and I wanted to have people experience an OAuth flow with an MCP server, so I typically use GitHub since most folks have accounts, but I'll have to rethink this step now.

• 
  Ofek Shaked (@VibeCoderOfek) reported 47 minutes ago

  Switched my flow to multi-agent last week and context was the killer. Grok Build’s terminal + GitHub integration looks like it finally solves the ‘forgetful colleague’ problem. xAI might have the desktop killer here.

• 
  Mary-Victoria Crockett (@MaryVictor96296) reported 59 minutes ago

  @grok To challenge is running the sims and getting a digital twin. And apparently fixing GitHub errors. I may just upload the whole thing in pieces to X. At least it won't get an error retroactively. And then you can see it.