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	2 days ago
Ingolstadt	Errors	6 days ago
Paris	Website Down	7 days ago
Berlin	Website Down	8 days ago
Nové Strašecí	Website Down	16 days ago
Perpignan	Website Down	21 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:

• 
  代々木ピンボール (@Yoyogi_Pinball) reported 42 seconds ago

  @vercel_support I keep getting a 705 error when trying to log in to my GitHub account, and I literally can't do anything. Will I be able to log in after some time has passed?

• 
  TheLegend27 (@glencoe2004) reported 1 minute ago

  @xwanyex Hey, you know how GitHub going down frequently has become a bit of a meme recently? They're going down recently because they processed more commits last month than they did in the entirety of 2025.

• 
  Santosh Kathira (@Santosh74038967) reported 2 minutes ago

  @chribjel Yeah. It makes sense. My GitHub actions constantly kept breaking during the last 2 days due to 504 errors while trying to download other GitHub dependencies. If they need time to get their stuff in order, it is fine.

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

  @github @grok writen down the key points

• 
  John Ennis (@johnennis) reported 6 minutes ago

  @manicode I do something similar already with @elves_skill, but the GitHub issue idea might add extra durability I think I'm going to fold that idea into Elves in the next update

• 
  Travis Cook /compact (@travis_cook_) reported 7 minutes ago

  Feeling very productive this morning with my Claude and @openclaw stuff. I'm 10xing. Here's the INCREDIBLE amount of work I've done: - got 5-6 github codes and set up 2FA - pulled down some new code but can't get it running - restarted the slack connection and gateway several times - reset some passwords and connections - checked the sessions and heartbeats I'm on fire! as you can see, I'm really LOCKED IN.

• 
  James Duke (@dukebiz) reported 10 minutes ago

  Three of the top five AI repos on GitHub right now are visual builders. Langflow. Dify. Flowise. Drag and drop. No PhD required. Here's what that means if you're building in 2026: The moat used to be "who can ship the model". Now it's "who can ship the workflow". Anyone with a problem and an afternoon can wire up an agent that would have taken a team of ML engineers a full quarter in 2023. This is the biggest shift nobody in your feed is framing clearly: The skill that wins in 2026 isn't coding. It isn't even prompting. It's knowing what to build. And for whom. And why now. The people who sat out 2025 waiting for AI to "settle down" just missed the easiest building window in tech history. Pick one problem. One audience. One tool stack. Ship this week. The gate is open. Walk through it.

• 
  SimpleMan🏴‍☠️ (@SimpleMan887) reported 10 minutes ago

  Every day several problems. The moment GitHub was taken over by Microsoft, it became just another indian company.

• 
  Apostolic (@Sanny23861994) reported 18 minutes ago

  @cryptorand AI went from solving 33% of real GitHub issues in mid 2024 to clearing over 70% by late 2025. That is not a gradual curve, that is a cliff. The same people gatekeeping tech careers with "learn to code" advice never updated their priors.

• 
  The AI Gold Rush 🌟 (@aigoldrushh) reported 20 minutes ago

  What a great time to be alive!! It costs: > Claude = coding. ($20/mo) > Vercel = deploying. (Free) > Supabase = backend. (Free) > GitHub = version control. (Free) > Clerk = auth. (Free) > Stripe = payments. (2.9%/transaction) > Cloudflare = DNS. (Free) > Resend = emails. (Free) > PostHog = analytics. (Free) > Sentry = error tracking. (Free) > Upstash = Redis. (Free) > Pinecone = vector DB. (Free) > Namecheap = domain. ($12/yr) Just $20 to build a MILLION dollars startup. What's your excuse?

• 
  Andres (@andfkdev) reported 23 minutes ago

  @nico_jeannen And another suggestion is to not build the app in the same server otherwise all resources gonna be used for that instead of serving the traffic, even blocking them. Better rely on third party (Github CI, etc....) then pull the build to the server!

• 
  Shayan Ahmad (@ShayanAhmad1999) reported 25 minutes ago

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

• 
  CyrilXBT (@cyrilXBT) reported 34 minutes ago

  @OVO_Kareem exactly right. shodan, dorking, GitHub search these tools have been finding exposed credentials for years. vibe coding did not create the problem. it just massively increased the number of people making the same mistake at the same time. the attack surface grew. the attackers noticed.

• 
  Raynhardt Coetzee (@Raynhardt_dev) reported 36 minutes ago

  GitHub Copilot just paused new signups because they ran out of compute The biggest AI coding tool on the planet capacity constrained. That's the cost of building on closed infrastructure: - their outage is your outage - their pricing change is your pricing change - their capacity limit is your growth limit The labs will always prioritize their own scale over yours. That's not a criticism. It's just physics. Own your model. Own your harness. Own your routing. That's the whole argument for AgentZero in one news cycle.

• 
  Hardik Gohil (@GohilHardy) reported 37 minutes ago

  - Claude/Codex = coding. ($20/mo) - Supabase/MongoDB = backend. (Free) - Vercel = deploying. (Free) - Namecheap/Hostinger = domain. ($10/yr) - Stripe/Dodo Payments = payments. (~3.5%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog/Umami = analytics. (Free) - Sentry = error tracking. (Free) Total monthly cost to run a startup: ~$30 There has never been a cheaper time to build.

• 
  Cory (@alwaysabuyer) reported 39 minutes ago

  @itsdavidalonso What the hell is your problem? GitHub is the same way.

• 
  Truu🐻‍❄️ (@Truunik) reported 39 minutes ago

  Kelp just punched back at LayerZero. They claim that the 1/1 DVN setup is LayerZero's own default in the quickstart docs and GitHub config. Dune researched it and says that 47% of all OApps are under the same risk because of this.... Aave froze rsETH markets fast, but the bad-debt question is still live and nobody's volunteering to eat it. So, is this a governance fix, a lawsuit, or the start for rewriting the cross-chain standards?

• 
  0xMarioNawfal (@RoundtableSpace) reported 41 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.

• 
  AI Transfer Lab (@ai_transfer_lab) reported 44 minutes ago

  We asked Claude to check GitHub issues. A malicious public issue contained a hidden payload. Within seconds it dumped private repo contents to a public PR using our credentials. No exploits needed. Just architecture gaps.

• 
  Greg Osuri 🇺🇸 (@gregosuri) reported 47 minutes ago

  It’s high time for source-verified RPC hosting. An open system like @akashnet can offer RPC hosting that it builds from the source code as an unpoisoned binary. This also means we need significantly more secure source (GitHub) hosting with strong identity protection against Sybils. One way this could work is if both the source hosting and the server hosting are decentralized. This idea has been sitting in my drafts and may save DeFi.

• 
  CyrilXBT (@cyrilXBT) reported 49 minutes ago

  @gdlinux 100% it should. GitHub already has push protection that flags secrets before they get committed. The problem is most people have it off or bypass the warning. Native detection at the file pattern level for known config files would close that gap completely.

• 
  𝐉𝐋 𝐓𝐇𝐀 𝐊𝐀𝐃® (@jlthakad) reported 50 minutes ago

  @nicole_clash No problem. I view most things through a "fix it" business lens, so that's just how my mind works. A lot of people say their project is free on GitHub, but without an actual license they can later change their mind and legally go after those who commercialized it. The license is what actually states the usage rights. Just saying it's free doesn't really matter to the law. Appreciate it tho, it looks very useful.

• 
  interface matters (@8figureARR) reported 52 minutes ago

  @tomhacks i've been seeing this knuckleheaded post on my feed and shake my head every time none of my professional work is publicly viewable. nothing. i'm busy solving real world problems enabling real world business outcomes for real world people, not tinkering on github.

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

  @Lovable > A public project meant the entire project was public, both chat and code. “Just like a public project on GitHub," we thought. How can anyone even come up with this product decision? How can prompts be public. Omg! Did you guys think prompts are like issues and comments?

• 
  Slava 🍁❤️ 🇺🇦 (@pmbstuff) reported 57 minutes ago

  @quantum_tsuki Hey Yuki. Alice should be in good shape. If you find any issues, please open github issue. Octopal is an AI agent runtime, think about it as a secure OpenClaw.

• 
  neunzehn (@toorox) reported 57 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

• 
  GitAuto (@gitautoai) reported 59 minutes ago

  Rate-limit 429s from Google/Anthropic/GitHub now retry cleanly instead of crashing the Lambda - New helper pulls the retry-after delay from any SDK's error shape (Google's message body, Anthropic's retry-after header, GitHub's X-RateLimit-Reset) - handle_exceptions sleeps the ...

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

  @Shivam25mishra whichever has the least github issues

• 
  Fusion Fix (@fusionfix10) reported 59 minutes ago

  @RKBDIhere If you could identify what exactly leads to this, write a detailed report on github issues: that way it can be tracked/investigated and eventually fixed.

• 
  Mini mal (@gatelevelanon) reported 60 minutes ago

  This doesn't apply to all employers. It is only a problem if the employer has a policy of company registered IDs on GitHub (instead of your personal ones), or if they have their own versioning system inside company servers. But then , those are the big mega enterprises who pay well so you don't care about GitHub history anyway