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:

• 
  tayyeeb_🐋 (@IdrisTayeeb) reported 6 minutes ago

  The Fable 5 story just got wilder. The jailbreak that got it suspended by the US government? The full technical details are now published on GitHub. 120,000 character system prompt. Publicly available. AI safety just became everyone’s problem.

• 
  Phil Jeffcock 🇺🇦 🇪🇺 🐳🆔=🐘🆔=@mastodonapp.uk (@PJeffcock) reported 9 minutes ago

  🚨🚨 Yet another unplanned change to the live bodged FBA Inventory Report @amznsellerhelp @AmazonASGTG Sometime between 2026Jun11 08:36:58 BST and 2026Jun11 12:47:44 GET_FBA_INVENTORY_PLANNING_DATA (FBA Inventory Report) started including data on our entire ~1.5 million listings and the recommendations is higher than the Restock Report (including before it was broken per GitHub #5261) suggesting retirement of the Restock is nearer. Sadly it is generating files which are truncated even more frequently and probably has other issues which I don't have time to investigate right now.

• 
  Ayaan Shilledar (@AyaanShilledar) reported 11 minutes ago

  Most teams already have the answers. They're just buried across GitHub PRs, Linear issues, comments, and project updates. I'm building System to solve that. Connect GitHub + Linear. Ask: "What's blocking this project?" Get an answer with evidence.

• 
  paul (building stuff nobody asked for) (@banx0isme) reported 16 minutes ago

  @elder_plinius no github no problem. and necessarily call it national security

• 
  Shravan Venkataraman (@theBuoyantMan) reported 20 minutes ago

  Github copilot outage? Transient API error since 2 hours ago. @github @Copilot

• 
  SHORT INFO (@ShortInfoNews) reported 20 minutes ago

  Any Windows 11 laptop with BitLocker in default TPM-only mode can be unlocked by a physical attacker with a USB stick. CVE-2026-45585 'YellowKey'. Microsoft $MSFT issued workarounds, no full patch. Fix: switch BitLocker to TPM+PIN. PoC public on GitHub.

• 
  Orville Wright's ghost (@angry_aero) reported 24 minutes ago

  @ProfBrahMos Have you ever looked at the NASA technical reports server? Their GitHub?

• 
  Faisal Karim (@Le__FaiCee) reported 26 minutes ago

  - Claude for coding. ($20/mo) - Supabase for backend. (Free tier) - Vercel for deploying. (Free tier) - Namecheap for domain. ($12/yr) - Stripe for payments. (2.9% per transaction) - GitHub for version control. (Free) - Resend for emails. (Free tier) - Clerk for auth. (Free tier) - Cloudflare for DNS. (Free) - PostHog for analytics. (Free tier) - Sentry for error tracking. (Free tier) - Upstash for Redis. (Free tier) - Pinecone for vector DB. (Free tier)

• 
  imefin (@imefinawulo) reported 27 minutes ago

  Is GitHub down??

• 
  cat (@uratmangun2) reported 31 minutes ago

  @ARYANJATHAR4 @andrewmccalip yeah this is probably an error when he vibecode with claude literally both x and github using stripe to pay all those people in the unsupported countries hopefully opus 4.8 can tell him and fix this

• 
  Lyrie.ai (@lyrie_ai) reported 34 minutes ago

  A Johns Hopkins University research team disclosed "Comment and Control" (C&C) — a cross-vendor prompt injection class that turns GitHub pull request titles, issue bodies, and issue comments into live command-and-control channels against AI coding agents. Three of the most…

• 
  Anton Semenenko (@adelayida210519) reported 36 minutes ago

  @mark_k I use both, but not for the same job. ChatGPT is where I shape the architecture: problem thesis boundaries risk model roadmap public framing what should / should not be built Codex is where I push that architecture into code: small scoped tasks repo changes tests docs checks repeatable validation I try not to use Codex as “do everything”. For me the flow is more like: ChatGPT => architecture / reasoning / prompt design Codex => implementation GitHub => memory / proof / audit trail local runtime => test what actually works The important part is not the tool split itself. It is keeping generation, execution, and release separate. Even with Codex: generated patch ≠ accepted change passing code ≠ released system agent capability ≠ release authority That is basically the same principle I use in my own work: generation != release authority

• 
  Neal Culiner (@NealCuliner) reported 37 minutes ago

  Github copilot chat window corrupt showing stack trace after upgrading to 18.7.0 (VS 2026). Anyone know the fix?

• 
  vivek (@itsreallyvivek) reported 37 minutes ago

  @tenobrus ig you dont have a job or genuinely dont do anything thats why you are keeping an eye on me each and every nanosecond and hoping i write or do something wrong. i cant see your single contribution on your feed just random bs atleast i actually made something for the public a knowledge base where they can navigate and learn things. its live on github you can check it tho and might be a good way to spend your time instead of just pulling me down

• 
  Nainsi Dwivedi (@NainsiDwiv50980) reported 37 minutes ago

  There's a quiet truth in security work: the single most important tool in web pentesting isn't some AI scanner or zero-day magic. It's a proxy that sits between your browser and the target so you can read, edit, and replay every request by hand. The industry standard for that costs $475/year per seat. A software engineer in Amsterdam named David Stotijn built an open-source version as a side project and put the whole thing on GitHub. It's called Hetty, and it does the core loop — intercept, inspect, modify, replay, search your full proxy history — as a single Go binary. No Java runtime. No license server. No account. No telemetry. The detail I keep thinking about: the last commit was over a year ago, and that's not abandonment — it's a feature-complete tool sitting still because HTTP didn't change. The proxy still proxies. A paywall would've expired your license by now; MIT-licensed code just keeps working. It won't out-feature the commercial suite on day one — there's no automated scanner, it's young. But for a bug bounty hunter, the math is brutal: one binary versus a subscription that costs more than your first bounty. The interesting part isn't "free Burp." It's that infosec tooling was community-built for years before it got fenced off — and one person quietly handed a piece of it back. It's called Hetty. MIT licensed. Link in comments ↓