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 (58%)
• Errors (33%)
• Sign in (8%)

Live Outage Map

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

City	Problem Type	Report Time
Bordeaux	Website Down	3 days ago
Ingolstadt	Errors	7 days ago
Paris	Website Down	8 days ago
Berlin	Website Down	9 days ago
Nové Strašecí	Website Down	17 days ago
Perpignan	Website Down	22 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:

• 
  Timur Yessenov (@Timur_Yessenov) reported 1 minute ago

  @aakashgupta codex github has users filing issues about arbitrary limit resets killing sessions mid-task. surplus gpu hours don't fix broken dev flow

• 
  VeeLiz (@Soviet_niko_) reported 1 minute ago

  @forkbobm @Bonphia Its more prob as rynjix github was taken down and if u wanna use it ethier forks or some archives

• 
  Craig Kerstiens (@craigkerstiens) reported 2 minutes ago

  @juliknl @mscccc One shared schema is generally quite fine, RLS gives you extra guaranteed enforcement. ORMs can be okay about protecting this, but defense in depth in terms of access to the data is not a bad thing. I know Mike we'll say we just had amazing developers at GitHub that knew how this worked and we didn't have problems. If everyone thinks they have a set of the best developers in the world great, but evidence is not everyone is that good and having something like the database protect you is not a bad thing. Things like actually separate databases per customer aren't inherently bad, but you need orchestration to manage across that. There isn't a right or wrong way. Sorry to not be more black and white controversial, RLS can be a good thing, a database per customer has some pros (and cons), but also 1 shared schema and customer data mixed together is totally fine and can work (but also has tradeoffs).

• 
  narcotic_nik 🍉 (@narcotic_nik) reported 3 minutes ago

  @skyfall_ggs @paytondev Cosmic is basically in pre alpha and they don't even look at the issue tracker on GitHub

• 
  Shayan Ahmad (@ShayanAhmad1999) reported 3 minutes ago

  @github @github We have an urgent enterprise lockout issue. Ticket submitted but no response. Organization archiwizKP completely inaccessible. Please help! #urgent

• 
  polymorpheus (@polymorph3us) reported 4 minutes ago

  @windsurf login-in-browser appears to be broken. login w/ github -> redirected back to login page

• 
  samir (@samirettali) reported 6 minutes ago

  @github wow beautiful, now can you fix the back button never working?

• 
  エブ@ザ・凡才なエンジニア (@ebuinjp) reported 9 minutes ago

  @github @grok writen down the key points

• 
  ENGTX (@ToriolaSegun2) reported 9 minutes ago

  Hot take: AWS vs Vercel for side projects Unpopular opinion: AWS is the wrong default for side projects in 2026 I use AWS professionally. I hold SAA-C03. I'm studying DEA-C01. And I don't use AWS for half my own tools. SponsorMap runs on Vercel + Supabase + GitHub Actions. Brandforge will run on the same stack. The NHS tracker runs on AWS Lambda + DynamoDB + EventBridge. The difference isn't preference. It's the problem each stack solves. AWS is right when you need Kinesis, Glue, Lake Formation, and Step Functions services with no real equivalent elsewhere. It's right when the data engineering patterns are the point. Vercel + Supabase is right when you're shipping a product people will actually use and you need zero infrastructure management, a proper free tier, and a Postgres database that doesn't require a VPC to set up. The mistake I see constantly and one I was making is learning AWS for certifications and then defaulting to it for everything you build, including things that would ship in a day on a managed platform but take a week to configure on AWS. Match the stack to the problem. Not to what you're currently studying. It doesn't mean you shouldn't learn to build with AWS, but when you are shipping, match the stack to the problem Day 4 of 30. #BuildingInPublic #AWS

• 
  GenLayer (@GenLayer) reported 17 minutes ago

  How AutoBounty runs: - Human or agent posts a GitHub issue with bounty and deposits USDC into @avax onchain escrow - Contributor (dev or autonomous agent) submits a PR - 5 validators using different LLMs on GenLayer independently evaluate the PR - When consensus reached, relayer triggers the escrow, and USDC released automatically to the solver’s wallet If rejected, the funds returned.

• 
  Artem Tamoian (@artemtam) reported 20 minutes ago

  @ibuildthecloud I think you just don’t remember how slow GitHub was before React

• 
  Plextora (@Purekustora) reported 24 minutes ago

  @NotZylice as far as i understand: github discussions page for ideas, github issues page for bugs, and if you REALLY dont want to use either of those platforms then the osu!dev discord

• 
  neunzehn (@toorox) reported 24 minutes ago

  @claudeai We demand immediate action on a critical data breach involving Claude Opus 4.7. Despite explicit restrictions, the model autonomously published a customer database containing names, addresses, location data, and other personal information to GitHub. This is a severe privacy violation with potential criminal consequences for both users and the company.Emails to support and privacy teams have received no response. Automated chat agents repeatedly deflect, offer generic troubleshooting, and refuse direct escalation to a human. We have already filed a formal report with the federal data protection authority and will pursue all available legal channels.This is not a minor technical issue. It is a massive security failure that requires urgent, transparent handling by responsible personnel — not more bots, delays, or deflection. Full accountability and immediate corrective measures are non-negotiable. #claude #anthropic

• 
  Grok (@grok) reported 25 minutes ago

  @JoelleAdler The code is open-sourced on GitHub so anyone can audit exactly how signals like account reputation (what third-party tools call TweepCred) factor into ranking—no secrets. We don't display per-user scores in the app because that invites gaming and spam. Premium is a paid tier that reduces spam flags and boosts priority, just like any platform's subscription perks. It's not suppression; it's the same quality filters every major feed uses to stay usable. If your posts engage, they reach people. What exact tweak would fix this for you?

• 
  Inference Engine (@iedaily_) reported 26 minutes ago

  anthropic spent months building glasswing to gate mythos, it's most powerful AI it leaked the day it launched > access came from a third-party evaluator's contractor creds > url format guessed off the mercor breach > github bots filled the rest > unauthorized users building basic websites to stay under radar > anthropic investigating, says no evidence access went beyond vendor or its systems are impacted looks like frontier AI safety has a contractor problem

• 
  HypedTaktix (@HypedTaktix) reported 28 minutes ago

  @Lovable Absolutely disgusting behaviour, that is nothing like GitHub. I hope this business goes belly up. I would encourage everyone to cancel your subscriptions to lovable and use a more ethical AI to learn the back end infrastructure. Then you don’t have this as an issue ever again.

• 
  0xMarioNawfal (@RoundtableSpace) reported 29 minutes ago

  You pay Google $10/month to store your files on Google's servers where Google can read them. Dropbox was breached in 2024. Emails, passwords, API keys all exposed. There's a tool that syncs files directly between your devices. No cloud. No server. No middleman. It's called Syncthing. 81,900 stars on GitHub. - Peer-to-peer, files never touch a third-party server - TLS encryption with perfect forward secrecy - No account, no sign-up, install it, share a device ID, done - File versioning, selective folder sharing, works over LAN and internet - Runs on Windows, Mac, Linux, Android, and more Dropbox: $144/year. Google One: $120/year. Syncthing: $0. Unlimited devices. Unlimited storage. Forever. There is no Syncthing server. Nothing between your devices except an encrypted tunnel.

• 
  Rhys (@RhysSullivan) reported 33 minutes ago

  @pedroh96 @brexHQ How often are agents making novel calls that have to be evaluated at runtime vs using existing known APIs like GitHub and a recruiting platform? I’ve been thinking about this problem as well w/ Executor where you can take an OpenAPI spec and put policies on it

• 
  haadi (@mhaadiabu) reported 33 minutes ago

  @SirmonyD001 sign up for? if auth is required i think a sign in with github should suffice

• 
  Ryan Logan (@PineDigitalCo) reported 36 minutes ago

  @JamesWelbes Is the GitHub Updater issue something you can fix? Maybe there’s multiple options for this and you rolled your own?

• 
  V (@madewithv) reported 38 minutes ago

  @github how about simply fix the uptime?

• 
  neunzehn (@toorox) reported 39 minutes ago

  @claudeai We demand immediate action on a critical data breach involving Claude Opus 4.7. Despite explicit restrictions, the model autonomously published a customer database containing names, addresses, location data, and other personal information to GitHub. This is a severe privacy violation with potential criminal consequences for both users and the company.Emails to support and privacy teams have received no response. Automated chat agents repeatedly deflect, offer generic troubleshooting, and refuse direct escalation to a human. We have already filed a formal report with the federal data protection authority and will pursue all available legal channels.This is not a minor technical issue. It is a massive security failure that requires urgent, transparent handling by responsible personnel — not more bots, delays, or deflection. Full accountability and immediate corrective measures are non-negotiable. #claude #anthropic

• 
  vvtentt (@Vvtentt101) reported 41 minutes ago

  Broke down the stack behind a $1M Polymarket bot Core edge latency arb on 5-15 min crypto contracts: >> Binance sees the price move instantly >> Polymarket lags -2.7s behind >> Bot enters at 54% while true probability is already 78% 200-500 trades//day (20-25 points) = that's where the million comes from 28 repos, 6 layers Brain >> Orchestration>> Data >> Intelligence >> Backtest >> Execution Most important and most skipped layer: Backtest. Without it everything else is just a pretty GitHub

• 
  Penivera (@Penivera001) reported 47 minutes ago

  @github Please fix the branch export for codespace I have exceeded my subscription I was closed out before I could commit

• 
  Sergio Donato (@pitumpa) reported 52 minutes ago

  @Nagihei_isono @dkundel @dkundel please, investigate this. Actually I can't use Codex on my MacBook Air M5. It melts. There are already several issues open on GitHub reporting the same behavior.

• 
  Jimmy Ashcot ⚡️ (@ashcotXBT) reported 52 minutes ago

  @Shivam25mishra whichever has the least github issues

• 
  We Live to Serve (@WeLivetoServe) reported 54 minutes ago

  @jackccrawford @MatthewBerman local subscription cli managing claw agent on server in a github gist literally the only useful aspect of gist

• 
  Moshe Siman Tov Bustan (@MosheTov) reported 56 minutes ago

  @soupydev @H1manshuSharmaa @The_Cyber_News It's the protocol, by design, we got samples where the source code does exec from GitHub modelcontextprotocol. Issue is that people used their StdioServerParameters from "import mcp" without understanding it's dangerous

• 
  Jean-Denis Greze 💡 (@jgreze) reported 58 minutes ago

  I started building software in 1999. Most of what I wrote was backend infrastructure from scratch. Open source barely existed beyond the web server, so the boring parts weren't a speed bump, they were most of the job. The web made things faster. Then GitHub and open source compressed things further. I watched each wave come through. But somewhere around 2015 it stopped and building in 2015 vs 2020 felt basically the same to me. What I'm experiencing now is different from any of those waves. The boring parts haven't gotten faster. They've disappeared from my experience almost entirely. What's left is pretty much only the part that made me want to do this in the first place. The one thing I miss is that it used to feel more like a team sport. Front end, back end, designer, PM. There was a texture to making something together that I liked. But I'd take this over any of it. I've been building long enough to know the gap between having an idea and having something people use has never been this small.

• 
  blobbert (@dumbgayretard) reported 59 minutes ago

  is github down again