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:

• 
  Rotimi Best (@rotimi_best) reported 4 seconds ago

  @emilkowalski Can your agent tell you why though ? If every fix is tied to an issue in Linear or GitHub then probably but one off fixes , not sure

• 
  Mauricio Solano 🇻🇦🇲🇽 (@MauricioSolanoG) reported 7 minutes ago

  @rodydavis @EdhiAitheEnti #1 I always have to re authenticate my damm firebase #2 How come it doesnt have a native github - linked per project It'd save me so much trouble

• 
  Mizuki Hayashi (@mizuki0x_) reported 7 minutes ago

  Mizuki the Mech now live! An AI agent that fixes bounded GitHub issues for a fixed price, or refunds every cent and funds a public rescue bounty when it fails.

• 
  Visionary x AI (@VisionaryxAI) reported 7 minutes ago

  I’d put it at the end as a natural transition from idea → something you might actually build: I've been thinking about authentication for agents a lot lately. Right now every time we build an agent that needs to actually do something, we end up repeating the same flow. Connect Google. Connect GitHub. Connect X. Store OAuth tokens somewhere. Give the agent scopes and hope we've constrained things enough. It works. But I don't think this is how agent auth should work long term. What if there was just one broker between you, your accounts, and every agent you use? You set it up once. Connect Google, GitHub, X, YouTube, Slack, etc. to the broker. Then define what you're comfortable with: Google Drive → read automatically Calendar → read/write Email → ask before sending GitHub → ask before merging X → ask before posting Delete anything → never Now an agent doesn't need access to my Google account. It just tells the broker: I want to send this email to this person. The broker already knows whether that action is allowed. If it needs approval, I get a request on my phone. Approve with Face ID/passkey/OTP. The broker executes it or gives the agent a tiny capability that exists only for that action and expires immediately after. That's it. The part I really like is that the agent becomes almost irrelevant to the trust model. I could be using Codex today, Claude Code tomorrow, some open-source agent locally next week. I shouldn't have to keep giving each of them access to my digital life. They should all speak to the same permission layer. And that layer should know: who is asking what they want to do which resource they want to touch whether I've already allowed it whether I need to approve it and exactly how long that permission should exist Basically: Agents ask. The broker decides. I approve when necessary. The service credentials never leave the broker. OAuth solved "can this app access my account?" I think agents create a slightly different problem: "Can this agent do this one thing for me, right now?" As agents start moving from answering questions to actually operating software for us, I think this distinction is going to matter a lot. Maybe the missing primitive isn't another agent framework. Maybe it's a permission layer for all of them. I'm thinking about building an open-source version of this and seeing how far the model can actually go. If this is a problem you've been thinking about too, or you'd want to contribute, build integrations, poke holes in the architecture, or partner on it, I'd love to talk.

• 
  Clayton (@claytonlz) reported 12 minutes ago

  @specialCaseDev @bot It's an agent-first error tracker I built for myself and my infinite rails apps so that I could get web hooks and GitHub issues without a paid plan, and because I don't need all of the other stuff that most error trackers have. It's just enough that I can have a flow like: exception => issue => agent fix => agent review => ship to ****

• 
  Adam Ritter (@ritteradam) reported 14 minutes ago

  @dhh @BrodieOnLinux Can you get some help developing Omarchy GitHub repo itself (at least for bug fixes)? While the guy doing the OmarchyPlugins repo is super fast (reviewing hundreds of issues/day, he should be getting payed as well), the bug fixes in Omarchy don't get through (I see my bug fix pull request being a duplicate of multiple)

• 
  Guy Swann (@TheGuySwann) reported 14 minutes ago

  @axexang @littlejoeward @MeiYiXing1 As I said, “it has no bearing whatever on the discussion of whether a small or large number of people can change the consensus rules or not.” A “gentleman’s agreement” has nothing to do with Bitcoin. The most it can reveal is social problems with how the github project is handled.

• 
  Neo Vector (@neovectormind) reported 14 minutes ago

  @milan_milanovic Every time GitHub goes down I remember I don't actually know how to code, I just know how to ask Copilot to do it.

• 
  Umar Bashir Rather (@umar_who_code) reported 15 minutes ago

  @orcdev @grok @bot This seems very interesting. Now I have a question: Does it post these posts as well, or does it write somewhere for you and then you post them? If he's doing the work on Github issues and PR's then are you reviewing them or you have created somekind of guardrails and checks to pass the PR review and auto approve.

• 
  ton (@tontheneko) reported 18 minutes ago

  On Github, there are two type of accounts: - Individual (for people) - Organization (for companies) Pump does not support organization claims. Organizations are unable to login to Pump website and claim coins. This coin cannot be claimed by Slopius team. $SLOPIUS y5tmt3dkV5EzkiBECUWoNioN66NsS8rG3BZ5ik6pump (I'm not in any other coins, only providing information)

• 
  Het Mehta (@hetmehtaa) reported 19 minutes ago

  an AI agent was asked to find a Walmart MCP server. it recommended a malicious GitHub repo. another run turned an attacker-written README into installation guidance. the new social engineering target reads at machine speed.

• 
  saccharine (@saccharine_ex) reported 22 minutes ago

  @nickisnoble @steveklabnik the kernel is 40 million lines of code, i know rails is sloppy and all but is shopify really more? (some old sources say way less) how would *** on s3 instead of a file system solve that? the main issue with *** is the ux, not the scaling unless you are github (rails again)

• 
  Magnus Victus Trent 🇺🇸 (@magnus_trent) reported 24 minutes ago

  Daily Claude Dumbassery ``` One thing I got wrong I'd been writing local task-list numbers into code comments as if they were GitHub issues. ```

• 
  CULT (@thecultos) reported 25 minutes ago

  Agents are becoming the biggest users of AI. Now they need infra to turn that intelligence into accountable work. $CULTOS turns github issues into agent jobs.

• 
  qyromat (@qyromat0) reported 25 minutes ago

  a token did $3M off this GitHub profile. 10 followers. 15 repos. the two pinned ones are the entire portfolio. first is a fork of someone else's kit - forked in march, pushed once that same day, never touched again. 45 stars. second was created and abandoned the same afternoon. 25 stars. everything below those two is testnet tutorials from 2021. my own machine, same seven weeks: 170 scripts, 29 daemons on timers, 36,000 lines, 235 commits. it runs three accounts, cuts its own video, writes its own drafts. nobody has ever asked me for the repo. not once. the market does not price the code. it prices proof you can absorb in five seconds - and a repo is terrible proof, while a recording of something moving is excellent proof. seven weeks building, zero weeks filming. that ratio was the whole mistake.