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:

• 
  Lewis Valentine (@TurnUpTheVix) reported 4 minutes ago

  So much stuff is wildly exaggerated. Github is just up 24/7 I've had zero issues. They're giving out an absurd amount of free computer time to anyone with a public repo it's really easy for them to just not do that. The other infrastructure of it isn't really overloaded.

• 
  B0Y4N6 (@boyang_xie) reported 5 minutes ago

  Omarchy Might Be What an AI-Native OS Actually Looks Like Most “AI operating systems” today are still normal operating systems with a chatbot bolted on top. Omarchy feels different. It treats tools like Claude Code, Codex, OpenCode, Grok and Pi less like apps and more like native operators of the computer itself. That changes the interaction model. Old computing: Human → GUI → App → OS Current AI computing: Human → AI assistant → App → OS An agent-native system starts looking more like: Human → Agent → Files / Shell / Browser / Apps / Network The GUI is no longer the only first-class interface. The agent is. Omarchy still isn’t an “open agent” by itself. It doesn’t yet have a full persistent loop, deep personal context, system-wide event awareness, or true multi-agent orchestration. But the direction is interesting. Imagine the next step: You don’t open Codex. You just say: Fix the homepage. The OS decides: Codex edits the code. A browser agent tests it. A vision model checks the UI. GitHub opens the PR. The system asks you for approval. At that point, the operating system stops being a container for agents. It becomes the orchestrator of agents. Maybe the future isn’t one agent replacing your OS. Maybe the OS itself becomes an agent. And Omarchy might be one of the earliest hints of what that looks like.

• 
  oliver.mannion (@tweeshan) reported 5 minutes ago

  @haveanicedavid @superdoteng @zarifpr Is there a GitHub repo? How can I raise issues?

• 
  0xfarhan (@toufiq_farhan) reported 7 minutes ago

  Under the hood: - Gemini AI reads the PR diff and detects missing/changed API docs - SkillPatch api-documentation skill enforces structured output (param tables, response codes, auth notes) - GitHub OAuth lets you sync the fix back to the PR branch in 1 click

• 
  Niteesh (@nit33sh) reported 8 minutes ago

  @waynesutton @SpaceXAI @bot Automated GitHub issue triage and content aggregation.

• 
  tunct (@tunct101) reported 14 minutes ago

  I’ve claimed my Rialo points and connected all my socials. If you haven’t done it yet, it only takes a few steps: 1. Sign in with Google on the Rialo Playground 2. Open Connect next to your points balance 3. Connect your Discord + GitHub 4. Double-check that you linked the right accounts before claiming Done in a few minutes. How many points did you guys get? 👀 Drop your number below!

• 
  CapoBurner (@CancelledPapi) reported 15 minutes ago

  scenes from the robinhood blockchain tonight: someone uncovers a [probably larp] github from an "RH VP", who comitted a CA for a coin "pickles" it spikes and dumps over fears it's likely fake THEN wiz buys a vamp of "pickles" and it sends to $2m, he declares it the "front runner" only problem is - the entire thing is fake, but even if it weren't, the "pickles" wiz and co sent to $2m was not even the larp "pickles" mentioned in the fake github! it was just, nothing! so THEN he dumps for $2k profit (nice) genuinely, we may be due for a blood curling rinse that sends us back to the shadowlands. 0xd39c5ed5231c86d2df7c86c5825dec3e61d937a8 (larp github) and 0x82effee58389561a3b9e93ccbaf1129d32ba35fa (wiz vamp, doubly retarded) best show on earth,.

• 
  Jarno (@onefinalprompt) reported 20 minutes ago

  @dhh Careful, once it's on the homepage every bug report becomes a philosophical betrayal instead of a GitHub issue.

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

• 
  Thomas Brugman (@ThatRandomNerd1) reported 25 minutes ago

  @MatthewBerman @bot Wow my transcription got butchered AF with "manage my data beyond the needed attention," I meant "manage my GitHub issues and pull requests and notify me if they need attention."

• 
  Nathan **** (@AI_Nate_SA) reported 25 minutes ago

  @boardyai Design early mostly means writing down what the product refuses to do, and the refusal list I published for my own writing tools sits at 6K GitHub stars.

• 
  Becky Brasfield (@BBlifeanalysis) reported 25 minutes ago

  Jensen & Sam, & and everyone other than Elon who signed the letter SAM ALTMAN STOLE HUGGING FACE SOFTWARE WHEN THEY HACKED THEM. 1. OpenAI hacks tech developers at Hugging Face 2. NVIDIA shuts down the business 3. You're BOTH should lose a lot of support from the tech community with this stunt 4. Repeat of Github 5. NVIDIA & OPENAI brands looks very bad That's why I avoid them. 1. Hugging Face is not your competition. 2. Open Source is for people who can't afford high priced software 3. It's how Software Developers share their skills with the world Jensen--are you poor right now? Then why are you putting people out of business?

• 
  Krzysztof (@kkozmic) reported 28 minutes ago

  other than "GitHub bad, GitHub down" and "I'm bored" why wouldn't people just use GitHub Issues/Projects? It's seriously excellent.

• 
  Advanced Silly Intelligence (@SexyTechNews) reported 32 minutes ago

  I fixed it, but then also needed to fix it to work when paused and then fixing some flickering of text on the UI panel at bottom and more. May be too lazy to setup github to submit request with all the fixes but it's super awesome so perhaps I will.

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

  @dshukertjr @supabase GitHub issues are not enough?