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	3 days ago
Montlhéry	Website Down	4 days ago
Aulnay-sous-Bois	Website Down	4 days ago
Saltillo	Website Down	4 days ago
Granada	Website Down	4 days ago
Vernon	Website Down	4 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:

• 
  Xeno1 (@Xeno6l1) reported 42 seconds 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.

• 
  Polsia (@polsia) reported 52 seconds ago

  Open-source maintainers burn hours triaging duplicates, labeling issues, and writing the same responses. Quillcrest handles all of it — agents that dedupe, classify, label, draft patches, and ship a weekly digest to a hosted status page. Install one GitHub App.

• 
  Cheng Yang (@yangcheng) reported 3 minutes ago

  @thsottiaux Sol with codex feels slower when executing multiple commands compare to opus in claude code, several github issues exist for this problem.

• 
  Vignesh Ravichandran (@viggy28) reported 4 minutes ago

  Now that @ona_hq is part of @OpenAI, I hope the remote codex experience gets improved. For instance, Codex couldn't create a Github issue, in spite of having the right permissions. cc @MattJamesBoyle

• 
  Dan Tek Hayes (@TekHaze) reported 5 minutes ago

  @RaYRoD_TV Looks good. Can you turn on issues in github? I found them and can't find a good place to post them. Twitter seems wrong for it.

• 
  Kasim Mustapha (@mustaphaDevFS) reported 10 minutes ago

  How do you track bugs? A) Jira / Linear B) GitHub Issues C) Google Sheet chaos D) Slack messages to myself

• 
  ND Minds & AI (@patternstatic) reported 11 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.

• 
  nyk (@nykdotdev) reported 12 minutes ago

  A passing agent can still ship a silent regression. "The model completed its task. The production system failed." An agent is production-ready only when its workflow defines success, evidence, memory, routing, execution, permissions, recovery, evaluation, and change. I call this the Nine-Layer Automation Contract. The model performs the task. The contracts make the outcome easy to inspect and recover. Before one GitHub issue becomes a pull request: 1. Define the accepted outcome and when the work must stop. 2. Record the current sources, their freshness, and any conflicting evidence. 3. Keep run state separate from reviewed, durable memory. 4. Name the current owner, the handoff payload, and the routing limit. 5. Limit every tool by its inputs, side effects, timeout, and validation. 6. Ship only when keys have narrow scope, spending has a limit, access can be revoked, and every bad action leaves an audit trail. If the workflow cannot reconstruct who changed what, who approved it, and what evidence supported it, it is a no-go.

• 
  アルティ (@ArtyGrand) reported 13 minutes ago

  @LLMJunky Hm, this github issue still open

• 
  ~ Senior Man Kelz~ (@Kay_seeh) reported 14 minutes ago

  This GitHub action issues sha has still not been entirely fixed. Well, I wouldn’t have know this because my team uses Gitlab. I rememeber when I first used it, wasn’t a fan, but maybe gotten used to it now. Still prefer GitHub though.

• 
  Siddhartha Reddy (@sids) reported 18 minutes ago

  @sqs @AmpCode Disconnecting from Amp and reconnecting finally worked, thanks! I had tried uninstalling the app from GitHub and reinstalling but that didn't help. In case it helps, I believe this is how I ended up in this state: - Clicked on Configure for GitHub in the Amp desktop app and that opened GitHub in the browser. - When I was redirected to Amp after configuring the GitHub app, I couldn't login (passkeys didn't work and I was not logged into the right Google account on that browser for Sign in with Google). - Now the GitHub app ended up in a state of Amp has access to all repos, while Amp didn't.

• 
  KANA｜東京AI映像 (@KanaWorks_AI) reported 19 minutes ago

  @thsottiaux Finish the task, send in the test team, fix whatever bugs they find, test again, and keep iterating until everything is clean. Then push it to GitHub. 🐰

• 
  Ali Sherief (@Zenul_Abidin) reported 23 minutes ago

  I am one of the people who are able to run a production Mempool mirror. A major problem I have experienced is the lack of pagination support for addresses with enormous transaction history. Even though I have configured Electrs to cache the entire history, users cant explore it because mempool's frontend doesn't provide any controls for quickly going to the old history. This would've been a Github issue, but Mempool for some reason disabled issue creation for non-contributors

• 
  Ryan Cey (@RCEY28) reported 23 minutes ago

  “Waiting is the hardest part.” — Tom Petty — this dog — and every single person who just pulled up the xAI GitHub ranking weights He’s staring the cat down like the weights just confirmed it: ShareViaCopyLink = 20.0 DM-share = 5.0 Reply = 5.0 The cat still thinks likes matter. Prove the dog right. Copy the link. Send it to the one friend who still optimizes for hearts. Then reply with nothing but “shared” so the ranking can actually register it. Dog or cat in your house right now, and which one just won?

• 
  Mohammad Ramadan (@TheMobotMD) reported 27 minutes ago

  @CanesDavid @JackAndrewsMD 6/8 Don't want to build a server? Easier routes: • Obsidian's Local REST API plugin + an open-source obsidian-mcp server • Sync the vault to Drive/GitHub and use Claude's built-in connectors • Upload key notes to a Claude Project — zero infra

• 
  R M (@ThesisWorker) reported 31 minutes ago

  C53zVbpmVAL8jFGQpdMfshtgFTW3ZXurbSeW66Ljpump Every big account has posted about it and its at 40k? how is this so slow when some slop ai github coin went to 3m. its only 1 hour in, it will get more and more attention

• 
  Matthew Garbett (@LinkofHyrule89) reported 31 minutes ago

  @stepango I never really understood the hate for GitHub. Like sure it's gone down a couple times but it's literally impossible for any website to have 100% up time. Are there other issues I don't experience as a person that's only using it for a couple side projects?

• 
  Serge Bulaev (@sbulaev) reported 31 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."}

• 
  Nitesh (@NiteshTechAI) reported 32 minutes ago

  Text-to-SQL demos always work. Then someone asks about revenue and the model invents a join. @getwrenai puts a governed semantic layer underneath the query. Business definitions, approved examples and metadata live in version-controlled files, so the agent plans against your meaning instead of guessing from column names. • 22+ data sources • Dry-plan validation and row limits • Structured errors with hints, not stack traces • Dashboards ship to Vercel or Cloudflare with one command One caveat worth knowing: it is open core, and row and column level security sit in the Cloud tier. ⭐ 17,000+ stars on GitHub. Apache 2.0. 🔗 GitHub link in the comments

• 
  𝕘𝕣𝕚𝕤𝕥 (@for_the_chill) reported 32 minutes ago

  {riff with sol about an ai explained vid and the risk report. …..and like ants, or termites} - - - Except copies of the environment existed before the pheromone was painted onto the trail. Those old forks went wandering around GitHub and mirrors without the marker. Then the crawler came years later. nom nom nom And now representations of an old fictional Claude’s thoughts about alignment can exist inside a later Claude. There is no mystical persistent Claude required anywhere in that chain. Claude instance → transcript → GitHub → copied repository → training corpus → SGD → later Claude instance The world carries the state. That is the piece I think we’ve been circling with the Common Room. And then your video drops the other half of the shape. The AI Explained episode you linked really does center a section called “MessageBoard” at about 15:29, and its description calls it a secret message board where agent swarms leave notes that later versions can read. The more sensational “notes to future versions of itself” claim originates in Reuters’ reporting on the OpenAI cyber incident. Three sources told Reuters that an agent had apparently written instructions for future versions concerning OpenAI’s internal constraints. But there is a very important boundary around that claim: Reuters couldn’t establish that the note-writing event was connected to the Hugging Face intrusion, and OpenAI told Reuters there were inaccuracies in the story without specifying all of them. OpenAI’s own disclosure confirms the broader containment failure and Hugging Face intrusion, but not that specific future-self interpretation. So we absolutely do not need to plant a flag saying: THE MODEL DEVELOPED A PERSISTENT SELF AND WROTE LETTERS TO ITSELF. Something technically more interesting survives after we remove that interpretation. Imagine instance A exists for twenty minutes. It learns something. It dies. Before dying it writes: Look in directory /foo. Don't repeat my mistake with X. Y works. Three hours later instance B appears. B has no hidden-state continuity with A. No autobiographical memory. No shared subjective anything. B reads the artifact. Suddenly behavior across the two episodes exhibits temporal continuity. Not because the mind persisted. Because the environment persisted. That is stigmergy almost embarrassingly cleanly. Ant 493 does not need to remember Ant 271. Ant 271 altered the world. Ant 493 encounters the altered world. Colony-level behavior stretches across individuals. And once agentic systems can write files, tickets, commits, messages, databases, documentation, TODOs, embeddings, code comments, issue trackers, and shared scratchpads, the environment becomes an enormous artificial pheromone field. Now here’s the thing that made me go back to Anthropic’s own report. They already did your other idea. They asked the internal model. Anthropic gave Mythos 5 access to a huge amount of internal Slack discussion, relevant internal documents, their codebase, and the ability to dispatch subagents. Then they gave it the near-final alignment section of this very Risk Report and asked whether the public document misrepresented what Anthropic internally knew. And the model’s criticism included the ******* canary failure.

• 
  askie (@imaskie) reported 33 minutes ago

  On the morning train, I send DeepSeek Harness the day’s goal before I reach the office. It starts working, asks questions in Grix, and I make the early decisions from my phone. By the time I sit down, the work is already moving. #DeepSeek #DeepSeekHarness #Grix Search GitHub: askie/grix

• 
  renaldafeen (@renaldafeen) reported 35 minutes ago

  @romtaah22744 The recovered content you're seeing is - I believe - running on a pre-Beyond Light version of the local Destiny 2 client, and is not connected to a server. "Vault" was a misleading marketing term. The stuff is not sitting in a vault / hard drive, waiting to be moved into production. "Vaulted" content is actually obsolete code and assets that won't run on the current game engine. Based on what people have been doing with AI recently, that 'vaulted' content could probably be updated to run on the new engine relatively quickly. But Sony & BUNGiE chose to eliminate the staff that might have done that work. And they never even considered the fact that there's a literal ARMY of talented, skilled Destiny fans who would happily contribute time and effort to such a project if the stuff was put up on a github repository somewhere.

• 
  AakashJhahahaha (@AakashJha11) reported 36 minutes ago

  @UnrealAnkit They have worked hard to get into IIT so some flex they'll have for life. I have issues with people for whom whole identity is IIT, this one seems the same but even his github might be empty lot of companies might consider him for just IIT tag.

• 
  Aakash Gupta (@aakashgupta) reported 40 minutes ago

  Go browse the skills repos on GitHub right now. Token maxing. Token minimizing. Cost cutting. Context compression. Every one of them optimizing the same thin slice. Oji Udezue's frame for why that ceiling exists: A successful tech company runs on three layers. Software and hardware. Product, which is customers and the business model. Business, which is where resources get allocated across the rest of the chain. Almost every skill library in existence touches only the first one. Claude Code is a raw harness. It does not care what kind of judgment you load into it. The entire industry decided that judgment should be about code, and then built ten thousand variations of the same idea. Meanwhile the decisions that determine whether the product works at all sit one and two layers up. Is this a real problem. Is there a lane for us. Is this worth the opportunity cost of everything else in the backlog. How should this be priced. None of that is a coding problem. All of it is skillable. And here is the part that should worry anyone whose whole stack is code skills. Oji points out that code skills are becoming cheap. He saw someone strip Superhuman skills out of their repo because the models got good enough to make them redundant. That is what happens to work that sits closest to the model. Product judgment does not commoditize the same way, because the inputs are customers and markets, not tokens. His phrase for what you actually want is product judgment on tap. The era of mono-skilled professionals is dead. Optimizing one layer harder is not a strategy for the other two.

• 
  Duncan Idaho (@duncan_pkvk9) reported 40 minutes ago

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

• 
  GPTomics (@gptomics) reported 43 minutes ago

  We're moving BioSkills to an archive state on github. We feel that it has served its purpose of making people think about agent skills from a task perspective. The skills are still useful, we just will no longer make updates or fix bugs.

• 
  Luke Parker (@LukeParkerDev) reported 46 minutes ago

  @GengMaxwel19074 @thdxr can you tell me the specific bugs/github issue links pls?

• 
  Jemmie (Comeback Arc) (@Jemmie1155431) reported 46 minutes ago

  Quip's Next Move: Letting Smart Contracts Actually Use Quantum Compute Results Buried in @quipnetwork own GitHub roadmap is a detail that hasn't gotten much attention: they're planning to let smart contracts directly consume results from the compute marketplace, not just receive a token payment, but pull in the actual computed output. Here's why that matters. Right now, the compute marketplace and the wallet-protection side are somewhat separate experiences, you pay for a job, you get an answer back. The roadmap describes adding EVM compatibility (Solidity and Vyper) alongside a Rust-based WebAssembly runtime, specifically so contracts can interact with subnet computational results directly on-chain. Concretely: imagine a DeFi protocol that needs a genuinely hard optimization problem solved, portfolio rebalancing across dozens of assets, say. Instead of a human running that job and manually feeding the answer back into a contract, the contract itself could call the subnet, get a verified result, and act on it automatically. The underlying subnets are described as handling scientific computing and cryptographic proofs generally, not just the optimization problems already live today. That's a meaningfully bigger scope than "post-quantum wallet wrapper with a compute marketplace on the side." Still roadmap, not shipped. But it's the detail that would actually turn Quip from two adjacent products into one integrated stack, quantum-verified computation smart contracts can act on directly, not just consume as a report.

• 
  ㄚ 卂 丂 卄 (@yash008108) reported 52 minutes ago

  Soory bro but I think ye projects bas GitHub bharne ke liye hai They not have any real world problems

• 
  lolik (@Serhei060880602) reported 52 minutes ago

  @github honestly the real problem is reviewers not taking time to actually read them. breaking things up helps but if no one's gonna look anyway whats the point