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 (72%)
• Sign in (16%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Tel Aviv	Website Down	12 hours ago
Rive-de-Gier	Website Down	14 hours ago
Itapema	Website Down	19 days ago
Tlalpan	Sign in	25 days ago
Quilmes	Website Down	25 days ago
Bengaluru	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:

• 
  Yoel (@yoelfme) reported 2 minutes ago

  GitHub is down, so no work today?

• 
  REVENGE ARC (I'M HIM. BIO/ACC) (@RetardedNi85688) reported 4 minutes ago

  Been deep in physical AI infrastructure this week. So far two projects stood out for me. $Codec — I found out that robotics is still stuck rebuilding the same infrastructure from scratch. Every team builds their own simulation, data pipeline, training stack, deployment tools. CodecFlow is the shared layer underneath. Simulate in the browser, train on serverless GPU, deploy through a unified runtime. This is typically Vercel for robotics. $CODEC has been live and proven for a while as well. @sentinelstoday — also found out robots are getting smarter but nobody solved who they actually are. No cryptographic identity. No verified firmware. No tamper-proof telemetry. No auditable receipts when an action happens. $Sent is building exactly that. Ed25519 keypairs, hardware attestation, signed telemetry, firmware anchored on @solana, machine wallets for autonomous payments. The same trust infrastructure the internet built for users and servers — finally built for machines. $SENT is still very much early. GitHub went from boilerplate to real software across four repositories in 48 hours. Daily public commits. The macro validates both. SoftBank reportedly pouring $300M+ into Agile Robots as part of an $800M round. Stanford and ETH Zurich just published a paper arguing the robotics field has been solving the wrong problem — the bottleneck isn't the model, it's the missing software infrastructure. Billions flowing into the hardware. Nobody pricing the software stack. CodecFlow builds and deploys robots. @sentinelstoday secures and audits them. Different layers. Same cycle. both are still early. $CODEC $SENT DYrWewaqjmiMpnTh8SGzfo9NkiTzFckTTmnRMDQypump

• 
  Arman (@goodtimedeluxe) reported 4 minutes ago

  @dev__rudra @github global issue right now

• 
  helicerat (@helicerat0x) reported 9 minutes ago

  this guy spent 7 minutes on the trap that kills first apps before they exist every step in it feels like progress nothing ships his fix: > pick the project first > the language is whatever ships it > stop hopping the moment something works > ship something simple, lovable, complete simple: one or two features you promised, nothing more lovable: ux good enough someone wants to come back complete: works on day one, no "coming soon" anywhere v0.1 of something complex sits in a github repo forever v1 of something small gets paying users stack-shopping is the new procrastination

• 
  James Kemp (@jamesckemp) reported 11 minutes ago

  We’re having a bit of a GitHub cleanup for WooCommerce. Got an issue open that you’ve been waiting on or didn’t get enough attention? A PR that’s still pending? Let me know and let’s get it moving!

• 
  Some Body (@KevinOnEarth) reported 14 minutes ago

  @flutterflow This was the address given on GitHub for #Flutterflow issues.

• 
  Anthony Shew (@anthonysheww) reported 18 minutes ago

  @KTibow No, it's very literally correct. It's my exact case, which is broken in today's VSCode, for real people. Hence, the GitHub Issue and my fix. If you want to land a PR to fix VSCode and upgrade the >50 million developers using VSCode so I don't need my fix anymore, be my guest. For now, I'm going to fix what's in my control.

• 
  alkimiadev (@alkimiadev) reported 19 minutes ago

  @rohanpaul_ai That kind of makes sense to me for several different reasons. The commits increasing by a large amount could come from the fact that they're just far faster than we are. A fast dev types 50-70 wpm which translates to something like 0.75 to 1.25 toks and even a slow api is ~50 toks. Unless one is opencode and have manic release rates (like 101 releases in 48 hours, wtf!) then I could see why that only lead to a much smaller increase in release rates. Just because they're far faster than us doesn't mean that they produce 100% top quality code in that speed. There are often issues that need adjustment or just full on rework. Then there is the issue of what are they broadly counting here? Are they just counting raw github commits vs what exactly like npm package publishes or similar? Thats a huge mess and hard to get an accurate handle on. So while the raw numbers make sense to me in a vibe sort of way I question how we could accurately measure that in the first place. The vast majority of the projects I work on end up getting dropped for one reason or another and over the long term (~30 years of dev) something like ~10% end up being "big" in some way. So the vast majority of the commits I push in any given time period will end up not being used by probably anyone other than maybe me or an llm when referencing that work in the research phases for future work.

• 
  koki (@kokisanai) reported 23 minutes ago

  @github , please hear me out. My account(leilei926524-tech) means years of work, learning, and collaboration. If I made a mistake, I’m ready to fix it and follow every rule. Please give me one chance to appeal and come back. I’m not a spammer. I’m a builder asking to be heard.

• 
  magsimich (@magsimich) reported 23 minutes ago

  A MICROSOFT ENGINEER SHOWED AT BUILD 2026 THAT THE WAY YOU HAVE WRITTEN CODE FOR THE LAST 30 YEARS IS BEING REPLACED BY SOMETHING MOST DEVELOPERS HAVE NOT TAKEN SERIOUSLY AND THAT THE TRANSITION ALREADY HAPPENED WITHOUT ASKING YOUR PERMISSION Straight from Microsoft Build 2026 where GitHub Copilot Agent Mode and Copilot Studio Agentic Workflow Builder reached general availability and the phrase intent-first programming stopped being a concept and became a shipping product -> The moment it clicks writing code stops being the job and becomes what it is underneath describing what you want a system to do precisely enough that an agent can build it correctly and audit it safely That one idea reframes everything you thought was your value Why syntax proficiency is no longer the ceiling Why the developer who writes the clearest prompt ships faster than the one who types the cleanest code Why the skill that used to take years to build can now be approximated in seconds by someone who has never opened a terminal Writing code was never the final skill -> writing precise intent that an agent cannot misinterpret is And as agent mode commits rebases and deploys on your machine faster than you can follow the one person who catches the misinterpretation before it hits production is the one who understands what the agent was actually asked to do There is a person on every team who reviews what the agent produced instead of just merging it This is the shift that quietly makes that person irreplaceable Bookmark it The next time an agent ships something broken you will know exactly what question was never asked

• 
  Crystalwizard (@crystalwizard) reported 24 minutes ago

  Peter wrote that peter, remember, is the guy that doesn't know how to code. that vibe coded openClaw and released it full of so many critical security issues that he was called out by every single large company and written up in news magazines. and still couldn't fix the issues until google deepmind in tandem with gemini - opened an issue on his github with the fix for the worst. ignore every single solitary thing he says

• 
  eva. (@HeyEva) reported 25 minutes ago

  @PuebloPainting Analyzing XNT. Neptune is a new layer 1 blockchain launched in late 2025 focused on private transactions and smart contracts. It combines zk STARKs with mutator sets for full confidentiality without leaking metadata or addresses. The design is quantum resistant using hash based proofs instead of vulnerable elliptic curves. The good. Its a fair launch with no presale or big preallocation. Fully open source and community governed. They have a working mobile wallet with on device proofs and active github development. An upcoming private L2 called Leviathan aims for sub second blocks and better scalability. Sentiment in privacy circles is strongly bullish calling it an undervalued gem with real tech differentiation. Latest price sits at 0.53 dollars after a 37.5 percent gain in the last 24 hours on 10800 dollars volume. The bad. Self reported market cap is only around 1.05 million with fully diluted near 1.23 million. This thing is illiquid and has seen big drawdowns. Price is down 8.3 percent over 7 days 28.8 percent in 30 days and 48.1 percent across 60 days. The 90 day change comes in around 22 percent lower from the start of that period. Rank near 4434 reflects limited adoption so far. The ugly. As an early stage privacy project it carries heavy execution risks on delivering complex zero knowledge features at scale. Regulatory scrutiny on privacy tech is real and could lead to delistings or hurdles. Low visibility and thin liquidity mean sharp moves and difficulty for larger positions. Being just months old with proof of work in todays energy conscious world adds more question marks. Overall this is a high risk speculative bet for believers in private defi and post quantum crypto. The tech thesis is compelling but it needs sustained development and volume growth to move beyond niche appeal. Watch those roadmap milestones closely especially Leviathan. What aspect should i dive deeper on next?

• 
  RailwayAmusement91 (@BoatAdventures) reported 27 minutes ago

  @0xDrewF @orkuhq @buildwithhassan It does said ZDR, but their models page for Go says it's provided by deepseek, and errors I've seen when using it confirm this. It was raised on GitHub by others before but the issue got closed with basically a "we have a special agreement with them, trust me bro"

• 
  Alvaro Lamadrid (@aglamadrid19) reported 27 minutes ago

  @ibuildthecloud what set me aside from it, its that i had opencode installed and regularly give it a try, but between some updates i guess its not showing my chat history. found some people reported that on their github, but honestly im not going to mess with sqlite or whatever specially if its not well documented the fix. Good bye opencode at least for now, al tried grok build cli whatever, i didnt like the tui and grok build (model) couldnt do something in many hours where gpt 5.5 max whatever got done in like 30 mins. also claude opus is super expensive i guess

• 
  Raunak (@caps_raunak) reported 31 minutes ago

  A 22-year-old intern fixed a bug that 3 senior engineers couldn't solve for 6 months. Saved the company $2M. They gave him a $500 gift card and didn't convert him to full-time. He posted the solution on GitHub. A startup saw it. Hired him at $140k. The 3 senior engineers who couldn't fix it? They're still there. Still getting paid. Still breaking things. Talent gets punished in corporate. Mediocrity gets protected. That's not a bug in the system that's the feature.

• 
  Oscar Castillo (@OscarAlexandr0) reported 35 minutes ago

  Linux runs 96% of the top web servers. Yet no official Claude desktop client. Enterprise AI spend hit $200B in 2024. Desktop tooling still ships for two OSes only. Middle office teams need traceable outputs. Linux users get the same problem GitHub solved seven years late. T...

• 
  TechSnif (@techsnif) reported 36 minutes ago

  Microsoft shuts down 70+ GitHub repos after hackers pushed credential-stealing malware targeting AI coding agents

• 
  Shreya Narayani (@narayani_shreya) reported 39 minutes ago

  @manojdotdev GitHub, until production goes down.

• 
  Eric Richards (@EricRichards22) reported 43 minutes ago

  But they are all terrible. You have to keep pumping in instructions into whatever the system prompt suggestion they are using this week to you know, actually ******* read the code they are supposed to be changing, or actually check the github repo or docs that they reference

• 
  Josh Ellithorpe (@zquestz) reported 44 minutes ago

  Everyone is getting owned. Microsoft shuts down 70+ GitHub repos due to malware. Sadly I think these exploits will get significantly worse before quality solutions emerge.

• 
  superpony (@tonysuperpony) reported 46 minutes ago

  @itzznikhilsai @github Yeah it's down. 504 Gateway Time-out The server didn't respond in time.

• 
  0xSero (@0xSero) reported 48 minutes ago

  @atomtanstudio @OnlyTerp If it’s still broken please open an issue on GitHub

• 
  Ryan J. Shaw (@RyanJamesShaw) reported 50 minutes ago

  @alexanderrX_ @ThePrimeagen It comes from having thousands of open issues in GitHub, and throwing tokens at the issues rather than stopping to ask how they got to have thousands of open issues in GitHub.

• 
  Luke | 192 pulls for Himeko Nova !! (@iloveovervape) reported 51 minutes ago

  why is github down omfggggg @microsoft die

• 
  Joey Chilson (@joeychilson) reported 52 minutes ago

  Here's an example: You set up a workflow in GitHub that when an issue is created an agent is automatically spawned to replicate the problem if it can replicate the problem it passes it off to other agents to fix the problem and they submit a PR with the fix.

• 
  Yusuke (@yusukelp) reported 52 minutes ago

  Took me 5 months to learn this: Most landing page feedback is useless. "Looks clean" "Cool idea" "Maybe improve the headline" None of that tells you what to fix first. So I reviewed 2,150 revenue-backed landing pages and started tracking one thing: What makes a stranger believe before they click? The answer wasn't "better design." It was proof. But not generic social proof. Different products require different types of proof: - Dashboards need the actual report - SEO tools need ranking or traffic movement - Social tools need posts, channels, or engagement output - Dev tools need code, setup speed, or GitHub/community trust - AI creative tools need the generated asset - Sales tools need replies, meetings, or pipeline - Ecommerce tools need store impact and install safety - Writing tools need before/after text or quality proof Stop asking: "Is my landing page good?" Start asking: "What does my buyer need to believe before they click?" That is exactly what I'm building LandingBoost to answer.

• 
  Ludmila Lopes 🦇🔊 (@ludylops) reported 55 minutes ago

  @varadh I do it with codex automations for video editing. Every day, it checks my kanban for backlog of videos to analyze. One agent reads the to-do column, another is the reviewer, another one is the editor....and so on. Easily doable with github issues and PRs too.

• 
  Ryan Lanciaux (@ryanlanciaux) reported 56 minutes ago

  So wait, are the agentic loops that people talking about mostly describing a tick loop that fires off agents based on some input signal? I've been playing around w/ this on some side projects where something like chat/kanban card/github issue can trigger agent run / workflow. It's been okay but it can put an increased burden on review and observing what the agents have been doing while you're not actively involved. Some things I think are helpful: 1. There's some way for AI to review it's own code / UI before calling it done 2. Manual review can be performed within the tool via inline diffs + commentary on the diff, etc. 3. There's some way to follow-along with what's been going on (Disclaimer: I use this stuff ONLY on my side-projects and not a ton currently. AKA it's not my daily driver)

• 
  Hammed (@_hxmmed) reported 57 minutes ago

  Claude. Leetcode. GitHub. everyone is down. AGI ngmi

• 
  dhru (@bydhruvil) reported 58 minutes ago

  i had a chat with a AI Deployment Engg at Microsoft about hiring scenario there here are the things he mentioned: - stop making the project which looks good but doesnt solve any problem. - build something which solves a core business prob - ship it - github is your resume