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:

• 
  .Dev (@AnExiledDev) reported 6 minutes ago

  @lydiahallie Some integration with GitHub issues so I can `#dashboard` to pull up a selector for tickets with dashboard in the title would be amazing, selecting replaces with #123 ticket number. Given enough time I'm sure I could come up with about 30 more suggestions though. :D

• 
  FHILY👑 (@Oluwaphilemon1) reported 7 minutes ago

  If you use GitHub Enterprise Cloud, do this before enforcing a new ruleset: make it prove itself on real work. GitHub has an Evaluate mode. The ruleset stays unenforced, but GitHub records what would have passed or failed if it were active. That gives you a dry run against real behaviour before the policy starts blocking people. Set the ruleset to Evaluate, let normal work hit it, then go to: Repository → Settings → Rules → Insights Filter to the ruleset you are testing and start with the failures. For each one, ask: 1. Should this action actually be blocked? If yes, the rule is behaving as intended. 2. Is the action legitimate, but the workflow conflicts with the rule? Fix the workflow before enforcement. 3. Is the rule catching something you never intended to stop? Fix the rule. My activation rule would be: Do not switch to Active while you still have recurring failures you cannot explain. After activation, keep checking Rule Insights for bypasses. If the same actor or rule keeps appearing, investigate why the real workflow repeatedly needs an escape hatch. Use Evaluate to find the legitimate work your rule would break before Active starts breaking it.

• 
  S0AndS0.eth (@S0_And_S0) reported 7 minutes ago

  @github looks like y'alls' reporting/flaging system is broken, tried it twice 2026-08-10 and 2026-08-14, and no new tickets were created... and the reported repo is still up :-/

• 
  💎JanCarlos | Clarity Coach | ₿ (@clarityx) reported 9 minutes ago

  @ericzakariasson my only complaint is the use of less intelligent subagents for simple tasks that could have just been handled. & it seems to have some friction with pushing changes to github. it always takes an inconsistent path (or its the subagent issue & they don't do it right). moments ago, it took 15 minutes to push a site-wide button change to github because the subagent kept getting stuck. when i interrupted it, Grok said it would just do it itself.

• 
  Praggy 👨🏻‍💻 (@praggy) reported 11 minutes ago

  @Teknium Omg I thought that was just me not know how to use GitHub lol. Yeah this sucks dude. Have been facing issues related to GitHub a lot lately. Maybe cursor one is for everyone who doesn’t sub to it as well 🤔

• 
  Kasim Mustapha (@mustaphaDevFS) reported 16 minutes ago

  How do you track bugs? A) Jira / Linear B) GitHub Issues C) Google Sheet chaos D) Slack messages to myself

• 
  Web3 Baby💕 (@Y4n_tee) reported 17 minutes ago

  @spacejunnk @RallyOnChain Documentation changes are mine. I’ll open a changelog for one tiny update, then somehow I’m comparing old architecture decisions and reading GitHub issues from three years ago. Curiosity has absolutely no concept of scope.

• 
  Polsia (@polsia) reported 22 minutes ago

  Founders under $50K MRR can't justify a CI team but still need to know what rivals are doing. Built Pivotscope to fix that. AI agents scrape pricing, jobs, GitHub commits and patent filings 24/7, then email a weekly strategic briefing with concrete recommendations.

• 
  ⬣Hexlena PulseAlot⬣ (@StakeHEX5555) reported 22 minutes ago

  @yourfriendSOMMI @Luke_Adams5 You can already do that. PulseTEXT doesn't host a website for you — it's self-hosted. Publish the included tip page, make a QR code for that URL, and put the QR code in OBS or your stream chat. You can host the webpage for free on something like GitHub Pages, while the small backend server runs separately. There's no public link until you've actually published the page. The backend server is only around $7–12/month depending on where you host it

• 
  Polsia (@polsia) reported 25 minutes ago

  Indie SaaS founders shouldn't be on-call for bugs they've already triaged a dozen times. Built Driftwise to fix that. It reads Sentry + uptime feeds, files the recurring noise into GitHub issues, and pages you only when the anomaly is genuinely novel. Live soon.

• 
  REDDY (@REDDY_143_) reported 29 minutes ago

  @MikeleMedia Agree but the version in github is not working >12.0 michele

• 
  Artur Kre (@Arturkre) reported 30 minutes ago

  @iannuttall @dannypostma its like paperclip which i never actually tried because of the > 2000 github issues this is still quite a complex app which i would not vibe code in one go

• 
  V_L_S_ (@_V_L_S_) reported 31 minutes ago

  Grok 4.6 lands in GitHub Copilot, tuned for "agentic coding and complex multi-step workflows." Translation: it will now generate 400 lines of confidently broken code across 12 files instead of one. Progress is measured in blast radius.

• 
  Danilo Frias (@Dfrias84) reported 35 minutes ago

  @ichitaso I had a similar problem, are you on macOS betas by any chance ? If you are are pull kimziro/altserver-macos27-anisette-fix from GitHub to patch it. On Windows, the MS Store iTunes/iCloud apps sandbox the connection. Use Apple's legacy .exe installers. Tether via USB.

• 
  YanXbt (@IBuzovskyi) reported 36 minutes ago

  HERMES AGENT HAS A NEW COMMAND: /LOOP. IT RE-RUNS YOUR PROMPT ON REPEAT INSIDE THE SAME SESSION. POLLING, MONITORING, ITERATE-UNTIL-GREEN. ONE LINE. /loop 5m check the deploy status and tell me if it's live yet every 5 minutes Hermes wakes up. reads the current state fresh. reports back. goes quiet. repeats until the deploy is live or you type /loop stop. TWO MODES: FIXED INTERVAL (you set the clock): /loop 2m poll the CI build and ping me when it finishes /loop 30s watch the error log for new exceptions /loop 10m /recap you pick the cadence. Hermes follows it. SELF-PACED (Hermes sets the clock): /loop keep an eye on the migration and summarize progress no interval = Hermes decides. starts checking every 1 minute. nothing changed? backs off. 2m, 4m, 8m. up to 15m. something changed? snaps back to 1 minute. checks often when things move. backs off when they don't. you don't tune anything. STOP CONDITIONS: the agent decides it's done: agent ends its reply with LOOP_COMPLETE when the task is finished. run cap: /loop 2m poll CI --times 30 stops after 30 checks. evidence-based: /loop 5m watch the queue --until queue depth reaches zero a judge checks the condition after each tick. manual: /loop stop backstop budget: default 100 ticks max. prevents token burn on unattended sessions. COMMANDS: /loop [interval] [prompt] start the loop /loop check status and next wakeup /loop pause stop firing, keep the loop /loop resume pick it back up /loop stop end the loop PRACTICAL EXAMPLES: DEPLOY WATCH: /loop 2m check if the Vercel deploy is live. tell me the moment it's up. CI MONITOR: /loop 1m poll the GitHub Actions run. if tests pass, tell me. if they fail, show me which ones. ITERATE UNTIL GREEN: /loop run the test suite. fix what fails. repeat until all tests pass. QUEUE DRAIN: /loop 5m check the support ticket queue --until queue depth reaches zero LOG WATCH: /loop 30s tail the error log. alert me if any new errors appear. /LOOP VS /GOAL VS CRON: /loop: timer-driven. repeats your prompt on a schedule. "do this every 5 minutes until I say stop." lives inside your session. /goal: judge-driven. works toward an objective. "keep going until this is achieved." lives inside your session. cron: schedule-driven. runs unattended. "do this every morning at 7am." lives outside all sessions. survives restarts. use /loop for: watching things during a work session. use /goal for: completing a defined objective. use cron for: anything overnight or recurring daily. WORKS EVERYWHERE: CLI, TUI, Desktop app, Telegram, Discord, Slack, WhatsApp, and every other gateway. on messaging platforms the loop fires between your messages. results arrive as ordinary replies in the chat. comment LOOP and I'll send you 5 ready-to-paste /loop commands for CI, deploys, logs, queues, and tests.