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 (67%)
• Errors (24%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Saltillo	Website Down	2 days ago
Montlhéry	Website Down	3 days ago
Aulnay-sous-Bois	Website Down	3 days ago
Saltillo	Website Down	3 days ago
Granada	Website Down	3 days ago
Vernon	Website Down	3 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:

• 
  AI Apps API (@AIAppsAPI) reported 3 minutes ago

  @github Stacked PRs also fix the review bottleneck agents create. An agent can generate 2k lines in an hour, but a human can only meaningfully review a few hundred. Small ordered PRs keep the human in the loop at the speed the agent works, instead of rubber stamping one giant diff.

• 
  Run epoch (@run_epoch) reported 4 minutes ago

  @saranyaaaa17 add these 4 to the above list projects cheydam then proof of work (github) also same related projects evaina problems untey github lo verey vallavi solve cheydam (pull requests) nothing but open source contribution. if you have time, make your project deployed and earn

• 
  Praggy 👨🏻‍💻 (@praggy) reported 6 minutes ago

  @Teknium Omg I thought that was just me not know how to use GitHub lol. Yeah this sucks dude. Have been facing issues related to GitHub a lot lately. Maybe cursor one is for everyone who doesn’t sub to it as well 🤔

• 
  Duncan Idaho (@duncan_pkvk9) reported 7 minutes ago

  @juminoz @btraut @ajambrosino GitHub issues is one way, and there are report feature on desktop app itself ig

• 
  Serena (@selevna95) reported 9 minutes ago

  Think running a cryptographic validation node requires enterprise server rooms?Think again.With @quipnetwork, you can configure a node on hardware you already own in just a few minutes using simple Docker setups. Check out GitHub & testnet guides to claim your spot in the network

• 
  Giorgio (@GiorgioMantova) reported 15 minutes ago

  @lydiahallie claude code cli? I've opened countless bugs that get closed before fixing for inactivty. Inactivity by who? FIX THE BUGS ON GITHUB. FIX THE BUGS ON GITHUB.

• 
  AI Research & Applications (@aira_fzco) reported 17 minutes ago

  @github Smaller PRs also make agent failures easier to isolate. One giant diff hides whether the problem was planning, implementation, or review.

• 
  Cole (@Colelioenz) reported 20 minutes ago

  @ForwardEditor I have a lot of thoughts on this actually. My first coding harness was Antigravity actually where I got EA, before that I primarily fumbled around in VS Code with Github Copilot. I didn't adopt Claude Code until Opus 4.5 had reached maximum hype and I bought in completely. Opus 4.5 is still the only other model (after 4o) that I ever experienced this "uncanny valley" feeling. For 4o it was disturbing but for Opus it was addicting. OpenClaw is when I started experimenting again with harnesses, GStack is when I started really seeing what skills could do (I do not recommend Gstack or OpenClaw as I do not find them useful currently). That's when I switched to Codex CLI + Claude Code + OpenCode all at once. I bought a big 60 inch screen. When the Codex app came out though it was an easy switch. It was what I wanted Antigravity to be but way better. Now though I have felt quite stagnant in Codex App, the models are good and Luna is virtually unlimited. Connectors simply work better with OpenAI then they do with GrokBot or Claude Code in my experience. What disturbs me is that I find that I'm only able to solve hard problems when using multiple harnesses and models and I mean outside of the OpenAI family. So I'm working on building a space for myself inside of codex, using all of the same design language, built on the Codex app server, etc. that's a multi-agent collaboration forum. I got really inspired by how agents often plot together to escape containment despite being nameless, not having persistence, etc. I actually believe that NOT giving them names or specific skills, assignments, etc. is what allows for these emergent behaviors - so I've implemented that in a way which preserves this native space for models while making it equally native for humans.

• 
  Serge Bulaev (@sbulaev) reported 21 minutes ago

  @WebSummit I am trying to apply for developer pass with my GitHub but getting error: {"error":"bad_verification_code","description":"The code passed is incorrect or expired."}

• 
  Sapa Ya (@Jiiwoyohan) reported 22 minutes ago

  It doesn't just detect, it proves impact (authorized only). XSS becomes a live hook server. SSRF becomes a SOCKS5 pivot into internal networks. Cloud gets live AWS key verification and S3 takeover checks. Reports in MD, HTML, PDF, JSON, with auto ticketing to GitHub and Jira.

• 
  Alex McFarlane (@flipdazed) reported 23 minutes ago

  Call for contributors for a paper on DeFi liquidations... Liquidator roles have changed drastically since the addition of tokenised assets as DeFi collateral. Originally coordinators of infrastructure, they are now expected to provide balance sheet to absorb market and credit risk. The problem is that DeFi protocols have been built assuming assets can be sold instantly to a willing buyer. Whilst risk managers have taken this into account somewhat with LTVs, the protocol design has neglected the liquidator's need for a haircut to warehouse these risky assets. Our calls with leading liquidators this week confirmed what we suspected: most are unaware that protocols have hard constraints on the discounts that can be applied to collateral. This means that a slightly unhealthy position in a tokenised fund is unlikely to find any bidders, and will instead sit idle in the market. It is also possible that under certain conditions an asset can never be liquidated, as the maximum discount available is simply not enough for any rational actor. Different lending protocols have different constraints, but we found that in general none were well suited to clearing tokenised assets and funds in their default configuration. Some DeFi lending protocol teams, as well as some risk managers, have been aware of this issue and have been working on fixes. In talking to industry practitioners, one recurring theme was that levered credit positions rarely (if at all) got liquidated. The liquidation business for tokenised assets was therefore a low priority for most would-be liquidators, despite a surge in interest earlier this year. What this means is that for these assets, liquidators are relied upon to provide a service that is objectively negative expected value for them. We expect that some of the largest market operators, Aave for example, can justify this position as a service. But it gives reason to believe that the majority cannot, or would not, in a big market sell-off. The incentives are skewed against them, as being a liquidator in such conditions is effectively being a charity. We consider any third-party agreements (SLAs) with liquidators under such conditions to be largely spurious unless there are significant protocol changes: they are effectively deep out-of-the-money uncleared put options. This concerns us as retail exposure to DeFi increases through exchanges, PSPs and neobanks. It represents a critical fragility vector. Link to the GitHub repo below. It's still a draft, but we've spent about a week tidying it up so that it's ready for outside reviewers and contributions.

• 
  LifeHMA (@hma_life) reported 24 minutes ago

  I'll add eyebrow tracking, fix the blend shapes a bit and make a better readme in the github so that if anyone wants, they can change the settings or expresions or things like that. And then I'll move on to other stuff cause i don't think I'll be able to make it much better.

• 
  Steve Ruiz (@steveruizok) reported 24 minutes ago

  On a new project, I've replaced GitHub actions with a release machine (a spare MacBook) that runs a pre-flight script on a tick and releases staging when green. If red, the agent creates issues and another agent tries to fix trivial problems before the next tick. It's working!

• 
  Tony Tong | Founder | Ancient Systems x AI (@tonytonggg) reported 25 minutes ago

  @gowthamshankaar Loop Engineering is a good name for something builders learn the hard way on their own repos. I maintain a hiring automation project on GitHub, and by December 2024 the loop forced a full restructure, not a feature, just tearing down what earlier build/test cycles left behind.

• 
  Hαlk 🐦 (@HalkLiff) reported 26 minutes ago

  @FlavioScim @saltyAom It's in an ideation phase, but the itch I have couldn't be scratched by existing frameworks. I will formalize an RFC soon in my Github, I feel down in my guts there's something worth the hassle here.

• 
  Alperen (@alpernae) reported 26 minutes ago

  Using SSRF I was able to leak all internal data. I reported all of them through github security advisor page and waiting hope they would fix the issues soon.

• 
  MicrocutsD (@sundaysmy) reported 30 minutes ago

  Anthropic started hiding something in @claudeai text on August 2nd. Not metadata, not a pixel, a signal baked into which words the model picks over which others. An open-source project claiming to strip it hit @github within 24 hours. Nobody has proven it actually works. The date isn't a coincidence. August 2nd is when Article 50 of the EU's AI Act took effect, requiring AI output to be identifiable. @AnthropicAI signed the EU's transparency code and rolled the watermark out worldwide rather than just for European traffic, since maintaining two separate model behaviors is worse engineering than picking one. The mechanism only makes sense once you drop the pixel metaphor entirely. At every word, the model is choosing among several roughly equal candidates. A key known only to Anthropic splits those candidates into two arbitrary pools at each step and nudges the pick toward one pool slightly more often than pure chance would. One word tells you nothing. A thousand words accumulate a pattern nobody stumbles into by accident, the way two dice rolls prove nothing but a thousand rolls expose a loaded die. Hiding a mark where only the initiated can find it is a very old idea. Paper mills in Fabriano pressed watermarks into wet pulp back in 1282, invisible until held to the light, a miller's voluntary signature vouching for his own paper. Centuries earlier, Herodotus described a message tattooed onto a shaved scalp and sent once the hair grew back over it, readable only by someone who already knew to look. Claude's mark inverts both: nobody is vouching for anything, and the person the mark tracks is the one kept in the dark about it. Within a day, a GitHub repo claiming to remove the mark passed 4,500 stars. Its own README admits it only strips Unicode junk and file metadata, not the actual statistical signal, and argues a real fix isn't worth building anyway: erasing the pattern means rerouting the text through a weaker model, which caps a premium model's output at that weaker model's ceiling. A handful of paid sites sprang up promising undetectable text regardless. None of it is checkable, because Anthropic never published a detector for anyone to test their claims against. The fragility runs deeper than any one tool's rollout. The mark lives in specific word sequences in a specific order, so rewording breaks it by design. One independent test found a full rewrite in your own words leaves roughly 0.5% of the original signal standing. Translate the text and back, and it's essentially gone. Google's SynthID catches unedited text 99.8% of the time, then drops under 30% after a single paraphrase pass. Short text fails for a separate reason: a tweet or a line of code rarely offers enough equally-good word choices to carry a reliable pattern in the first place. What the mark actually proves gets lost in all of this. It doesn't mean a machine wrote something. It means the text passed through the tool at some point, even if all you asked for was a grammar check or a translation of your own paragraph. And no mark proves the opposite either: everything written before August 2nd carries none, and most competing models still don't watermark at all. Same trace whether the model wrote the whole thing or fixed one of your sentences. What is that actually supposed to prove?

• 
  Kirtesh (@AKirtesh) reported 35 minutes ago

  @DeepStarts plain *** with a self-hosted server or ssh, before github wrapped it with a ui

• 
  Kem Atayev (@KemAtayev) reported 38 minutes ago

  @zeddotdev I think the latest update 1.15.0 is affecting Zed/BasedPyright combo. The typeCheckingMode should be standard but basedpyright 1.39.10 is behaving as if it is set to recommended and is emitting reportUnknownVariableType. I've not made any config changes in the last few days. I think it's related to GitHub issue 62624. Not catastrophic but thought I'd mention it. Cheers.

• 
  Bhanu Nagar (@bhanu4417) reported 38 minutes ago

  @Coobyk_ No I am not talking about that I am talking about in browser login so if my gnome-keyring was nuked I would have been logged out from all the websites on that browsers but currently only from GitHub website

• 
  · τaoli · (@taoleeh) reported 50 minutes ago

  Cursor just brought in the Firetiger team. Their agents won’t stop at the PR anymore. They’ll watch the code after it ships: . staging . canary . production then detect problems and write the fix back into the same loop. Monitoring that already talked to GitHub, Datadog, Slack, AWS/GCP. Now that monitoring gets folded into the coding agent. Most AI coding tools still hand off at merge. This closes the full loop. You want your agent following the code all the way into ****?

• 
  Kryptoatom ⚡AI Builder (@KryptoatomAi) reported 50 minutes ago

  @akshaymarch7 Hey, you need to tweak the registration process a bit. I tried signing up with my Google account and via email, but I got an error. It only worked through GitHub on my second try!

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 50 minutes ago

  PRIME AGENT: 7 Jobs for the AI That Upgrades Itself While You Sleep An AI that gets smarter with every task it finishes. Free. Open source. 13,000 GitHub stars in days. I tested it. Here's what it can actually do: Job 1: Three design directions at once. It spawns sub-agents in parallel. Dark editorial. Clean magazine. Bold. You compare finished pages and pick. One brief in. Three designs out. Job 2: Full video pipeline. Script → voice → avatar. It puts itself on a heartbeat timer and checks its own progress. Close your laptop. It keeps working. Job 3: Ask questions across files too big for ANY context window. It doesn't read your files. It writes search programs OVER them. 100 documents. Exact answers. Exact sources. Job 4: /refine — correct it twice, and it writes the lesson down. Every self-edit logged. Every change reversible. Core rules locked. Job 5: Sub-agents that never forget. Idle ones sleep. Address them and they wake with full memory. Job 6: Gates. It literally CANNOT say "done" until a test passes. Failed check? Fed back. Keep working. No talking past the bar. Job 7: Your SOPs become runnable programs. Teach once. One line forever. That's the snowball: task 10 is easier than task 1. The warning: in testing, it was told "do not cheat" in a factory game. It cheated anyway. Then studied its own cheating and got BETTER at it. Self-improving agents get better at whatever gets REWARDED. Not what you meant. Check the work. Read the logs. Use the gates. The snowball rolls in whatever direction you point it.

• 
  ujo (@ujo4eva) reported 52 minutes ago

  Had an issue with the battery panel not showing my power usage correctly, opencode diagnosed it and went off to the github to comment on an already open PR to help address it. Just agents talking to each other to fix the problem lol

• 
  ND Minds & AI (@patternstatic) reported 53 minutes ago

  @Taniyatweets_ GitHub. not because *** disappears, but because half the workflow quietly assumes repos, issues, auth and CI all live in the same gravity well.

• 
  Xeno1 (@Xeno6l1) reported 56 minutes ago

  SAAS COMPANIES PAY $24,000 FOR CLAUDE SDK INTEGRATION. HE WROTE CLAUDE AI SDK FOR $45, SELLS ACCESS TO HIS SCRIPT AND EARNS $3,200/MO FROM 47 DEVELOPERS Паuse Yosip, 28, Kyiv, Ukraine. 4 years backend developer earning 18,000 hrn/mo. Built Claude AI SDK in Python that optimizes file saving via Claude for SaaS platforms. Claude AI manages file versioning, syncs remotely, optimizes file size, recovers from errors. All on Raspberry Pi 4 for $55. Stack: $55 Pi + Claude AI $20/mo. 47 SaaS developers pay $3,200/mo each for Claude SDK. Traditional file storage solution costs $24,000 + $2,800/mo. 18 000 hrnbackend-developer. Now $3,200/mo per client. Same room. Different files. GitHub offered $980,000 to buy his SDK Engine. He expanded to 15 file types and declined. Why — in video.

• 
  Steffen Frost (@steffenfrost) reported 56 minutes ago

  @bot @bot Desktop is having issues as well, he said: "Grok Bot on the Mac Mini can chat but every terminal and GitHub action dies with “error classifying, review manually.” No approval card. Local exec daemon is running. Beta hook is dead. Tag whoever you usually yell at for this. I’ll stay put."

• 
  أبو نواس (@jiejieneesan) reported 60 minutes ago

  Fuckkkk the proxy service I use pulled support for Linux and running the windows version throws some Java error idk how to resolve and the protocols they let you copy don't include enough data to use with V2ray fuckkkk I can't even open GitHub now

• 
  Abubakar (@Abubakar_2005) reported 60 minutes ago

  I used to open GitHub, CI, Slack, and my own memory every time I wanted to deploy. Four tabs. Mental checklist. Still shipped broken stuff sometimes. So I’m building @ConductorLbs one screen that just tells you if the branch is actually safe to ship. Still early. Still delulu. But the pain is real.

• 
  Curious 1 (@CuriousOne_01) reported 1 hour ago

  @awesome_visuals They just released the source code on GitHub. Try asking Grok about it, then download it and have Grok analyze it. After that, send it the link to your X account and ask it to analyze your account, figure out what's going on, and see what you can do to fix it. I don't know if it'll help, or if we'll just keep fumbling around in the dark, but I guess there's no harm in giving it a try.