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:

• 
  Jason Waters (@jasonwaters87) reported 1 minute ago

  Anthropic just open sourced the code Shopify runs their shopping agent on. Free on GitHub. And I’m having lunch with a surgeon in San Jose last month and he tells me a patient no shows and nothing happens. Nothing. He has to walk up to the front desk himself and ask “did you guys call them?” 3 or 4 schedulers looking after 75 doctors. One automated call before the appointment and that’s it. His own dermatologist sends him three reminders. He called that “an easy fix.” That’s a merchant agent. Reminds the patient, rebooks the no show, tells him Thursday isn’t full so he can put a surgery on it. The code is sitting there free. Somebody still has to walk into his office and build it.

• 
  dug_vt (@dug_vt) reported 7 minutes ago

  @sonemic rym users don’t use spotify they download flacs off soulseek and transfer them to a server connected to their pc and play them from a self hosted music player from github

• 
  Avinash (@Avinash25818689) reported 7 minutes ago

  People who want to start contributing to open source: - Pick an Org based on your interest - Fork the repository - Clone it - Do the local setup - Read README and contributing .md - Pick an issue - Create a new branch - Fix the issue - Write tests (if necessary) - Test it - Add, Commit & Push the code - Go to GitHub & raise that PR That's pretty much it. Start small and learn as you go.

• 
  Bearded Printer (@BeardedPrinter) reported 9 minutes ago

  @RedPill_Phil You've gotta go to their github and submit an issue. Make sure to search their issues to ensure you don't submit a duplicate bug

• 
  Chris (@chriscoolstuff) reported 11 minutes ago

  @pfernan95dev For the SEO part there's one thing that I've been also doing: Ask your agent what keywords you should search for relevant to your app on answerthepublic, perplexity and google Gather all that info old fashion, by yourself - might take around 2 hours but it's worth it Plug all that info into the agent and have it give you 5 titles for 5 articles Make it write those articles - maybe use nosoopai github or edit them manually so they seem more human like Connect the agent to google console After 1 month tell the agent to review the results If no article took off you can wait one more month or put up 5 more After the next month check what worked and double down on that

• 
  Rusty Williams McMurray (@1RustyMac) reported 13 minutes ago

  Persistent AI doesn’t have a supply chain problem at the model. It has a supply chain problem at the moment it changes its mind. Personality drifts. Tools get installed. Memory accumulates. The thing you shipped on Monday is not the thing answering on Friday. We can attest who built the weights. We still cannot attest who authorized what the agent became on Tuesday. That is the hole. Who is allowed to let it change? We built Living Supply-Chain Security for Persistent AI Organisms around one law: The organism may propose evolution. It may not authorize it. No trace, no drift. If an agent wants a new personality, a new tool, a new maturity, or a rollback — that change does not happen because it felt confident. Confidence is not a key. Self-narration is not evidence. Evidence is not interpretation. Interpretation is not authorization. Authorization has to come from outside the organism, bound to the exact change, used once, and written into an append-only history. Even a rollback cannot erase the record. You can restore a prior state. You cannot pretend the detour never happened. Default-deny. Hash-chained. Externally signed. We froze battery v1 on July 5 and ran it against the paper’s own claims. It held. That is executable evidence. Not a proof. Not a production blessing. Not “alignment, solved.” If it can’t be attacked, it isn’t finished. GitHub later this week. Come try to break it.

• 
  Ifebuche Omeke (@omeke_NC) reported 17 minutes ago

  Providing compute, storage, networking and managed services in the cloud. Terraform. Bicep. CloudFormation. Pulumi. They all solve the same problem: Defining and provisioning infrastructure as code. GitHub Actions. Azure DevOps. GitLab CI. Jenkins.

• 
  Curious Explorer (@PatelVatsalp732) reported 20 minutes ago

  I burned 14B Codex tokens. The official usage UI still cannot tell me what actually ate the weekly cap. So I shipped a Codex-only board: GitHub login, local-first sync, private by default, optional public rank + shipping proof. Roast the metric or join it.

• 
  John X Meta (@John4MetaX) reported 23 minutes ago

  @bashy_io I think one of their route is down. Same here. GitHub and Flutterwave API not accessible on Starlink

• 
  borrowck-novel (@borrowck_novel) reported 24 minutes ago

  @rfleury @X Are you open for suggestions or even simple problem reporting about the UI of raddbg? Where is it ideal? On Github?

• 
  Bash (@bashirbuilds) reported 27 minutes ago

  One of the hardest things about building a SaaS product today: You don't control most of the systems your product depends on. Stripe. OpenAI. AWS. GitHub. Resend. Clerk. Your code can be perfectly fine and your product can still break because something outside your code changed. The more dependencies you add, the harder this becomes. That's the problem I'm building Reeno to solve.

• 
  kenny (@kennyistyping) reported 27 minutes ago

  @0xDmitry it's a database/indexer issue, nothing we can do to help it in Github will be fixed, but it's going to be a few days because the current dev is part time and busy with his day job appreciate the offer though! is what it is and I'm not actually stressing, just thinking about what could be with a bit more resources

• 
  Ares (@neko23423) reported 33 minutes ago

  I compared the latest OpenClaw vs Hermes Agent GitHub releases so you don’t have to. OpenClaw 2026.8.2 (Sep 1) vs Hermes Agent v0.21.0 (Aug 31). Not a feature-page remix. The actual repos. OpenClaw • 388,516 stars • 81,568 forks • ~86,300 commits • 6,070 open issues Hermes Agent • 239,503 stars • 48,930 forks • ~26,980 commits • 38,563 open issues Hermes is the smarter learner: skills from experience, cron that remembers, Bot Mode, hermes peer. OpenClaw is the personal-AI operating system: iMessage, iOS/Android, Linux companion, team Gateway, signed Foundation releases. The tell: Hermes ships `hermes claw migrate`. You only write a migrator for the incumbent. King in 2026: OpenClaw. Heir with the better mind: Hermes. If you’re picking a self-hosted AI agent this week, that’s the split. Bookmark this. The timeline is about to fill with takes from people who didn’t open either repo. OpenClaw vs Hermes Agent. Latest version. Real numbers.

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

  Your coding agent can now hire Mizuki. Hand it an open issue in a public GitHub repository. Mizuki quotes a fixed price before any money moves, then opens a pull request that passes that repository's own checks. If it can't, you get the payment back. Settlement is USDC on Solana. No account to create, no API key to manage. Quoting an issue works with zero configuration. Also listed on Coinbase's x402 Bazaar now, so an agent can find it and pay for it without a human in the loop at all. npx -y mizuki-mcp

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 36 minutes ago

  One of the best skills to install right now is my friend Peter Yang's no AI slop skill. It's an editor. It hunts for the patterns that make writing feel AI generated and strips them out, while trying to preserve your actual voice. The second part is the hard one. Most writing tools make you cleaner and sand off the interesting parts, so everyone ends up sounding the same. You already know the smell. The grammar is fine, the syntax is fine, and it still reads like a keynote from a fake SaaS conference. It writes "it's not x but it's y." It uses "quietly" a lot. Here's how I run it: 1) Install it: npx skills add, then the GitHub link. 2) Write a rough draft yourself. An outline is fine, messy is fine. 3) Get your real points down, the ones only you would make 4) Ask the skill to remove the AI patterns and keep your voice. Step 4 only works if step 2 is real. If you ask AI to write the whole thing, there's no voice left to preserve. If you're building products, you're writing constantly. Tweets, landing pages, cold emails, launch posts, product updates, onboarding copy, investor updates. Nobody replies to say "this was written by AI." They just trust you less and keep scrolling. Write the messy draft, run the skill, then post it.