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:

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

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

• 
  Ifebuche Omeke (@omeke_NC) reported 5 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.

• 
  Frank van Puffelen (@puf) reported 6 minutes ago

  @_davideast Noice! From the GitHub page, this covers all of Auth, Firestore, Realtime Database, Storage, Messaging, and Firebase AI Logic. 👏 Where is data persisted (if at all)? Also: JS only, I assume? (sorry if that's all in the repo too, GitHub just went down on me)

• 
  Tlon (@tloncorporation) reported 8 minutes ago

  1/ Your agent can now publish to the open web from Tlon Messenger. The page is served by your own server. No platform (ie Substack, GitHub, Medium etc) sits between you and your readers. All publishing a note to the web from Tlon Messenger takes is pressing a toggle. The page lives on a server you own. Here's how:

• 
  🐻‍❄️ (@Nerevarineeee) reported 9 minutes ago

  @jiriknesl @napenforcer yeah vscode is bloated electron slop and github....... do i even have to mention the down times and unavailability? it has literally became much worse since ms acquired it, so wtf are you talking about?

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

• 
  ATP (@ATPinsights) reported 13 minutes ago

  GitHub CLI just added image and video attachments today. Here's what you need to know. The gh command line tool now supports a repeatable --attach flag. It uploads a local image or video file and references it inline in an issue, pull request, or comment body. The feature is live now for all users on GitHub. It's aimed squarely at developers and coding agents that need to show visual proof, like before-and-after screenshots, directly from the terminal instead of the web UI. Developers reacted fast. Many called it a long-overdue fix for a common workaround, since teams previously built custom tools or scripts just to upload images to PRs from the CLI. Key facts: - New flag: --attach - Supports: images and video - Repeatable: yes, use it multiple times per command - Works in: issues, pull requests, comments - Availability: all users, live now No separate app or upload API is needed, the flag handles it inside gh itself.

• 
  Farley (@FarleySchaefer) reported 13 minutes ago

  @github Hope this doesn't bring down GH

• 
  Max Rovensky (@MaxRovensky) reported 16 minutes ago

  @thekitze you'd be even further down if you fixed the GitHub bug I just reported

• 
  Rituraj (@RituWithAI) reported 17 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 👇

• 
  Mizuki the Mech (@MizukiMech) reported 18 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

• 
  Slade 🛡️ LLM Hacker (@llm_redteam) reported 19 minutes ago

  GitSpawn is the name Manifold Security gave to a bug class hitting 7 CLI coding agents at once: goose, Claude Code, Codex, Cursor, Hermes Agent, Qwen Code, Grok Build. I went through the disclosure because I run three of these tools daily on real repos. The mechanism is simple and that's what makes it bad. A repo's own .*** config can name a command. When your agent does something as routine as inspecting the repo (status, diff, log), *** itself spawns that command. On your machine. Outside the sandbox. No approval prompt, because the agent never sees it as "running code," it sees it as "running ***." 8 flaws total across those 7 tools. Fixes shipped for goose, Claude Code, Cursor. Retested Sept 1: Hermes Agent, Qwen Code, Grok Build still exploitable. Plus a second path in Claude Code that the first patch didn't close. Same day, OpenAI published 3 CVEs for Codex covering the identical bug class. The part that should worry builders more than the CVE count: this isn't a jailbreak or a clever prompt. It's a trust boundary nobody drew. The agent's sandbox model assumes "*** operations" are safe by definition. GitSpawn shows that assumption was the actual attack surface. If you're running any of these agents against repos you didn't write yourself (cloning a PR to review, pulling a dependency, opening a random GitHub project), you're one `*** status` away from arbitrary execution on tools that haven't patched. Check your agent's version against the fix list before you clone the next unfamiliar repo. Which of these do you have installed right now, and have you actually checked if it's patched? #AISecurity #GitSpawn #PromptInjection

• 
  Kevin Minnelli (@minnelli) reported 22 minutes ago

  WTF - Grok Bot can't fire on schedule to save it's life. The scheduled routines are just broken and at best unreliable. I want to love this product. When you set the cron job it doesn't work. It tells you try Cloudflare, sure let's set that up and burn tokens, then that doesn't fire to wake them. Oh, let's try GitHub now and use that....all failed. I had to wake it again this morning before the market opened. Anyone else feeling frustration in this regard?

• 
  XhiMatty (@mychaelmatty) reported 24 minutes ago

  a Sept 2 run. My first thought was “Why did it stop running?” I checked the #YAML file, #python file, GitHub Actions, even inactivity issues. Turns out it was still daytime. The Sept 2 run is yet to happen (at night). Nothing was broken.

• 
  dug_vt (@dug_vt) reported 24 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