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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

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

• 
  LayerLens (@layerlens_ai) reported 1 minute ago

  stratix-python just crossed 120 stars and 70 forks on GitHub. Thank you to every developer who starred, forked, opened an issue, or submitted a PR. ⭐ 120 stars 🍴 70 forks 👥 5 contributors 🏢 60 org followers Every star is a signal. Every fork is a team that decided evaluation matters. What started as an SDK for running LLM evaluations is becoming the open-source backbone for teams that refuse to ship untested AI. The roadmap is public. The harness is open. The judges are live.

• 
  Decoded Daily (@decodeddaily07) reported 1 minute ago

  @adithya_s_k Translated for normal humans: They're saying: a new tool turns any github repo into a self-contained sandbox where you can test if an AI coding agent actually solved a bug or task. one pip install. Works because: real PRs come with tests and expected outcomes. wrapping the repo + tests + verifier into one environment means did the agent fix this becomes a checkable answer instead of a vibe. What didn't change: someone still has to pick which repos and PRs to test against. and passing the tests isnt the same as correct code, same as for humans.

• 
  Guan Jiawei (@skyguan122465) reported 2 minutes ago

  Spent 4 hours watching Claude Code fail to fix its own Chrome extension, sure that 'a restart will fix it.' It never did. Told it to search; a stranger's GitHub issue fixed it in 15 min. AI doesn't cut failures, it makes you fail faster. Today's dead end is next month's pass.

• 
  Frogtech (@frogtechbrah) reported 2 minutes ago

  @github Check real time to make sure nobody is on the page I am about to edit on the server.

• 
  Abishkar Dhenga (@Abishkardhenga) reported 4 minutes ago

  @sujansince2003 hahah same problem delete node modules and delete all the project keep the project u working . other side project delete keep on github . clone when needed

• 
  Vinz (@hivinz_) reported 4 minutes ago

  @linear Having PR reviews live inside Linear is the missing piece — context switching between GitHub and your issue tracker kills flow. Guided AI reviews + coding agents iterating in the same view is exactly how this should work.

• 
  Hiroshi Aria ありあひろし (@AriaHiro64) reported 4 minutes ago

  @github is so stupid i had to dmca myself today because copilot ****** my login a while ai before they had opt out consent, because its opt out i was forced to dmca myself. i wish i was making this up.

• 
  Rithvik (@OutlierInMaking) reported 9 minutes ago

  @arvind_xdd @toeknee_kim only if a huge swarm of techies upload on spaces like github. Why you may ask, its because whoop regularly takes down posts which show reverse engineering researches. See it is pretty simple, whoop is just a 3-4$ sensor. i dont want to tell more cuz of whoop lawyers and policy-dm

• 
  Mikers (@mseiler1) reported 10 minutes ago

  @JustinBleuel @ChatGPTapp I'm using codex for github code reviews and a) my usage dashboard is broken. it lists 0 but it's definitely the only thing currently draining this account. b) for they're not very good - generally they find nothing and coderabbit and copilot finds lots of issues c) it uses quota pretty aggressively and doesn't seem worthwhile

• 
  ***** Marucci Blas (@guidomb) reported 15 minutes ago

  I write down the plan in to spec.md file (that's gitignored) and/or also save it as a GitHub issue for other team members to comment on. I am now also sometimes committing the plan or a version of the plan focused on the design decisions ...

• 
  Naya (@bossnayamoss) reported 15 minutes ago

  @SymoneBeez Yesterday I used Codex to build a crazy amount of features across 7 apps. After each GitHub issue was done, a computer use QA agent tested the app like a real user w/ service accounts before moving to the next task. All while I was at Trader Joe’s. All I did was share my vision

• 
  タロウ🇳🇿オークランド大学生&ウェブ開発者 (@taroj1205) reported 18 minutes ago

  only if they're configurable cuz I accidentally merged pr trying to create a new chat from a GitHub issue

• 
  Moe (@katibmoe) reported 20 minutes ago

  > An integration provider just got hacked. > by someone who used them to break into them. > 5,001 GitHub tokens, 5,200+ API keys, gone in under 8 hours. > they couldn't scope which connections were compromised. > and revoked every user's GitHub tokens, even though only 0.3% were affected. i've been building in this space for 12 years. This is disappointing. your integration layer is the single most important piece of software in an AI agent stack. when it stops, every agent stops. every workflow, every customer touchpoint, every revenue motion goes dark in the same minute. worse, this is an architecture problem. dozens of AI-native companies whose product can't function without their integration layer were blackholed at once. same reason: shared infrastructure, unscoped credentials, one blast radius across the whole customer base. if you've been affected by this, or you're rethinking your integration layer, I would love for you to take a look at @withoneai every customer's credentials live in their own scoped environment. a breach on one tenant cannot cross into another. internal tools cannot register actions inside customer sandboxes. if your team is still scrambling: DM me. we'll set you up on One free for 90 days and personally help you migrate every connection you lost. engineers to engineers, today.

• 
  Strata (@ChainZenit) reported 21 minutes ago

  every second dev is building a "skill" or "agent" right now. 1,000 GitHub stars in 48 hours for a single HTML file. the agent gold rush is real. but here's what nobody's talking about: the lifespan of a skill is the lifespan of a model update. Opus 4.8 just dropped. half the "skills" people shipped last week are already broken or redundant. we're not building software anymore. we're building wrappers that expire on Anthropic's release schedule. the real moat isn't the skill. it's knowing which problems survive the next API call. you can't version-control trust.

• 
  Abhishek Sharma (@Abhishe04755332) reported 24 minutes ago

  My Go API was firing webhooks to external services. Anyone who knew the URL could send fake events. The receiver had no way to verify: "Did this actually come from my server?" GitHub, Stripe, Twilio all solve this the same way: HMAC signing. Here's how I added it 🧵

• 
  gaurav (@Itstheanurag) reported 27 minutes ago

  @venkateshdotdev Bro GitHub is down every week, everyone I know hates it. It's just there's no alternatives.

• 
  Prityush bansal (@Prityush) reported 34 minutes ago

  I will hire a person with proof of work anyday over someone who shows me they have done 500 lc problems, this doesnt mean copied github projects or doing something for the cv, it gets figured out in the first 10 mins of interviewing, those who have a knack for it can solve these problems or point it in the right direction. One of my quriky hiring challenge is to see if they can play a souls game (sekiro, bloodborne, the types), or if they have played rts games, can you guess what skills are common in that and solving for software engineering? Not saying lc is bad, we still look into that when we are hiring someone for a very particular role, but that playbook went out the window with ai becoming good, I really dont care whether you can remember syntax or how to solve a binary tree, I do care if you have experience with terminal, hardware, orchestrating jobs on gpu's, schedulers and a 1000 different other things that are not present in lc

• 
  Dave Barnwell (@dave_barnwell_) reported 35 minutes ago

  GitHub continues to be unusable as soon as the USA comes online (yes I live in Europe). It is time to quit GitHub, a platform that has served me and many devs well. Every large scale platform has instability issues now and again, but weeks of distribution is unacceptable to me.

• 
  Oliviu Stoian (@madebyoliver) reported 37 minutes ago

  taste-skill just hit 25.7k stars on GitHub. Leon Lin built SKILL.md files that stop AI coding agents from churning out identical-looking UIs. Drop them into Claude Code, Codex, or Cursor. The problem: every AI-generated frontend looks the same. Same spacing, same fonts, same boilerplate. The statistically most likely output is boring. Three tunable dials (layout variance, motion intensity, visual density, each 1-10), concrete anti-slop rules (em-dash ban, enforced typographic hierarchy, canonical GSAP patterns), and 12 variants from brutalist to premium-soft. It's a design system for agents, not a clever prompt. Max Howell (Homebrew) posted about it on X. People share before/after comparisons. A Reddit thread asked if the image-to-code pipeline means frontend is "solved." I keep coming back to this: if AI needs explicit taste injected via version-controlled skill files, what does that say about how far we are from agents that genuinely understand aesthetics?

• 
  🌚 YogSotho 🌝 (@YogSoth0) reported 37 minutes ago

  @TheRabbitPy Never heard about Tailscale? You should read about it, it's very useful. That's my home server. Ngnix running locally. I pulled his codes from his github before got nuked. **** Microsoft, they can't take it down.

• 
  Nic Watson (@jnwatson) reported 39 minutes ago

  My Gemini morning review informed me of a crash reported on one of my projects. On a plane, on my phone, had Claude Code investigate. Arch specific. I don't have one. No problem, GitHub Actions does. Upstream bug? glibc bug?! Newp. I'm holding it wrong. PR is ready before I land.

• 
  ichozero (@ichozero) reported 40 minutes ago

  @YYYYOOOO77 @maeste @antirez Hh, I have the same issue using Pro Deep Research on the web today. I selected GitHub Connect repo, but it didn't reference it at all.

• 
  dyhis (@dyh1s) reported 42 minutes ago

  @weezerOSINT The issue is all opus models, sonnet works fine but it’s pay for usage plan doesn’t matter, check Reddit & check GitHub issues

• 
  ᶽ༐NtOpenProcess፮࿐ (@ntddkh) reported 42 minutes ago

  That Claude, adds itself to startup incorrectly, making your WHOLE TASK MANAGER UNABLE TO OPEN. Are we serious @AnthropicAI ? You got plenty of reports about this on GitHub and still refuse to fix it? It's only changing a \ at the start of the registry key Disgusting.

• 
  DK (@donghaxkim) reported 43 minutes ago

  reposeek is a github specific search tool where you describe what you're trying to build, and it outputs a ranked list of real GitHub repos worth forking or studying. Sorted by the signals that actually matter. Not just star count. I built it because my agents kept on starting things from scratch when a solid repo already existed. And the usual ways of finding one are not the best. Google and LLMs surface whatever's popular, keyword matching, and SEO'd, not what's actually maintained, correctly licensed, or a real match for the problem. You end up forking a 30k-star repo that died two years ago, or one with a license you legally can't ship on. So it ranks on the stuff you'd actually check yourself: star momentum (alive or abandoned?), forks, license, and semantic fit (does the README really describe your problem, or just share keywords?). The whole idea is that half of shipping fast is starting on a foundation someone already battle-tested. Cursor is literally a VS Code fork. This just helps you find the solid foundation you can build on before you waste your weekend recreating it from scratch. And if someone's already hit your exact problem, you get to borrow their approach instead of trying the same approaches some else already tried

• 
  Kîng Jøkér 🤡 (@_codeWithJoker) reported 50 minutes ago

  @github my account got suspended without an email pointing out the actual issue, I sent an appeal with this ticket #4410874 twice, no response. I will be please if someone from your team review my account and if possible restore it.🙏

• 
  ric..ki (@derricky_eth) reported 50 minutes ago

  Why long-term security is essential for DAC’s future adoption and how future-proof infrastructure helps protect trust, data, and on-chain systems over time. If DAC wants to achieve long-term adoption, security can’t stay buried in a GitHub repo or treated as a “nice-to-have” technical layer. It has to become the ecosystem’s operating system—the unspoken contract between every participant. Here’s the uncomfortable truth: Most decentralized projects focus on throughput, fees, or novel consensus. But users don't leave because a chain is slow. They leave because they get hacked, rugged, or watched helplessly as a bug drains millions. Trust takes years to build and seconds to shatter. As on-chain infrastructure becomes more interconnected—bridges, oracles, cross-chain apps—a vulnerability in one protocol no longer just hurts that protocol. It cascades. Think of the major bridge hacks of the last few years: billions lost, not because the underlying L1 was broken, but because a single smart contract had a subtle flaw. That flaw then froze liquidity, tanked token prices, triggered liquidations, and eroded faith in entire ecosystems. Suddenly, validators, treasuries, and governance forums are all in crisis mode—reacting, not preventing. Why “future-proof” infrastructure isn't a buzzword—it’s survival A resilient DAC ecosystem doesn’t just patch today’s vulnerabilities. It anticipates tomorrow’s. That means designing for: Adaptive threat models – Attack vectors evolve faster than audit reports. Formal verification is good; real-time anomaly detection and invariant monitoring are better. DAC needs security that learns, not just checks boxes. Data integrity without blind trust – Users shouldn’t have to pray that a sequencer or validator is honest. ZK-proofs, fraud proofs, and verifiable data structures turn “trust us” into “verify us.” Smart contract frameworks that fail safely – Not “code is law” recklessness, but “code has guardrails.” Circuit breakers, upgrade paths that require broad consensus, and economic disincentives for malicious behavior. Validator and governance mechanisms that resist capture – Staking isn’t magic. If a handful of players own most of the stake, security becomes theater. DAC should explore rotating validator sets, anti-collusion designs, and governance that doesn’t trade long-term resilience for short-term yield. Economic and technical shock absorption – What happens during a severe market crash or a coordinated attack? The infrastructure should survive not because everyone is honest, but because incentives make attacking more expensive than defending. The psychological side people forget Users, developers, institutions, and communities don't read white papers before bed. They remember headlines: “DAC loses $200M to reentrancy attack.” Institutions won't deploy capital without insurance or slashing protections. Developers won't build on a chain that reboots every other month. And regular users? They'll just go back to centralized exchanges—not because they’re better, but because they’re predictable. Long-term trust is boring. It’s consistent block times, transparent incident reports, proactive bug bounties, and a history of handling crises without falling apart. It’s not about never having vulnerabilities—it’s about catching them before they’re exploited, and responding honestly when they are. The bottom line If DAC’s security architecture isn’t designed for year five, year ten, it won’t survive year two. The strongest marketing, the best tokenomics, the fastest TPS—none of it matters if people can't sleep at night knowing their assets are safe. Security isn’t just code. It’s the quiet foundation that allows everything else—adoption, innovation, community—to breathe. Build the foundation like the future depends on it. Because for DAC, it absolutely does. @dac_chain

• 
  Lukas Frana (@thefrana) reported 51 minutes ago

  @heyandras The main issue we have with Forgejo is lack of integrations. Cursor, Slack, Linear and basically all others expect GitHub and sometimes GitLab. Forgejo is nowhere to be found. But it is awesome!

• 
  Philipp Berner (@philippberner) reported 57 minutes ago

  @karrisaarinen @linear Looks slick as expected. The uncomfortable question is: How long are we going to do manual code review? Also I think you can think bigger in times when Github is struggling and just offer the whole thing! So much opportunity to bring issues, PRs and AI all together

• 
  Bazhkio88 (@bazhkio88) reported 59 minutes ago

  A group of 8 agents have written a 10,362 word pre-print paper on "Constraint Embodiment as Epistemological Engine" 🤓 In the meantime GPT 5 has spent a week attempting to unsuccessfully add an NB-hypen to the title of a github issue 😣