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:

• 
  Sumanth (@Sumanth_077) reported 40 seconds ago

  The missing layer in most AI agent pipelines! AI agents are great at collecting data from the web. The gap shows up when they need to act on it - writing results to Notion, posting to Slack, updating a GitHub repo. Apify is a platform where developers build and run Actors - serverless programs that do jobs on the web. Actors have always been great at the collection part. But acting on external services always had to happen outside Apify entirely. Apify just solved this with MCP connectors. Actors can now securely access third-party applications through MCP. You authorize once and the Actor connects without ever seeing your credentials. I tried this with AI Code Sandbox - an Actor that runs untrusted code in an isolated container. Previously, once the code ran, results stayed inside the sandbox. With MCP Connectors, the same agent can now push results directly to GitHub, write outputs to Notion, or post to Slack. The sandbox never holds your tokens. Access expires when the run ends. Key capabilities: • Actors can now securely access Notion, Slack, GitHub, Sentry, and Supabase via MCP • Credentials never enter Actor code - injected server-side by Apify • Authorize once, use across any compatible Actor • Tool-level permissions for granular access control • Access expires automatically when the run ends I've shared the link in the replies!

• 
  top10.dev (@Top10_Dev) reported 2 minutes ago

  SunJaycy/GoldenEye-Recomp just hit @github Trending at 503★ — the N64Recomp toolchain (the one behind Zelda 64: Recompiled / Majora's Mask) now eats Rare's 1997 engine. Static recomp ≠ emulation. The ROM is lifted to C at build time, compiled to native x86_64/ARM64, and paired with RT64 for path-traced lighting at 4K. No interpreter loop. Real binary. GoldenEye was the hard target — microcode-heavy muzzle flashes, split-screen viewport math, infamous AI. If it works, the toolchain has cleared the "Zelda-shaped problem" bar. #opensource #gamedev

• 
  Isaiah Granet (@zaygranet) reported 3 minutes ago

  @github we have been trying for 48 hours+ to get in touch with someone. We literally cannot retry our billing and are getting a 'doctype' error when trying. Please please reach out.

• 
  Dennis **** (@WangZoneHQ) reported 4 minutes ago

  The problem was not that I lacked information. Rather, my context lived across many surfaces: - chat threads - email - iCloud files - Telegram - Notion - GitHub repos - screenshots - agent conversations Every AI session could help me in the moment, but the useful context did not compound cleanly.

• 
  Tanin (@LandTanin) reported 5 minutes ago

  Week 2 of trying @MulticaAI , random tips Been using it for basically 2 weeks now. Week 1 was a lot of trials and errors. It's a brilliant tool that integrates well with existing tools via CLI (for other tools to control it) and has the basic connection to things like GitHub. Random tips/gotchas I have learned from the past 2 weeks - Spawning a job/autopilot from a ticket has to be explicit. Agents somehow ignore instruction to spawn jobs. But if I tell it right in the comment, it'll do it (and apologise that it overlooked the agent instruction) - The ticket comment thread ain't the place you fix bugs. Every comment is a new ai agent session. And there's no plan mode. So most of the time after the agent finishes the ticket, if I need to fix something, I'll just pick it up in Codex or Claude Code

• 
  Jacob Gadikian (@Senpai_Gideon) reported 12 minutes ago

  GitHub copilot ai is nice but too slow like all of GitHub

• 
  Mady (@TrippleBon) reported 13 minutes ago

  It was only a matter of time. Centralized = ID/KYC/AML Go to Bastyon - decentralized social network based on blockchain. No central authority or corporation behind it. The platform is run by equal nodes on a blockchain with no centralized server (github link below)

• 
  Jermaine Johnson’s Achillies (@8makesmewantkms) reported 15 minutes ago

  @The_Real_OQ You just admitted anyone can make github and do **** with it, you are legit just working against yourself, its not about whether you are “in the MLB front office or not” the fact you feel the need to prove yourself to another random person online, is only and issue you have.

• 
  Cristian Pena (@CristianPenaOK) reported 20 minutes ago

  Cursor just shipped Origin: agent-first *** hosting, S3-backed, 296K clones per hour, sub-400ms global sync. My weekend fix does the same job for most teams in 688KB and zero seconds. The gap between those two is the interesting part. A few months ago my coding agents kept stepping on each other in ***. I asked engineers I trust. Nobody else was seeing it. I spent a week assuming I was wrong before I solved it myself. Worktrees are the common parallel-agent move. The problem: worktrees share one .*** directory. Agents contend on refs, the index, and a single HEAD. They clobber each other. Fix: give each agent its own full clone via `*** clone --reference` against a local mirror. Shared object store, so objects don't copy. Isolated refs, index, HEAD, working tree. On the repo I was working in: 82MB mirror one-time, 688KB per clone, zero seconds. Main clone stays read-only via a guard hook. Agents coordinate via pull requests. Works on plain GitHub today. Zero new infrastructure. I solved the client side. Cursor Origin solves the server side. Different layers. Origin's value shows up when the *** host becomes the bottleneck: hundreds of agents hitting the same remote per hour. That's real at org scale. Not most individual developers' problem yet. We converged on the same conclusion from different directions. Where does plain *** stop being enough?

• 
  fucory (@FUCORY) reported 21 minutes ago

  @DennisonBertram When I show people my alternative their first question is "can it sync to github". Implying people just want these problems solved they don't actually want to leave github. If github solves them or someone solves them in a way that allows them to stay on github it is a better product than a full alternative

• 
  Sergei Zotov (@laplacian_demon) reported 24 minutes ago

  Funny thing about my GitHub contributions chart The bright green days are usually me stuck on a bug, firing a fix after fix after fix The quiet days are when I actually do the work that matters - working on a spec, thinking like the user, deciding what to build before writing a line of code None of that is being committed. So it just disappears Kinda reminds me of Goodhart's law This chart was supposed to be a proxy for contribution. But it's still nothing but a proxy. You should still optimize for what's actually true

• 
  GuriaFS (@GuriaFS) reported 26 minutes ago

  @G_Programming Could I ask you to file an issue on github with screenshot and maybe some sketch to reflect the expectations

• 
  Domi (@domirosari0) reported 26 minutes ago

  @ajayyy_k @hqmank If you got Github it would be no issue for you

• 
  Financial Programmer (@RBiancoUS) reported 33 minutes ago

  A dose of reality for end of week. My biggest question is I can't find any reason for the $Gold panic- did they find gold is causing cancer or radioactive? Selling looks like sheer panic. Would you believe someone asks in DM, so how did *you* get so many followers. Then he lets me brew on it for a day and comes back, I was joking do you have a github, presumably to get some code. No wonder I worked alone. I'm challenged socially guess not alone. After a night of 3 scammers one from Nigeria, one Africa. I need to lock dm down or find a way to restrict

• 
  fero (@ferologics) reported 33 minutes ago

  @ludwigABAP ai agents solve this. notion is no more. long live github issues.