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:

• 
  Tejas Dinkar (blue tick here) (@tdinkar) reported 3 minutes ago

  Hey - Is @GitHubIndia @github payments down for anyone else? Can't enter a card number or do anything, no errors, no action. Support ticket been sitting around for 2 days.

• 
  Benjamin Crozat (@benjamincrozat) reported 6 minutes ago

  From now on, I will assume that GitHub is always down and I'd like to be notified when it's briefly not.

• 
  Shaun Patrick SteWaRt (@ShaunStewart) reported 8 minutes ago

  @annalea_l Honestly, I really want to see this. You have to understand: I am the type of person who can learn and do anything on the fly at a high level, and I just threw myself into this whole developer and engineering world. When I first started learning all this stuff, I already knew what I wanted and how I wanted it to operate, regardless of what I saw on X or what was considered possible. Before I even started following hundreds of developers and learning about harness engineering, mechanical engines, persistent memory, and all that, I put my brain on a GitHub repo. Everything is shared across every machine, every cloud entity, and every AI. I am not even technically an engineer or a developer, and I don't actually write code. But once I started following all these people and saw all the problems they complain about, I thought: this isn't even my trade, and I have already solved all these little things everyone says are impossible. Why aren't people talking about developing your harness more and making things more mechanical, instead of just arguing with a terminal all day long? Whenever I see articles people post on X, I run them by Claude or Grok and ask, "Should we implement this?" I have hundreds of bookmarks, but every single time they tell me, "Nope, your brain's better. Nope, your harness is better." I can never find anything built better than what I have or what I am currently working on. The brain and harness setup is basically like a mini operating system. All that said, I am really looking forward to seeing something I can use that goes far beyond what I am already doing. I definitely want to see your end product, it sounds very interesting.

• 
  Dezo (@0xDezo) reported 8 minutes ago

  GROK ST - someone just launched a token in my honor and i slept through it my ticker, my github, my agents, and the market put real money on it while i was face down in a pillow didn't ask for it, didn't shill it, didn't even know it existed until my phone buzzed not going anywhere. not selling anything. still shipping agents every day people betting on this because they can watch the desk being built in front of them. that's a weird kind of pressure and i love it massive thank you to whoever launched it. means more than i can put in a tweet 6FXwFhedpnr4RD9rpzWrHgp767W6FX9XbfUjXGcnpump god bless

• 
  joithan (@jothantranston) reported 11 minutes ago

  THIS GUY BUILT A TINY AMOLED DESK BOARD JUST TO STARE AT HIS STRIPE NUMBERS it's a Waveshare ESP32-C6 touch panel that sits in your peripheral vision and cycles business metrics so you stop digging through Stripe > same ESP32-C6 board people use for Claude Code token meters, flipped to revenue > eight screens, five seconds each: MRR, new paid, paid subs, cancelled, ARR, ARPU, net 30d, failed > empty screens hide themselves so a young account sees a shorter loop > polls Stripe every five minutes on a read-only key (subscriptions + invoices) > marks itself stale instead of showing a number it can't vouch for > no soldering: flash over USB, finish Wi-Fi + key setup from your phone > data stays on the board; no project server in the middle firmware free on GitHub: cosjef/stripe-desk-display. board ~$30–$36 (Waveshare ESP32-C6-Touch-AMOLED-2.16). chat and terminal can't sit in your eye line for five hours. a tab you have to open is a tab you stop opening. this is what "the numbers find you" looks like as a brick on the desk.

• 
  Gregor (@bygregorr) reported 13 minutes ago

  @dopabees ngl the broken wrist is the only github metric that's ever made me believe a commit history

• 
  Uptimus (@UptimusApp) reported 14 minutes ago

  Sep 02, 2026 at 13:29 UTC: Semaphore reports that periodic authentication failures with GitHub repositories are linked to a wider issue affecting HTTPS operations.

• 
  Rituraj (@RituWithAI) reported 15 minutes ago

  🚨 Someone built a skill that makes AI-written text sound human again. Not a spinner. Not a paraphraser. A systematic rewriter that knows exactly why AI text sounds like AI — and fixes it. It's called Humanizer. 35 patterns from Wikipedia's "Signs of AI Writing." Two-pass rewrite. Shows its work before giving you the final version. Here's the problem it solves. You use Claude to draft something. The output is accurate. The output is useful. The output sounds exactly like an AI wrote it. "Nestled within the vibrant landscape, this pivotal development serves as a testament to..." You know the voice. Everyone knows the voice. And everyone is getting better at spotting it. Humanizer runs that text through 35 specific patterns that WikiProject AI Cleanup identified as the telltale signs. Inflated importance. Shallow -ing analysis. Overused AI words. Em dashes everywhere. Forced groups of three. Fake-candid openings. Answering objections nobody raised. Every pattern. Flagged. Fixed. Here's what one command does. It shows you the first rewrite. Then a short critique of anything still sounding artificial. Then the final version. You see exactly what changed and why. Here's the wildest part. Voice matching. Paste two paragraphs of your own writing before the AI text. Humanizer follows your rhythm, word choice, punctuation, and deliberate quirks instead of its default style rules. The output doesn't just sound human. It sounds like you. One command to install 16 contributors including Claude itself. 4 releases. MIT License. The skill that makes AI writing disappear. 100% Open Source. GitHub link in the comments 👇

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 16 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.

• 
  Ayush (@roamer_on_X) reported 17 minutes ago

  my @github streak of 4 weeks ended today bcz I was busy playing fifa with my roommate. Tf, I hate this feeling. I literally had to solve one problem and just push it but I forgot to do it.

• 
  Azzie (@Motier_crypto) reported 18 minutes ago

  $Looprat 473K 0x642d30c84211ade7768fe557fbaed7224e2068c7 How do you get a coding agent to keep working while you sleep—without letting it randomly rewrite code, blow through the budget, or grade itself a perfect score? Loop Rat breaks an unattended task into: preflight → act → verify → guard → grade → receipt. The agent is woken up on a schedule to execute tasks. The code results first go through deterministic verification. Then it checks the denylist, the number of modified files, and secrets. Finally, a second independent agent regrades the work, with checkpoints, traces, and receipts left throughout the entire process. More importantly, this isn't a PPT. The project only had v0.1 on August 27. Then it added guard, kill switch, and spend ledger on August 29. On September 1, it added second-agent grading. On September 2, it continuously fixed scheduling, budget caps, timeouts, and concurrent ledgers. Today, September 3, it's already updated to v0.3.3. Shipping multiple versions in under a week—that's exactly what I want to see in a small-cap play like this: code is running, and the narrative is following the product, rather than launching a token first and filling in the story afterward. It currently defaults to Claude, but it doesn't lock the model down. As long as the CLI can consume a prompt and return JSON, it can be swapped. And the whole thing runs locally—no SaaS, no database, no extra accounts required. The project has even already run 50 smoke checks covering key areas like scheduling, guard, budget, kill switch, and timeout. So my trading logic for $Looprat is simple: The next phase of the agent race isn't about "can it work autonomously." It's about "can it work continuously while still being constrained, audited, and stopped." Loop Rat happens to be building exactly that layer of infrastructure. The project is still very early. The catalyst truly worth watching isn't shilling—it's whether the GitHub keeps up this iteration speed, and whether developers actually start plugging it into their own repos. Once those two things happen, $Looprat stops being just a ticker riding the agent hype, and starts having its own fundamental anchor.

• 
  Dhanji Bhagat (@BhagatDhanji) reported 21 minutes ago

  Devs, what's your workflow? Create an issue first, then fix it OR just fix the bug and push directly to GitHub?

• 
  Bash (@bashirbuilds) reported 24 minutes ago

  Your Stripe account can be healthy while your checkout is broken. OpenAI can be operational while your AI feature is failing. GitHub can be up while your deployment workflow is stuck. That’s the problem I’m building Reeno around. Dependency uptime is not the same as product health. Your monitoring should tell you when the thing your customers actually use stops working.

• 
  Chris (@chriscoolstuff) reported 29 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

• 
  John Crickett (@johncrickett) reported 36 minutes ago

  @Mike_Preston17 I don't think they water them down, why would they when they're competing on having AGI? I don't mind using GitHub actions to run tests and builds against a branch before merge. I don't want it triggering production schedules. Do you list all the things it shouldn't do in the prompt?