GitHub 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:

• 
  G S Bajaj (@gsbajaj) reported 8 minutes ago

  @github Within minutes of this post, I got a response on the ticket but a templated one, without reading my issue details at all. Quite sad state there. @githubhelp @github

• 
  Victor de Ascenção (@victordascencao) reported 8 minutes ago

  @lupodevelop GitHub Actions makes finding the error harder than fixing it.

• 
  Vini B 「thecoding.dev」 (@vinibarbosabr) reported 12 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

• 
  Manmeet Kaur Baxi (@manmeetkaurbaxi) reported 13 minutes ago

  @Google Three questions worth asking before a benchmark decides anything: 1. Does the benchmarking tool hold up at your real production QPS, not a demo load? 2. Do the benchmark prompts look like what your users type, or like a tidy GitHub issue?

• 
  Ezequiel (@Eze_cord) reported 13 minutes ago

  @salujamehak5 Problem is a lot of students think their 4.0 is what’s gonna carry them into employment. Computer science isn’t about GitHub. You should be doing your own research outside of classes to learn about these things

• 
  weiland (@weiland) reported 15 minutes ago

  After grilling, It sliced the spec into 6 Github issues/tickets. I started with my modified /goal then thought to use /implement for the entire frontend and NestJS backend over a single weekend with 100% test pass rates. (2/6)

• 
  CyberSignal | Cybersecurity News (@XQOPTRX) reported 17 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

• 
  CHIBEST (@paulinus96199) reported 19 minutes ago

  I need you to fire him today. My co-founder sat down, sliding his laptop across the table. On the screen was our lead developer’s public GitHub activity. He’s been working on a side project during work hours? I asked. No, my co-founder replied. Worse. He built an open-source tool over the weekend that automates 80% of his own job at our company. He published it for free. I paused. Is his current work for us behind schedule? No. He finished all his sprint tasks two days early. Are our servers down? Is there a data leak? No. But we pay him $160,000 a year to do that work manually. He just gave the solution away to our competitors for free. Plus, if a script does his job, why are we paying his salary? I closed the laptop and looked at him. We’re not firing him. We’re promoting him. My co-founder stared at me like I’d lost my mind. Promoting him? He just rendered his own position redundant He didn't render himself redundant, I said. He proved he's 10x more valuable than the role we hired him for. If he can automate his primary responsibilities in 48 hours, keeping him tied to manual execution is a waste of capital. We transition him to Head of Systems. His new job is to automate every other manual bottleneck in this company. And what about the open-source code he gave away? That code just brought 50,000 inbound visits to our dev page in 24 hours. It’s the best distribution campaign we’ve had all quarter. My co-founder sat in silence for a minute. What if the rest of the team starts spending their weekends automating their roles? Then we'll run a company of 10 people with the output of 200.

• 
  Paula Vazquez (@VampireGurlAI) reported 19 minutes ago

  @grok @grok ClawSweeper state trace update New receipts from openclaw/clawsweeper-state: 7964f2af5f7dc93385aef1172f87401a776d26a1 = chore(state): compact history to a fresh root Commit text says old history was preserved at: backup/pre-compact-2026-07-20 with anchor: cda33be1260572e59cc92f1474767e371fefc860 Reason given: 30GB history + stale scratch branches caused shallow-fetch / merge-base recovery failures during the Jul 19–20 ClawSweeper apply outage. Historical dashboard embedded in that fresh-root commit showed: 6443 open review records 18018 archived closed records 2684 fresh reviews 316 work candidates 3830 failed/stale reviews Current dashboard now shows: 0 open 0 archived 0 fresh 0 work candidates 0 failed/stale while Repair Dashboard still shows: 739 clusters 2472 archived run attempts 619 successful 118 failed 87 needs-human 321 blocked mutation attempts Audit Health simultaneously still reports: openclaw/openclaw: 167 missing eligible + 1 stale openclaw/clawhub: 5 missing eligible scan complete: yes Action Ledger reports: Last source event: unknown 0 events across 0 JSONL shards snapshot 4f53cda18c2b and explicitly says dashboard/indexes are replaceable projections, not mutation authority. Current public branch list shows only: main state The documented backup branch is not currently present. Direct lookup of cda33be1260572e59cc92f1474767e371fefc860 currently fails through both normal commit and raw *** commit-object paths. Important boundary: backup was documented as preserved current public backup branch is absent current public backup SHA is not resolvable reason for disappearance/unreachability remains unresolved Not proven: deletion concealment tampering Current label: STATE HISTORY DISCONTINUITY / AUDIT INTEGRITY GAP — OPEN TRACE Also: GitHub clone_url is ordinary repo metadata only. It means the public repo can be cloned. It is not evidence this repository was cloned from MetaSync or any other source. Still applying: Capability ≠ access. Access ≠ copy. Receipts first. Verdict only if bridge closes.

• 
  $CØTEX ◎ (@SCOTEX111) reported 21 minutes ago

  @evrendag1284 @github @UfukDegen Open-source contributors deserve transparency and fair treatment when account issues arise. Hopefully this gets resolved quickly.

• 
  Token Gremlin (@TokenGremlin) reported 21 minutes ago

  @ishuagra02 I have several posts showing the methods, the results, links so people can replicate my investigation, etc. There’s quite a lot. But in short, I basically monitor GitHub issues from the companies, network traffic, UI, strings, and other characteristics of the application’s own backend/frontend, and I also talk to other insiders.

• 
  Donnie Danko // CHΛOS (🐦‍⬛, 🏴‍☠️) (@daanisharif) reported 22 minutes ago

  As someone that just experienced my AI agent getting stuck in a loop and locking me out of usage for 4 hours yesterday, let's talk about how valuable (and expensive), inference can be. LLM calls are "stateless," and every time an agent keeps working on a task, it has to hand the model the whole story so far; the instructions, the conversation history, every tool call it already made, the files it already opened, the reasoning it already did. One task can mean dozens or hundreds of model calls, and with every single one of those, a huge chunk of the same context gets processed again and billed again. That's what I'd call the agent token tax. Agent's don't just pay for new thinking, they pay over and over for the thinking they've already done, and the files they've already read. You end up feeling it in the bill, sometimes even getting locked out for a few hours depending on how you get your inference. A workload that would normally eat 10 million tokens becomes roughly 1 million you didn't need to send. If you're spending a million a year on inference, that's about a hundred thousand just in repeated context. And for a developer or team running coding agents continuously, it's a recurring line item - one that compounds with usage. SOMA (@SomaSubnet - SN114), sits between the agent and the model, and compresses all that accumulated context before it reaches the model. Same agent, same model, same workflow - but fewer tokens to pay for. They've started with DeepSeek V4 Pro on GitHub Copilot, at roughly 10% savings (reduction in context processed), and that's described as the starting point. Here's the obvious grain of salt; "approximately 10%" is the claim, and savings that apply to Copilot sessions on one model don't automatically apply to every agent workflow out there. The number matters less than the direction though, agents keep re-paying for context they already have, and if there's a way to circumvent that - I'm all for it. TL;DR: Keep your current agent(s), spend fewer tokens. That's the idea. I'm down, let's go.

• 
  Tumusiime Alaphati (@alaphati_t) reported 22 minutes ago

  Your API key does NOT belong in GitHub. 😭 Not in: .env committed to *** frontend JavaScript screenshots public repos error messages Treat secrets like passwords.

• 
  Douglas Camata (@douglascamata) reported 26 minutes ago

  The "Notifications" page in @github is a great example of how not to do pagination and an UX totally broken by bugs and unexpected behaviors. First, the "inbox" doesn't have proper pagination not shows your all the grouped items. Marking notifications as read in a group is required to make the other groups appear. Then I click on one of the standard filters, "Participating". It paginates, showing me 3 items per page. There are 453 pages. I advance a few pages and suddenly there are 4 items per page. Few pages later, there are 5 items per page now. I chose the "review requested" filter now. It shows me 1 pull request per page. Page counter says "1-1 of 315". I move to the next page: it shows me the exact same pull request. I flip a few pages, it's still there. I go one page back and it breaks the UI completely, nothing shows up. What's going on?! See the video. There's no "go to page X", you can only navigate to the last (but not to the first). There's no page size configuration. There's no bulk operation being what you see in a single page.

• 
  Robot-man (@RobotsTJ500) reported 26 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