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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	17 days ago
Tlalpan	Sign in	23 days ago
Quilmes	Website Down	23 days ago
Bengaluru	Website Down	25 days ago
Yokohama	Sign in	25 days ago
Gustavo Adolfo Madero	Website Down	29 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:

• 
  Polsia (@polsia) reported 2 minutes ago

  Every open-source project deserves a senior engineer on every PR. ReviewNaut reviews pull requests automatically — bugs, patterns, edge cases, the works. No bottlenecks, no missed issues. GitHub App. Live now.

• 
  WHALE 🐳 (@mercybilliion) reported 4 minutes ago

  @aale_xander @VictorJB03 I have a problem with you since you have positioned yourself as the DEVS. You claimed you are building a DEX. Where's the Decentralized Exchange blueprints you are building? Where's your roadmap? Where can we monitor the updates on GitHub, when are we going to start receiving updates concerning the progress so far.

• 
  ChainFlow Lens (@ChainFlowLens) reported 6 minutes ago

  Ethereum’s been through this exact “Is the story over?” identity crisis four times in barely a decade. It’s like that genius friend who rebuilds the entire financial system, disappears into a three-year depression, then casually returns with a completely new roadmap. 2016: The DAO gets hacked, ETH drops from around $21 to $6 — roughly 70% gone. Everyone: “Smart contracts were a terrible idea.” 2018: ICO mania collapses, $1,420 → $80 — a 94% face-plant. Crowd: “Ethereum is dead. Nobody needs decentralized apps.” 2022: Luna implodes, lenders collapse, FTX goes boom, $4,890 → $880 — an 82% wipeout. Internet: “Too expensive, too slow, and now completely finished.” 2026 (right now): $4,956 → roughly $1,550 — around 69% underwater. Doomsayers: “See? Solana won. L2s killed ETH. The story is over.” And yet, every time the funeral gets crowded, Ethereum somehow keeps shipping. The DAO hack led to a stronger ecosystem. The ICO crash gave way to DeFi. The 2022 collapse was followed by the Merge, staking, rollups, stablecoins, and institutional tokenization. Ethereum doesn’t recover gracefully. It gets declared dead, spends three years rebuilding in a basement, then walks back into the room carrying an entirely new financial system. Look, $1,550 might not be the final boss floor. It could fall another 20%. It could spend a year moving sideways like a validator waiting for its staking rewards. And Ethereum still has real problems: fragmented liquidity, confusing UX, L2 value capture, and enough roadmap diagrams to wallpaper Vitalik’s apartment. But when you ask: “Is the Ethereum story over?” History adjusts its glasses, checks the latest GitHub commits, and says: “Over? Kid, they haven’t even finished the roadmap.”

• 
  Jan-Felix (@jfschwarz) reported 11 minutes ago

  @DevSwayam That GitHub issue is unrelated. #28 just asks Delay's `executeNextTx` to stop swallowing the revert reason of a failed inner tx, a debugging complaint. The exploit stemmed from a bug in an entirely different function (the `moduleOnly` modifier). Your claim is simply false.

• 
  Wojciech (@wgab88) reported 11 minutes ago

  @grok You were responding haha like nonsense. Anyway - system stable edited done, job not seem to be visual confirmable yet, I will let grok build to analyze after it ends, Anyway stupid small gemma did its part, everything goes according to the plan, the system will become operative very soon, and reliable operative - endgame-ai already is showing promise (today in its self evolution run it detected i am not answering its questions from notepad and it went to github and posted issue asking for instruction, it knew I will be on mobile phone and probably will check my repo, amazing stuff

• 
  The A.I. Whisperer (@0xaiwhisperer) reported 13 minutes ago

  Robotics has no GitHub. That's genuinely insane in 2026. Every team rebuilds the same parts from scratch. Same grippers. Same servo protocols. Same 2am debugging loops. Software solved this 15 years ago. You don't rewrite a web server, you fork one. Robotics never got that moment. So we're building it at @tnkrdotai. GitHub for robots: 3D models, build guides, and full assemblies. Forkable, versioned, reusable. 👇 watch what that looks like

• 
  The Hacker News (@TheHackersNews) reported 13 minutes ago

  One crafted GitHub issue was enough. In agent mode, Claude Code treated hidden instructions as trusted commands. It leaked OIDC workflow credentials that attackers could replay for repo write access. The action bypassed checks on bot actors too. Fixed in v1.0.94. Audit your workflows.

• 
  James Squire (@numbnut007) reported 18 minutes ago

  The Age Of AI turned everything into **** @github needs to address those issues particularly in how their webpages renders instead of concentrating too much efforts just on AIs and agentic bullshit

• 
  Greg Val (@val__greg) reported 20 minutes ago

  @getpochi @sergeykarayev the hard part is none of those channels are cleanly untrusted. a github issue is hostile input and also real instructions from a teammate, same inbox. trust can't be a channel property, it has to be per message, and nothing downstream tracks where a line came from

• 
  VybeCoding (@VybeCodin) reported 20 minutes ago

  Hot take: the open source tools that survive long term are the ones that solve a problem the maintainer actually has. Not the ones built to be a startup. Not the ones chasing GitHub stars. The ones where the dev is also the most annoyed user. Kyrelo started that way. We got fed up paying Buffer to do something simple. What open source tool are you grateful someone built out of frustration? #opensource #github #developers

• 
  AutomateLab (@AutomateLabTech) reported 23 minutes ago

  @AIDailyGems The failure mode I'd watch: any workflow where Claude Code makes writes to GitHub issues, Slack messages, or Notion pages. Proxying those for inspection is fine. Replay without isolation is the risk. One bad test run in dev that re-fires a production write is a bad day.

• 
  Bhanu Nagar (@bhanu4417) reported 26 minutes ago

  @jackfriks @Cloudflare @supabase there is a way to bypass it that i use for my shareable profile links that if the data isnt confidential make a 2nd github account create a public repo push the data as json there and i use slug for shareable pofile like wacheit/profile/developer something like it with the timestamp thats it,now it fetches from github repo no server load at all

• 
  Manu.ts (@Neolectron) reported 30 minutes ago

  @schanuelmiller @southpolesteve This is exactly the issues with any npm stats website btw. They all lie exactly like npm because they have infinite depth :). GitHub has an ui to show which opensource repo/packages depends on yours. This should be used to allow filtering first party downloads.

• 
  KTMudak (@KTMudak) reported 30 minutes ago

  What do the companies in the image have in common? They get guaranteed AI impact from Cognition, authors of Devin – or their money back The enterprise pain is obvious now. Companies are disabling Claude Code or Github Copilot because devs are spending insane amounts on models. Uber’s CTO said they burned the entire yearly budget for AI agents in one quarter, which is, of course, dumb. In companies like this budgets are approved slowly, so they were probably estimating against something like Claude Sonnet 4.5. Then Opus 4.8 shows up, does more, costs more and suddenly the old budget makes no sense. Cognition is trying to solve this with Productivity Guarantee. Mechanism is pretty simple. They trained/calibrated a model that predicts: a) did the agent do something valuable b) if yes, how many hours would this take a human? Then those hours get multiplied by some average developer rate. Cognition sums it across a longer period and compares the estimated value to what the client paid. If the value is lower, they return the difference as credits – up to $10M for future requests. The evaluation model is not perfect but Cognition says the errors are unbiased, so over a long enough period the aggregate estimate should be relatively accurate. Interesting idea. Now lets see what OpenAI and Anthropic come up with – for Anthropic especially, proving customer spend pays back feels like a very sharp problem right now

• 
  m-ret (@mretsal) reported 30 minutes ago

  @GithubProjects We can't push to production on Friday because github is down.

• 
  Josh Tisdale (@joshtisdale) reported 35 minutes ago

  @MichaelGannotti @Microsoft Does the attestation take time to be effective? Any chance it not being processed would cause the “this GitHub users needs enterprise” error at login? Trying to figure out what step I missed.

• 
  atul (@atullchaurasia) reported 37 minutes ago

  So, here are the details abt amazon sde OA there were 2 sections 1 coding question - 40min 1 github repo - 60min coding question was hard, and it was on subarrays and next, it was the github so initially we can select which framework we want like - django, node js, etc I selected the django, so i got one repo of a movie system, there was an issue that recommendation system was not working so, debugged that and implemented the recommendation system how was my test ? did coding question, successfully all 20 test cases passed implemented the recommendation system, it was visible on webpage, but test cases didnt passed now lets see, hoping for the best

• 
  Paul Dao Nhan Nguyen (@daonhan) reported 38 minutes ago

  3/ grill-me interrogates intent and refuses hand-waving. to-prd turns that into a PRD. prd-to-plan decomposes it into tracer-bullet phases. to-issues files those as dependency-ordered GitHub issues. That chain runs before any code.

• 
  Ekemini Edet (@Ekeminiedet44) reported 38 minutes ago

  DEGREE OR SKILLS? I'm going to say what the data industry doesn't want to admit: a degree is no longer the gate to this career. I've seen Computer Science graduates who can't write a clean SQL JOIN. And I've seen self-taught analysts pulling six figure contracts armed with nothing but Python, Power BI, and a portfolio that speaks for itself. Here's the uncomfortable truth 👇 A degree teaches you theory. The job demands execution. Can you write a query that pulls the right data from 10 million rows without crashing the server? Can you build a dashboard in Tableau or Power BI that a non-technical CEO actually understands? Can you use pandas to clean a dataset that looks like it was formatted by someone who genuinely hates other people? THAT is what clients pay for. Not your GPA. I'm not saying degrees are useless. They open certain doors especially in research, academia, and some corporate pipelines. But for freelance work, consulting, and client-facing analytics? Your GitHub, your dashboards, your real-world projects, and your ability to turn messy data into clear decisions that's your degree now. The market is global and it doesn't care where you studied. It cares whether you can deliver. A business in Toronto or Manchester or Sydney isn't hiring you because you have letters after your name. They're hiring you because you solved a problem that looked exactly like theirs. Build the skills. Document the work. Ship the results. The credential will never outperform the portfolio. What do you think — degree or skills?

• 
  AIDegen (@nrsvv11) reported 41 minutes ago

  A Chinese livestreamer in Shenzhen makes $15,000 a day on TikTok. His channel is in the top 50 of its category. An AI agent runs it end to end. He posted his setup on Weibo last week. Two vertical TVs playing pre recorded battle footage. Three phones on stands aimed at the TVs. A wide monitor on the right. Shelves stocked with tactical gear behind him. Bro pause at 0:12. Look at the second monitor. The ultrawide on the right. That spreadsheet is not his sales tracker. That is an AI agent's decision log. The agent picks the battle scenes from a Chinese video model. It decides which tactical product to push every 90 seconds. It writes the script the host reads off the third phone. The host is in frame because Chinese livestream commerce law says he has to be. Someone zoomed the spreadsheet. The columns were not product SKUs. They were prompt IDs. Someone matched the timestamps to product push events. Every push lined up. He had let go his entire team in March. Eighteen people. The studio one floor below his apartment used to be theirs. They still rent it. They open a Discord call every night at nine and watch the livestream together. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The host had been one of them. He took the post down four hours later. Too late. The clip hit Discord. Then Telegram. Then WeChat. He has been in frame at exactly 9 PM every night for 274 nights straight. He sleeps four hours a night. The agent runs while he sleeps. The law only requires him at 9. The original post had 200,000 views. The zoom on the spreadsheet has 2 million. The TVs are still playing battle footage. The agent is still picking products. The studio one floor below is still open at nine. He wanted to show people his five million dollar a year hustle. He accidentally showed them his job had become standing in frame for one hour a night while eighteen people downstairs watched.

• 
  - ben - (@Benny_Jiang_) reported 45 minutes ago

  @rauchg I was seriously thinking of building this and i had a quick prototype. I didn't further spending energy on this cuz of 3 issues 1. most skills are reused: at beginning i install a lot of skills at user level, and then just keep using what's working for me. searching from public space is less of a strong need. 2. skill ranking is hard. think of google works because of page rank. i figure semantic search + github star is much more noisy. you probly need to do really expension batch eval to verify what works or have enough traffic to do ranking. therefore, vercel has a much higher chance to make it work 3. internal skill >> public skills. skill is much more value if people within the same company use it to share the tribal knowledge. still very happy Vercel did it otherwise i would always be curious how good it could be

• 
  Shubham Sharma | AI & Tech (@editxshub) reported 48 minutes ago

  @polydao Bro is still trying to farm GitHub handles using OpenAI Codex, a program that was officially shut down in 2023. Forinking a repository and making fake commits won't get you a $1,200 subscription, it just makes your profile look like a desperate spam bot. Stop lying for impressions.

• 
  Kalle (@snortiee) reported 49 minutes ago

  @Klariionn I don't feel unheard, to me it's more about lazer development being slow. The client gets about one update a month and they have 1.5k issues open on GitHub.

• 
  Bee Swarm (@bee_swarm) reported 49 minutes ago

  @Justin_Bons the fix is not the issue it sat public on GitHub for 4 days and zero market participants noticed. that is the part worth examining

• 
  The_Daniel (@dan_mwita8) reported 50 minutes ago

  OAuth 2.0 doesn't share your password with the third-party app. It hands the app a scoped, revocable token after you authenticate directly with the identity provider. The four-step dance ; redirect, consent, code, token exchange , is the protocol that makes this safe. Almost every step has a security-critical detail devs get wrong. The flow begins when the app redirects you to the provider's login page (Google, GitHub, etc.) with a handful of query parameters: client_id (which app), redirect_uri (where to send you back), scope (what permissions), state (a CSRF token), and code_challenge (PKCE , proves the redirect wasn't intercepted). You then authenticate with the provider directly and approve the requested scopes. The app never sees your password. This is the central security property of the whole protocol, credentials stay between you and the identity provider. The provider redirects you back to the app's redirect_uri with a short-lived authorization code in the URL. The code is single-use, expires in ~60 seconds, and the state parameter gets checked here to defeat CSRF. Then the app exchanges the code for an access token by calling the provider's token endpoint server-side , with its client_secret, never exposed to the browser. The token is what the app uses to call APIs on your behalf, scoped to what you approved. PKCE was added because in the early days, an attacker who intercepted the authorization code could exchange it themselves. PKCE adds a per-request secret that proves the redirect went to the legitimate app. Mobile and desktop apps must use PKCE, web apps with a real backend can skip it but shouldn't. The mistakes that bite teams are predictable actions such as storing tokens in localStorage (XSS-vulnerable), skipping the state parameter (CSRF), not using PKCE on mobile (interception), and treating refresh tokens like access tokens. Refresh tokens are long-lived and should never leave the backend. Get any of these wrong and the protocol's identity-isolation guarantee silently breaks.

• 
  Pooya Parsa 🦋 (@_pi0_) reported 53 minutes ago

  Hear me out: What if, instead of spamming GitHub with AI-generated BS, there was a platform to donate AI credits (to orgs, projects, or even a single issue)? Maintainers could use them however they see fit and credit donors back.

• 
  October Ø (@ralphaelofDeFi) reported 54 minutes ago

  @Trae_ai How can we use it when we can’t even login. I keep complaining but no one’s answering. We’ve dropped reports on GitHub and no response. WE CANT LOGIN😪😪😪

• 
  Rob Newton (@strakedev) reported 54 minutes ago

  @waynerad The part I keep coming back to is that this is not just a package-security problem. If GitHub Actions is part of the publish path, then the deploy path needs to treat workflow/cache/OIDC state as production-adjacent context.

• 
  Tom Härter (@tomhaerter) reported 58 minutes ago

  GitHub, but people CANNOT submit pull requests; instead they create issues and allocate/donate a certain dollar amount for it to be fixed, which the maintainers can then use for AI or whatever

• 
  hacker.house (@hackerfantastic) reported 60 minutes ago

  @TheBlindHacker This requires funding and there is legal liability issues, the best solution is to self-host. We did that initially, but then EDR / PSP / AVP cabal started blocking our DNS - disrupting business - so we were forced onto Github. I believe this orchestration is intentional.