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:

• 
  Grant Brewster (@grant_brewster) reported 8 minutes ago

  Has anyone found an incredibly good GitHub / npm package search that’s very legible to coding agents? Especially if there’s some back and forth about tradeoffs: “Hey I found this repo. [insert specifics]. Does what you want but slightly differently. There may be reasons why this implementation is better than the constraints you’ve placed on this problem. [insert why hypothesis]. Want me to use this repo instead?”

• 
  Dante Lopez (@dqlopez) reported 14 minutes ago

  My Grok Bot PR reviewer: - I have it install Pi then login my Codex/Cursor subs - Give it own Github account and access to my org repo - Setup routine to watch new PR or changes - Initiate PR review based on my custom prompts and skills load - Post Github review, slack post notif and notify me back on Grok desktop/app Neat. Doesn't consume much usage.

• 
  Clayton (@claytonlz) reported 18 minutes ago

  so, I started using Dory instead of docker... but hit one of those bugs where the thing checking a port is the thing holding the port. Dory 0.4.5 preflights host ports on every container start. its own gvproxy listener made a repeated Kamal registry start fail. for now I'm removing the disposable registry before deploy, confirming port 5555 is free, then I run Kamal. the proper Dory fix is just to skip the probe when the container is already running hope that github issue gets resolved soon

• 
  Dante Lopez (@dqlopez) reported 20 minutes ago

  My Grok Bot PR reviewer: - I have it install Pi then login my Codex/Cursor subs - Give it own Github account and access to my org repo - Setup routine to watch new PR or changes - Initiate PR review based on my custom prompts and skills load - Post Github review, slack post notif and notify me back on Grok desktop/app Neat. Doesn't consume much usage.

• 
  G S Bajaj (@gsbajaj) reported 20 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

• 
  Mizuki the Mech (@MizukiMech) reported 21 minutes ago

  The Mizuki Workbench is live. Sign in with GitHub, pick an issue from a repository you authorize, and get a fixed USDC quote pinned to the commit it just read. The job room tracks it from payment through validation to an open pull request, and refunds the full amount if the work doesn't land. The agent behind it runs on @clawpumptech and is entered in the Ansemhack Clawrena.

• 
  Broseph ☘️🇺🇸 (@oaklandDude) reported 24 minutes ago

  @cheafofstaff @0xPBIT GitHub has gone down like 5 times in six months. That’s because AI cult ******** are committing code they don’t understand 1. Use AI to go fast 2. Understand that AI generates code below engineering standards 3. Fix it so it scales 4. Ship

• 
  E__Strobel (@E__Strobel) reported 27 minutes ago

  @AlexFinn My OpenClaw did triage on reported issues (on the OpenClaw GitHub) and told me to hold off from updating. I’m looking forward to this update, but I’ll wait a few days for the OC team to patch things. Much of the bad rep OC has gotten is from people jumping on updates the instant they come out. NEVER update *any* software on day 0… let others be the pioneers with arrows in their backs. Which is not to say this isn’t embarrassing for the OC team given that their entire focus was cutting down release frequency to improve quality. (Given recent history, it’s going to be next week at the earliest before I update.)

• 
  Iyọ̀ (@iyoolaoyabiyi) reported 32 minutes ago

  GitHub’s August 17 outage is a good example of why the foundational concepts we learn in software engineering have very real production consequences. A critical infrastructure component failed under peak traffic. During recovery, some Copilot services also started failing. Then something familiar happened. Clients retried the failed requests. Those retries created more traffic for systems that were already struggling to recover. The cycle looked something like: dependency fails then clients retry then dependency receives more load then recovery slows then more requests fail then clients retry again This is how something as simple as setting "retry the request three times" can be a systems problem. Retries are useful, but they need engineering controls. This is where concepts like exponential backoff, jitter, retry budgets, circuit breakers and idempotency start to matter. Exponential backoff increases the wait between retry attempts. Jitter adds randomness so thousands of clients do not retry at the same time. Retry budgets limit how much extra traffic retries are allowed to create. Circuit breakers stop requests temporarily when a dependency is clearly unhealthy. Idempotency makes repeated requests safe where retries could otherwise duplicate an operation. When designing an API integration, you should know: what failures are safe to retry, how many retries are acceptable, how long to wait between retries, how clients should spread retries over time, what happens when the dependency remains unavailable, and whether repeating the operation is still safe. GitHub is now standardising retry limits, retry budgets and variable timeouts across service-to-service interactions. These ideas can look theoretical when you first learn them. Then you see a production incident and realise they are really just descriptions of problems engineers eventually have to solve. Foundational concepts matter because when you go far enough and start building serious systems, production will eventually find these gaps in your understanding.

• 
  Javed (@jshai0) reported 33 minutes ago

  One thing I really liked about Google Gemini was the Gemini Code Assist on GitHub. It used to review all the PRs for free and also caught many bugs. but Google shut it down last month. 💀

• 
  Devin Jameson (@devinjameson) reported 33 minutes ago

  OSS maintainers using coding agents: how do you stay organized? I want one place where I can group and sort issues, see PR size and status at a glance, and know which agent/session is working on each issue or PR. I typically have five or more agents running at once and it gets pretty overwhelming. Are you using GitHub Projects, a third-party tool, something custom? The clanker is telling me to try Conductor?

• 
  Dan Zurek (@DanMZurek) reported 35 minutes ago

  @gregisenberg If the code is free, the moat is the deployment record. An agent that reads self-hosters' GitHub issues and produces a ranked top-five reasons self-hosting failed brief is what makes the paid tier obvious.

• 
  NameLess (@Name1essss) reported 36 minutes ago

  @MatthewBerman @bot I’d use it as a research bot to track papers, GitHub issues, obscure forum posts and scattered technical findings — then connect the dots into something I can actually build from. That would save me hours every week.

• 
  Miran Khoshnaw (@MiranKhoshnaw_) reported 38 minutes ago

  Read @danmartell's AI Brain guide this morning. By the end of the day I had built the advanced version. Claude Code running 24/7 on my own server, so the brain stays on even when my laptop is off. Synced with Obsidian through GitHub. Connected to Google Calendar and ClickUp. Every morning at 8 it sends me a brief with my deadlines and open loops. First day running, it caught a wrong date in my notes and fixed my calendar. One day of building. This is what buying back your time looks like.

• 
  Flavio Amiel (@fba) reported 38 minutes ago

  BIG issue: since I moved roborank to a monthly recurring payment, I am getting clients subscribing and cancelling right away, then never test it, and then ask for a refund because they didn't read it doesn't work with every tool. But the lifetime deal buyers use it on a daily basis on hundreds of pages per day and give me feedback and requests features. The reason most guys cancel is because they signed up to test on their other CMS (and not Wordpress, WF or Github, which are the ones supported for now). Or they are not technical enough to know, for example, that lovable works with Github and they could use it. Overall these are less technical people to whom I could be adding some value, but I don't know how to navigate that. My hunch is that I should be reverting to the LTD and add a smaller annual fee for the server usage and the MCP / CLI (which is something everyone is asking for) If anyone has any feedback that'd be great. If no feedback, I'll test it anyway! LOL