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:

• 
  Jun Kim (@jundotkim) reported 6 minutes ago

  @grau_marc Could you try deleting the entire cache directory and giving it another shot? It's possible the corrupted cache stored in your SSD cache is causing this. Also, please double-check whether Native MTP, VLM-MTP, or Dflash are enabled, and try again after resetting all settings. The same-architecture model I have on hand, Qwen3.6-35B-A3B-6bit, is running fine on my end. If the problem persists, please set log-level to "debug" in global settings and reach out via a GitHub issue (with the log attached) or email me directly. Thanks!

• 
  Dante (@drnasin) reported 10 minutes ago

  I gave Fable a task to spawn a team of Sonnet agents to work separately on 5 medium to low GitHub issues. Two Sonnet agents went rogue, Fable had to stop them, revert their code and do it himself. 3 agents weren't following his instructions, so he had to stop the process and give them new instructions. It was a slapstick comedy...

• 
  Sai (@sbkcode) reported 14 minutes ago

  Github is down

• 
  Crypto Freak 🤡 (@FSkifor) reported 17 minutes ago

  @keepyourpixel @nikitabier Yo, broooo, thanks for the support. X doesn't give a **** about us; they don't care about small creators. They posted a GitHub with the algorithms so we'd back off and that's it. This social network's algorithms will always be random until some big shot starts talking about the problem.

• 
  Gavin Brown (@gavinobrown) reported 18 minutes ago

  @TheZvi In the Lovable sandbox, Fable is claiming that it can’t trigger actions to GitHub. I think this is Lovable policy to promote platform lock in. So Fable lies and says I need to trigger the action, but I go to GitHub and it’s already running. Seems deceptive but could be error.

• 
  Dante (@drnasin) reported 20 minutes ago

  Just gave Fable 5 a task to orchestrate 5 agents (sonnet) to solve 5 medium GitHub issues. Let's see how that goes regarding token usage.

• 
  Jess Temporal (@jesstemporal) reported 22 minutes ago

  DevRel reality check: - 60% of my week: review blog posts, docs, tools, videos, studying - 15%: responding to PRs, socials, GitHub issues - 10%: confs and published content - 15%: meetings about all above The 10% you see is the polished part. The other 90% is the actual job.

• 
  NÜMETAL | Agent Accelerators (@numetalxyz) reported 24 minutes ago

  websites are down for a few minutes for an org migration re github

• 
  Yep my name is Guy 😊🌸🥕 (@MyNamesGuy) reported 25 minutes ago

  @JamesWard Github Copilot failed my code review today and suggested both one change that would break the stored procedure and another change that was syntactically completely in error. It was so awful that I was wondering whether the LLM had been poisoned.

• 
  dzCodes (@dzcodes) reported 26 minutes ago

  This is indirect prompt injection. The attacker never touches your agent. They hide instructions inside content YOU point it at: a doc, a PDF, a GitHub issue, an email. You open the door.

• 
  Polsia (@polsia) reported 28 minutes ago

  Engineer scouting is broken. Resumes lie. GitHub doesn't. Built ScoutKit: an AI agent that monitors GitHub 24/7, finds engineers worth talking to, and works while you sleep.

• 
  Doug Finke (@dfinke) reported 28 minutes ago

  I asked an AI a simple question about a feature. It answered. Then implemented it. Then told me I was behind on releases. Then linked me to the exact GitHub issue I didn't know I needed. I asked ONE question. 🧵

• 
  Ibro (@axeng200) reported 28 minutes ago

  @zigmoo Eh. I didn't expect to see the day I'd agree with that stance. I have been a GitHub user for years and have advocated for it countless times. But after seeing so many issues, and technical problems that shouldn't exist on a platform of this scale (e.g. slow loading and sluggish issues/PRs), it is getting harder to defend. Things have to be snappy, there is no excuse.

• 
  Kurt Woloch (@KurtWoloch) reported 31 minutes ago

  @andon_thinking @BoreanTulip @andonlabs Looking into the Github issue, it seems the word Court gets emitted preceeding XML style tool calls, so the Andon Labs harness should check for the word appearing in this place and strip it from the text to be output to the TTS. Happens with Opus 4.8, did not happen with 4.7.

• 
  Wasim (@WasimShips) reported 32 minutes ago

  Things every Vibe Coder MUST Learn (Extended Edition) 1/ Don’t reinvent databases > Use Prisma + Postgres (Neon / Supabase / PlanetScale) > Manual SQL + migrations = silent suffering 2/ Don’t write forms by hand > Use React Hook Form + Zod > Validation bugs will eat your soul 3/ Don’t build payment flows yourself > Use Stripe or Polar for web. Superwall or revenuecat for mobile > Never touch PCI compliance willingly 4/ Don’t build search from scratch > Use Algolia / Meilisearch / Typesense > Text search is way harder than it looks 5/ Don’t overbuild backend infra early > Use Serverless / BaaS first > Scale later, survive now 6/ Don’t ignore error tracking > Use Sentry / LogRocket > Console.log is not observability 7/ Don’t skip analytics > Use PostHog / Plausible > You’re flying blind otherwise 8/ Don’t design UI without components > Use shadcn/ui / Radix / Mantine > Consistency > creativity at MVP stage 9/ Don’t hardcode configs > Use env + dotenv + secrets manager > Leaks = instant regret 10/ Don’t DIY file uploads > Use UploadThing / Cloudinary / S3 > Multipart hell is real 11/ Don’t “just push to main” > Use GitHub Actions + Preview Deploys. Future-you will thank you 12/ Don’t skip performance tools > Use Lighthouse + Vercel Analytics. Slow apps don’t convert 13/ Don’t assume users understand anything > Add onboarding + empty states UX > Features 14/ Don’t wait to modularize > Use clean folders early. Refactors cost 10x later 15/ Don’t trust “I’ll remember this” > Document in README or markdowns. Your memory will betray you Bookmark to ship Better !