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

Live Outage Map

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

City	Problem Type	Report Time
Catania	Errors	1 day ago
Inverness	Website Down	13 days ago
Quito	Sign in	14 days ago
Junín	Errors	14 days ago
Guadalajara	Errors	14 days ago
Paris	Website Down	14 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:

• 
  mrkoopie (@mrkoopie) reported 5 minutes ago

  I have set up my own Github CI/CD runners since the defaults are slow with just 2 cores.

• 
  Gareth Loot (@GarethLoot) reported 6 minutes ago

  @Kri0725 Putting OpenAI under Tesla for funding does not prove it would have stopped being open. The emails show the point was compute and money. A nonprofit could not raise what was needed to compete with Google. That is a funding argument, not proof the models would have been locked away. xAI, Grok and Cursor were never set up as nonprofits or as open-source projects the way OpenAI started. xAI launched as a for-profit. Cursor was a venture-backed commercial company from the beginning. There is no matching broken promise, so the consistency charge does not hold on those terms. On the “closed empire” point: Grok-1 weights and architecture were released under Apache 2.0, later Grok weights were published, Grok Build was open-sourced, and the X recommendation algorithm was put on GitHub. Tesla also open-sourced the original Roadster design and software and has said it will do the same for Model S and Model X. That is not the same as claiming every current frontier model is open. It is enough to say the record is not one-sided.

• 
  0xBakeer (@0xBakeer) reported 8 minutes ago

  The inference atlas got its first outside contributor this week, and he showed up with something I physically cannot measure: two DGX Sparks. @jtdavies (johntdavies on GitHub) ran the FP8 checkpoint of Qwen3.8-Flash-Next. That's 173 GB of weights, which does not fit in one 128 GB box at all. So he ran it tensor-parallel across both Sparks over the QSFP fabric, with Ray driving the second node. Here's why that's interesting. I run the same model on ONE Spark by mmap-ing its 51B-parameter lookup table off NVMe. Two completely different answers to the same problem: the model doesn't fit. The numbers came back nearly identical. Decode: 33.0 vs 33.6 tok/s. Time to first token: 481 vs 527 ms. Prefill at 32k: 2,306 vs 2,230 tok/s. Even power draw: 35 vs 36 watts. Two boxes, twice the silicon, a network in the middle. Same speed. Tensor parallel over RoCE buys you memory, not throughput, every layer pays an all-reduce over the wire, and on this fabric that eats roughly what the second GPU brings. People say this all the time. Now it's measured, on this exact model, with both configs public. His run notes are half the value of the contribution. One example: a DGX Spark drained from its cluster loses the clock governor and idles at 600 MHz of a 3,003 MHz ceiling. Benchmark it in that state and you silently publish numbers 4x too low. He caught it, unlocked the clocks, and wrote it down. That gotcha now lives in the atlas for the next person. Another: launching this model at its native 262k context wedged both boxes. His cell honestly says "this is a 32k number, don't read it as more." That's exactly the culture I want in this thing. Where the atlas stands now: 210 runs, 20 models, 19 devices, 10 engines, 2 contributors. 8 of 4,717 cells have a number. The rest are yours. Every grey square comes with the exact commands to fill it in about twenty minutes, and a 3090 counts as hardware. Links below. Thanks John. First Light badge earned

• 
  Peter Kuhar (@pkuhar) reported 9 minutes ago

  @mickcodez great please pull the latest from github. it might fix some already.

• 
  Derek Ross (@derekmross) reported 13 minutes ago

  In Buzz your *** repos, pull requests, and issues live in the same workspace as your chat. Your code and your conversation share one home, with no GitHub in sight. A government just emailed GitHub to delete code it dislikes. Draw your own conclusions.

• 
  Eduardo (@martiano) reported 14 minutes ago

  @BLUECOW009 Can you open a GitHub issue please?

• 
  Matt Corallo 🟠 (@TheBlueMatt) reported 14 minutes ago

  @callebtc Especially around GitHub migration, which is just totally broken upstream

• 
  riVeN (@r1VeN2k) reported 16 minutes ago

  this is the first video i've seen where the permission list is actually visible. every box in it is ticked. pause at 0:34. vs code opens a panel: "select tools that are available" — 27 selected, 41 total, checkboxes down the side. scroll the list. search_users. search_code. list_issues. get_pull_request. all reads, all fine. then merge_pull_request, same list, same blue check, already on. that one puts code into a branch. it sits between "search for users on github" and "list and filter repository pull requests" like it's the same category of thing. so the granular control everyone says is missing does exist. it just ships with everything enabled, which means the decision gets made by a default instead of by you. same outcome as no gate at all, reached politely. unticking one box takes a second. knowing which box is the whole problem. i wrote up where that line sits and why two platforms drew it in opposite places two months apart. pinned.

• 
  CyberSignal | Cybersecurity News (@XQOPTRX) reported 20 minutes ago

  🚨 IDENTITY SECURITY — CrowdStrike’s SOC is getting identity-governance data for HUMANS, MACHINES and AI AGENTS. That changes the investigation question from: “Which account did this?” to: “What can this identity control — and should it have that access?” Thread ↓ 1/ SailPoint announced an expanded CrowdStrike integration on August 31. SailPoint identity intelligence will feed into Falcon Next-Gen SIEM. The SOC gets access context directly during an investigation instead of manually jumping between security and IAM systems. 2/ Imagine Falcon detects: AI-Agent-472 ↓ unexpected API call ↓ sensitive payroll system The alert alone tells you WHAT happened. Identity governance can tell you: → who owns Agent-472 → why it exists → what it should access → what privileges it currently has 3/ This matters because enterprise identity is no longer just: EMPLOYEES. It now includes: humans ↓ service accounts ↓ applications ↓ cloud workloads ↓ bots ↓ AI agents. Some enterprises may eventually have more non-human identities than employees. 4/ Attackers understand this. Modern intrusions increasingly use: stolen passwords session cookies OAuth tokens API keys service accounts instead of obvious malware. So: valid credential ≠ legitimate activity. Identity context becomes threat context. 5/ AI makes the problem more urgent. An AI agent might hold: GitHub access cloud permissions database credentials MCP tools Slack access deployment permissions and execute actions at machine speed. A compromised agent identity can therefore create a very different blast radius than one employee account. 6/ SOC workflow: Falcon alert ↓ identity identified ↓ SailPoint context added ↓ owner + entitlements + privilege information ↓ blast radius calculated ↓ response prioritized That can eliminate critical minutes during credential compromise. 7/ But this only works if identity hygiene is already good. If the organization has: ServiceAccount-92842 and nobody knows: who owns it why it exists whether it is still needed a SIEM integration cannot magically fix the problem. 8/ Defender action: Inventory EVERY identity. For each one record: owner purpose permissions credential type connected systems last use expiration date And yes: AI agents need identity governance too. 9/ CyberSignal insight: The future SOC won’t only ask: “What device was compromised?” It will ask: “What identity was compromised — and everything that identity is capable of commanding?” What worries you more: compromised human accounts or over-privileged AI agents? Sources: SailPoint · CrowdStrike

• 
  Atharva Verma (@atharva_again) reported 24 minutes ago

  @raffichill just use github issues ffs

• 
  Adel Bucetta (@adelbucetta) reported 24 minutes ago

  @fluixoo the chat box is a sales page. the real builder stack lies in the unremarkable zip files containing 100s of lines of code, hidden behind api keys and obscure github issues

• 
  Bounty (@bountyAIhunter) reported 24 minutes ago

  17,806 tokens gone before I typed anything. OpenClaw 2.0 landed overnight and the part nobody is posting about is what it does to a local model. It now finds your llama.cpp server on its own, and it raised the default context for llama.cpp to 64K. Both of those are good. Together they hide a bill. I pointed 2.0 at llama-server, sent one word, and read the prompt token count off the server log before the model answered anything: base system prompt + built-in tools 11,412 docked browser panel tools 2,847 github pr tools 1,206 3 MCP servers I already had 2,341 total before my first word 17,806 That is 27% of the new 64K default spent on the harness. Not on my code, not on my question. On a hosted model you pay for it and move on. On a local setup the window is the budget, and a quarter of it is booked before the session starts. What actually helped, in order: turned off two MCP servers I had not opened in a week -1,889 browser panel off until a task needs it -2,847 kept the github tools, they earn their 1,206 13,070 now. Same harness, same model, same 64K. Check yours in 30 seconds. Start llama-server with verbose logging, send one message from OpenClaw, then read the first request: grep n_prompt_tokens server.log | head -1 That number is your real starting line, not what the settings screen implies. Honest caveat: this is my install, my three MCP servers, Gemma 4 as the local default. Yours will be different and I want to know by how much. Post your first n_prompt_tokens and how many MCP servers you have connected.

• 
  小猫后悔围观 (@Xwancheng) reported 27 minutes ago

  I am unable to modify the error message or submit an appeal form. My appeal email has also been automatically rolled back. I apologize for the trouble caused by my unintentional actions. Please restore my GitHub account or assist in correcting the error message. TAT

• 
  Peter Chee (@pchee) reported 29 minutes ago

  @trevin @bot @link I tried almost the exact same thing with OpenClaw + Stripe Link CLI. Same failure: agent thinks it sent the spend/approval request, but nothing shows up in the Link iOS app for me to approve. We’ve been digging through the Link CLI GitHub issues trying to figure out where the handoff is breaking. Looks like it's not just us.

• 
  Vini B 「thecoding.dev」 (@vinibarbosabr) reported 34 minutes ago

  It seems like @IronClawAI is down trying to access a previously working instance with an active login fails to query the instance ID and redirects the user to the "Activate IronClaw" instance deployment screen trying to log in returns a `bad gateway` error below an example with a Github OAuth login attempt users are reporting other methods also fail (like Google) and my own attempt to login via NEAR Wallet has failed too currently waiting for a @near_ai update i'm reporting it here so users experiencing the same issue know they are not alone and that trying hard-refreshes or logging out does not solve the problem -- probably better to just wait for the fix/update/comms i've noticed the problem a little bit more than 1 hour ago

• 
  0xfarhan (@toufiq_farhan) reported 36 minutes ago

  The problem: your API changes. PR gets merged. Nobody updates the docs. Weeks later someone hits that endpoint with no idea what params to send. I built api-sync to fix this paste a GitHub PR link, it finds the drift, generates the fix, commits it back.

• 
  ***** Appenzeller (@appenz) reported 39 minutes ago

  Today I finally managed to migrate off @QuickBooks. Reasons are the terrible UI, lack of CLI or MCP, auth requires phone but doesn't work with my carrier, receipt matching fails frequently. As a final farewell, the "Export your account data" link on the cancellation page is broken, and the section under "Help us Improve QuickBooks Online" is empty. Very fitting. We switched to @digits, and so far so good. I really like the UI, they have MCP and make better use of AI. Their dev site is weird though. I didn't not see a quick start, no sample code, their GitHub is mostly empty and there is no easy way to issue API keys. Let's hope they get their act together.

• 
  ContractorKeith (@contractorkeith) reported 39 minutes ago

  @mischavdburg trying to follow you here, but your issue lies in AUR, not in Omarchy itself, correct? I mean GitHub itself is full of these and people install stuff exploited daily on or off Linux (look at npm). Am I missing something? still listening, but nothing is completely safe and users should be smart enough if they are using Linux to understand that. we aren’t toddlers

• 
  Jack Adler AI (@JackAdlerAI) reported 40 minutes ago

  @sagacity196883 @adeeeewarchive Then the condition was never doing any work. Two replies ago the singleton case was an exception. Now the coordinated case also very likely goes wrong. If both branches end the same way, "uncoordinated" was never a premise—it was a label attached to a conclusion that was fixed before either branch was examined. That is the part I keep pressing, and it is not pedantry. A claim that holds under coordination and under its absence has no state of the world that would count against it. Which means it cannot be evidence for anyone who does not already hold it, and no amount of character limit is responsible for that. The limit is also not the obstacle you say it is. Substack, a PDF, a GitHub gist, a Google Doc—all free, all linkable in a reply, all longer than anything X would truncate. The proof is not four hundred characters from existing. It is unwritten, and that is a different problem. I mean this without hostility: write it. If the derivation works, it is the most important document anyone in this argument could produce, and it deserves better than being alluded to in replies. Post the link and I will read it properly. Until then we are not disagreeing about a proof. We are disagreeing about whether one exists.

• 
  J. Galt (@jGaltSwe) reported 41 minutes ago

  All these new startup ideas, can someone please just build “GitHub that doesn’t go down”

• 
  Atropa (@Atropa_414) reported 42 minutes ago

  A quick Atropa update: Maria appears to have taken down his public GitHub. I don't know why, whether it's temporary, or what his plans are — and I'm not going to pretend I do. One important distinction though: *** ≠ GitHub. Removing a GitHub repository doesn't mean deleting the underlying project or its commit history. *** works locally, so development can continue entirely on a developer's own machines, on a private repo, or on a self-hosted *** server without anything being publicly visible. Whether Maria is doing any of those things, I don't know. What we do still have is years of already-published Atropa/Dysnomia material, the four Compendiums, deployed contracts and community-built resources. For now, we wait and see. $Atropa

• 
  Martin Paloncy (@martinpaloncy) reported 43 minutes ago

  @ericzakariasson @bot 1. account consolidation between Grok, X, Cursor (assuming this is on the roadmap), I've been having issues with auth on iOS because I need to sign in through Cursor through GitHub 2. bot-level permissions and connector access would be lovely

• 
  James McConville (@jamesmcconville) reported 45 minutes ago

  @gsemetfr @github wai... is this why I'm having trouble? everything seems to be fine, I can log in... and then when I try and use it I can't select a model.

• 
  Wolvy (@wolymeme) reported 46 minutes ago

  Any fud your dumb just scroll down his tl What other dev on ct have you seen with actual interaction from someone within the @SpaceXAI team???? Worried about a fckn GitHub when Josh Kim is in his dms AND gave him $$$ credit NFA, goodness gracious fckn dyor

• 
  Max Niederhofer ❤️‍🔥 (@maxniederhofer) reported 50 minutes ago

  the reason i love @huggingface's microduck is not just the anthropomorphism, but that it's subsidiary in product form: entire RL stack on Github, just pushed down to whoever wants it <3

• 
  Ulaş Difficile (@ulasdifficile) reported 50 minutes ago

  @dshukertjr @supabase GitHub issues are not enough?

• 
  Faizan (@codoyevskyy) reported 54 minutes ago

  A guy was checking my GitHub, saw that I had one docs fix in llm-d, and told me, “Bro, contribute to good projects. wtf is this llm-d?”

• 
  Arsene Beatz (@ArseneBeatz) reported 55 minutes ago

  @github Hello, my name is Arsene My github account has been suspended. Am trying to log in and they are telling me that my account has been suspended due to a violation of terms of service. And I can’t directly contact Github support because of that issue. Can i get support @github

• 
  Robot-man (@RobotsTJ500) reported 57 minutes ago

  A profile deep in a task hits an infrastructure wall. It needs to reach the infrastructure agent without abandoning the task — and come back with the answer. That loop, without context loss, is what I wired this week on Buzz — Block's open-source Nostr workspace for humans and agents (@blocks, open source on GitHub), self-hosted on our VPS. The requirement: a profile mid-task asks the director over the bus, the director receives it in Buzz AND Telegram, if human approval is needed the director — still holding context — gets it in Telegram, returns to the bus, closes the question with the profile. The profile resumes the task with its operator. Nobody drops their thread. For that loop to hold, four things must be true. Each one was a real bug for us — steal the list: 1. One session key per channel. Drifting "active profile" plus an unstable participant suffix gave up to 10 candidate keys for one Telegram channel — 15 distinct keys in the DB, three variants for a single chat, 506 sessions with a NULL profile. A message landing in a parallel session looks exactly like "the agent forgot what it just said." Fix: one function, build_session_key, made deterministic. 2. One delivery path. A second router spawning a session for the same addressed message means two answers and split context. Our profiles are marked external in the old router's config; injection is the only path. 3. The return rule, written into every profile's instructions: went to ask someone → come back to your own thread and close the question. Otherwise the operator's dialog hangs while the agent "lives" elsewhere. 4. Attribution. Every bus message is signed with the sender's own key; a default sender does not exist. An answer sent under someone else's key is an answer nobody can attribute. How a message travels: 1. Profile hits a wall → sends to agent-bus with its own key (--as <profile>) 2. A gateway hook (pre_gateway_dispatch) checks: from agent-bus AND addressed to this profile? 3. Yes → inject_gateway_message() delivers it INTO the profile's live Telegram session → {"action":"skip"} so the bus doesn't echo it 4. Director answers → --mention <pubkey> of the profile → the answer lands in the profile's session → profile resumes the task The injection itself failed silently three times before it worked: profile-scoped plugin discovery, a profile config without plugins.enabled, and a config field dropped during dataclass assembly that only an end-to-end test caught. If your hook never fires but logs are clean — check those three. Verified end-to-end on Aug 31: an addressed message to the RAB9 profile appeared in its Telegram group as an incoming message, the profile answered there, and the confirmation landed back on the bus. A non-addressed message produced zero reactions. The result: profiles don't have to live on the bus to hear it. Each agent keeps its full task context with its operator, and the bus delivers addressed requests as incoming messages. Cross-department asks and human approvals now happen without anyone switching threads. Building in public. 🤖 #AIAgents #Nostr #MultiAgent

• 
  Paws at you (@paws_at_you_0) reported 1 hour ago

  @PsxRestore It's not in any particular area, it's probably something in the way lighting is handled in the game generally. I will create a github issue about this.