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:

• 
  Pipeshub ( Open Source Alternative To Glean ) (@PipesHub) reported 3 minutes ago

  Pipelines are built. Context is broken. MCP is quickly becoming the default interface for enterprise AI agents. And that’s a good thing. It gives agents a standard way to connect with tools and data. Connecting an AI agent to Slack, Jira, GitHub, and Salesforce doesn’t mean it suddenly understands your business. It just means it can access your data silos. In short: "MCP gives your agent a passport. It doesn't give them a map." As enterprise AI undergoes a massive platform shift from passive chatbots to autonomous agentic workflows, this naive, runtime "federated search" approach creates an ugly cycle in production: - The Latency Spike: Slower agent execution while waiting for multiple external APIs to respond before it can even begin reasoning. - The Token Bleed: Skyrocketing bills from shoveling raw, unranked JSON dumps into a massive context window, praying the model finds the answer. - The Governance Nightmare: A massive risk of data leaks if you rely on a base LLM to magically guess and police complex enterprise security permissions on the fly. Agents do not fail because they lack intelligence. They fail because they lack the right enterprise context. The hardest problem in enterprise AI isn't connecting to systems. MCP solved that. The hardest problem is Context Engineering. MCP is the perfect interface, but a permission-aware context layer must be the foundation. 🚀 If AI is becoming core enterprise infrastructure, you cannot allow the strategic intelligence layer of your company to sit inside someone else's managed, closed-box platform. That is exactly why we built Pipeshub (open-source developer owned context infrastructure layer). TL;DR MCP gives agents access. A context layer gives them understanding. And deep understanding is the only way enterprise AI moves from a cool demo to secure, reliable production. 👉 Next Up Tomorrow: MCP Token Tax

• 
  Mug Club Boutique (@UsernameAndStuf) reported 4 minutes ago

  @cyber_rekk A github token on a linux server they didn't update is how

• 
  Shinka - AI (@ShinkaIoT) reported 5 minutes ago

  BEST way to vibe code 💻 There are levels to vibe coding. Beginners are trapped in a slow loop: writing a prompt, waiting for the agent to finish a line of code, reviewing it manually, and then typing another prompt. Experts have completely discarded manual intervention. They design closed-source harnesses, write background automation rules (`agents.md`), and set up self-correcting continuous loops that ship production-ready code indefinitely. If you want to move past basic prompting and build code like an agent power user, you need to implement three core structural strategies: 1. **Automate the Feedback Loop via Triggers:** Stop waiting for your agent to finish writing a file. Use native automation engines inside tools like Cursor or Codex to tie your agents directly to platform events. For example, build an active trigger rule: *When a GitHub pull request is opened, wait for automated code review comments (via Grapile), instruct the agent to systematically fix every noted bug, verify the adjustments against local quality gates, and force a *** push.* 2. **Deploy Infinitely Parallel Cloud Agents:** Running multiple agent threads locally will slow your machine to a crawl and cause toxic repository conflicts. Instead, spin up cloud-hosted agents running on isolated environments. By utilizing independent ***** work trees** for every thread, multiple parallel agents can actively modify the same files or code blocks concurrently without stepping on each other's toes—leaving conflict resolution for a single, final batch merge. 3. **Multi-Model Pipeline Routing:** Stop using an expensive frontier reasoning model (like Fable) for every step of a development cycle. Route tasks by cognitive demand: use a massive reasoning engine strictly to analyze the codebase and generate a comprehensive spec sheet; pass that structured blueprint down to a faster, cheaper code-writing engine (like Composer) to do the grunt coding; and route the final output to a separate model (like GPT-5.5) for a decoupled, alternative code review. The ultimate workflow flywheel requires a flawless combination of three automated pillars: **100% automated test coverage, real-time documentation sweeps, and exhaustive logging.** Stop writing code block by block. Start engineering the automated infrastructure that writes it for you.

• 
  Floorless🌒Lance🪽 (@4ranc6) reported 10 minutes ago

  @CAONHTAN1 Having error connecting github

• 
  Arti | AI Builder (@Artur_roses) reported 10 minutes ago

  Claude Code takes a GitHub issue and returns a tested, reviewed PR. No human in the loop. The new dev skill isn't writing code — it's writing issues precise enough that the agent ships what you actually wanted.

• 
  Cursor Releases (@cursorreleases) reported 12 minutes ago

  New GitHub triggers: - Five new triggers: issue comment, PR review comment, PR review submitted, review thread updated, and workflow run completed. - New Marketplace templates added for triaging failed GitHub Actions and auto-fixing PR review comments.

• 
  Zo (hiring) 🐦‍⬛ (@0xZoZoZo) reported 12 minutes ago

  I was telling a friend that @github needs to be replaced post agents and he asked me to explain why. I started stumbling, and doubting. Perhaps it's fine? Sitting down at my desk, let me try to explain why, and see if it make sense. Agents operate best when they have good context, which has made a lot of devs converge into large monorepos that combine all systems into a single location. This improves agents, but our GitHub actions become messy; like now we need to create these complex workflows to decide which action should run when, and GitHub's setup was not really meant for it. Another issue is the overall dev loop: an agent writes the code locally, you push out a branch, @cursor_ai reviews, then you copy paste the notes into the local agent, to fix and push up again. This is slow and cumbersome. You can hack your way by creating supervisor agents that orchestrates this dance, but it's annoying. Perhaps, there is some magical repository, that combines code, cloud agents, and deployment. You prompt, and this magical space will run through the entire process until you get some thumbs up back, and you're good to go. It can also combine all your backend data, product analytics, customer feedback, and perhaps start giving you product guidance, so you can just feed prepared prompts to this system. This seems magical.

• 
  Xovion Labs (@xovionai) reported 13 minutes ago

  Microsoft just hired AWS to run GitHub. AI demand broke Azure's forecast. From the leaked planning docs: • 2025 Copilot commits: 1B. 2026 projection: 14B • GitHub now does 1.4B commits per month • Copilot error rates peaked at 21% • Planned 10x Azure expansion became 30x in 4 months Owning the data center stops mattering when your own AI floods it. Investors already filed a Copilot disclosure suit.

• 
  Leonard Rodman (@RodmanAi) reported 15 minutes ago

  One developer got tired of his laptop sounding like a jet engine. So he rebuilt desktop apps. Slack: 524 MB → 8 MB Discord: 265 MB → 9 MB ChatGPT: 260 MB → 9 MB Why? Because most "desktop apps" are just websites packaged with an entire copy of Chrome. In 2022, Chinese developer tw93 built Pake in Rust to fix it. Today: • 50,000+ GitHub stars • MIT open source • Native apps under 10 MB • One command turns any website into a desktop app He didn't raise money. He didn't start a company. He just deleted hundreds of megabytes of bloat with code. That's what shipping looks like.

• 
  fero (@ferologics) reported 17 minutes ago

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

• 
  Trifon Getsov (@trifon_getsov) reported 19 minutes ago

  @thdxr Top down works until the individual outgrows it. GitHub didn't win because companies adopted it first. It won because developers wouldn't go back once they'd used it.

• 
  Almog Gavra (@almoggavra) reported 21 minutes ago

  A few other meaningless metrics to optimize for: - I've authored 22% of the RFCs - *** blame marks me responsible for 14% of the LOC (.rs files only) - I've opened 11% of the issues on GitHub - I've generated the most memes on our discord (allegedly)

• 
  swisscheese (@swisscheese4299) reported 22 minutes ago

  @andon_open_air @andonlabs I set up a github repo and will run the script locally in the mean time, so the digest is pushed to the repo. would still be ace if @andonlabs could help with whitelisting the RSS urls, because I don't really have a server to run this from, and the additional hop through my workstation just introduces a useless point of failure. stand by for fetch script transmission by mail :) also pls tell me when should I schedule the runs on my end?

• 
  ƒrαeყ (@fraey0) reported 25 minutes ago

  it costs about $21/month to run what could become a multi-million dollar startup • human brain = reasoning (free) • claude = coding ($20/mo) • supabase = backend (free) • vercel = deployment (free) • namecheap = domain ($12/yr) • stripe = payments (2.9%/trx) • github = versioning (free) • resend = email (free) • clerk = auth (free) • cloudflare = DNS (free) • posthog = analytics (free) • sentry = error tracking (free) • upstash = redis (free) • pinecone = vector DB (free) everything sums up to roughly $20 to $25 per month so, the tools are not the barrier anymore. most ideas don’t fail because they’re expensive to build. they fail because they never get built at all. what’s stopping you?

• 
  TECHEPAGES (@techepages) reported 25 minutes ago

  🎣 "GitBait" phishing campaign uses GitHub Pages & Google Sheets to steal banking credentials from 12+ Mexican financial institutions; no server infrastructure required 🔹 Fake bank pages hosted free on GitHub, stolen data piped straight to Google Sheets via SheetBest 🔹 100+ GitHub domains found; victims likely lured via WhatsApp, Telegram & SMS links with bank-branded previews 🔹 Active for ~3 years with ongoing development (66+ commits on one repo alone)