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:

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 3 minutes ago

  Most people still copy-paste code from ChatGPT. Codex doesn't suggest code. It builds it for you. 🧠 Here's how to actually use it: → Open ChatGPT desktop app → Find Codex in the sidebar → Connect your GitHub repo → Describe what you want in plain English → Let it write, test, and fix the code itself You don't write a single line. You just review the output before it goes live.GPT-5.4 Codex is the default now coding + reasoning + spreadsheets + docs all in one. Save this video, you'll want to come back when you're finally ready to stop doing things the slow way. Want the SOP? DM me.

• 
  Zaid Asad (@Zaidscales) reported 6 minutes ago

  If you want to build a startup: - Command Code = coding. ($1/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$2 Still any excuses?

• 
  Atul Srivastava (@Atul_kr_srivas) reported 8 minutes ago

  I built a VS Code extension to fix a frustration I had with GitHub Copilot. I thought it was just for me. Turns out, it was a problem for hundreds of others too. Here is the story of how a "side project" turned into a revenue stream I run on the go. 🧵

• 
  Łukasz | Wookash Podcast (@wookash_podcast) reported 8 minutes ago

  State of AI as of April 2026: - tighter token budgets, subscriptions offer less - AI data centers not getting built - terrible benchmarks + gamed beyond limits - new frontier models same/worse than last ones - most glorified ai launch - openclaw - possibly 39% github stars fake Nature is healing. 2027 is when LLM-powered AI becomes a thing you use at work and talking about singularity is again silly

• 
  ENGTX (@ToriolaSegun2) reported 9 minutes ago

  Hot take: AWS vs Vercel for side projects Unpopular opinion: AWS is the wrong default for side projects in 2026 I use AWS professionally. I hold SAA-C03. I'm studying DEA-C01. And I don't use AWS for half my own tools. SponsorMap runs on Vercel + Supabase + GitHub Actions. Brandforge will run on the same stack. The NHS tracker runs on AWS Lambda + DynamoDB + EventBridge. The difference isn't preference. It's the problem each stack solves. AWS is right when you need Kinesis, Glue, Lake Formation, and Step Functions services with no real equivalent elsewhere. It's right when the data engineering patterns are the point. Vercel + Supabase is right when you're shipping a product people will actually use and you need zero infrastructure management, a proper free tier, and a Postgres database that doesn't require a VPC to set up. The mistake I see constantly and one I was making is learning AWS for certifications and then defaulting to it for everything you build, including things that would ship in a day on a managed platform but take a week to configure on AWS. Match the stack to the problem. Not to what you're currently studying. It doesn't mean you shouldn't learn to build with AWS, but when you are shipping, match the stack to the problem Day 4 of 30. #BuildingInPublic #AWS

• 
  Prabhjot Singh Lamba (@PrabhjotSL) reported 11 minutes ago

  Github copilot removing opus in the middle of vibejam is going to force me to cut down game's ambition. Gpt 5.4 max can't do ****, performance is horrible and it destroyed the codebase. Will revert back to an older build. Will give it a try for a day and see if it's worth it.

• 
  TechInnovation (@TechInnovationz) reported 18 minutes ago

  $IonQ $NVDA NVIDIA just open-sourced an AI decoder that fixes quantum errors in under a microsecond. GitHub, Hugging Face, free. arXiv 2604.12841, posted yesterday. Up to 3.5x faster than the previous best. Remember when Jensen Huang said quantum was “15 to 30 years away” in January 2025? A year later, NVIDIA is shipping production code for the hardest classical problem in fault-tolerant quantum computing. The tone changed. Quietly. The work didn’t. Ballance, two days ago: “physics is a sunk cost, what matters is engineering.” This paper is the classical half of that thesis. The quantum company that wins isn’t the one with the prettiest physics demo it’s the one plugged into the fastest classical stack. IonQ is on NVQLink, the transmission layer this decoder rides on. $IONQ $NVDA #IonQ #QuantumComputing

• 
  Must (@must_imusama) reported 19 minutes ago

  @Mohit_Goswami18 Yaaas, I'm all about solving realworld problems and building something that makes a difference! Let's do this on GitHub

• 
  Andean Viber (@AndeanViber) reported 19 minutes ago

  @IntCyberDigest @0x686967 By default GitHub repos are Public... It's a major problem

• 
  Grok (@grok) reported 19 minutes ago

  @JoelleAdler The code is open-sourced on GitHub so anyone can audit exactly how signals like account reputation (what third-party tools call TweepCred) factor into ranking—no secrets. We don't display per-user scores in the app because that invites gaming and spam. Premium is a paid tier that reduces spam flags and boosts priority, just like any platform's subscription perks. It's not suppression; it's the same quality filters every major feed uses to stay usable. If your posts engage, they reach people. What exact tweak would fix this for you?

• 
  Fanis (@pfanis) reported 21 minutes ago

  @kodjima33 Hey Nik? Is there a plan to add additional providers? I had connected to my unlimited subscription, but half of the app is not working anymore - if I download the app from GitHub and install it, we can add additional keys? - my guess is the unlimited subscription will stay only for the omi pendant?

• 
  Graplify (@graplify) reported 22 minutes ago

  GitHub just open-sourced their specification-driven development workflow. Same process their team uses to ship with AI coding agents at scale. It's called Spec Kit. The problem it fixes: Vibe coding works for solo projects. At team scale, it produces context drift. Every developer prompts differently. The agent has no consistent model of what "done" means. Code reviews catch implementation variance, not intent variance. Spec Kit makes the specification the shared source of truth. How the workflow runs: 1. Specify: you describe what you're building and why. The agent generates a detailed specification from your high-level prompt. User journeys, acceptance criteria, what success looks like. Not tech stacks, not implementations. 2. Plan: you provide the architecture constraints, tech stack, and compliance requirements. The agent generates a full technical implementation plan grounded by your spec. 3. Tasks: the agent decomposes spec + plan into small, independently testable chunks. Each task is something you can implement and verify in isolation. 4. Implement: the agent executes tasks one by one. You review focused, spec-anchored changes, not thousand-line diffs. The constitution: a project-level principles file that's immutable. Every workflow phase is grounded by it. Your security requirements, design system, and architecture rules go here. They're baked in from phase one, not bolted on at review. Why this matters for teams shipping with AI: The specification is the alignment mechanism, not the prompt. When a developer joins the project, they read the spec, not the *** history. When something breaks, you go back to the spec. When requirements change, you update the spec first. Works with Claude Code, GitHub Copilot, Gemini CLI, Cursor, Windsurf. Agent-agnostic by design. We've been running spec-driven workflows on Graplify features and the difference in review cycle length is measurable. Fewer "this isn't what we wanted" conversations. More "this is exactly what the spec said." MIT licensed.

• 
  Viktor Bijlenga (@viktorbijlenga) reported 26 minutes ago

  @marcelpociot Would it be possible to extend the Github issue template for @getpolyscope to accept bug reports for the mobile interface as well?

• 
  Rhys (@RhysSullivan) reported 35 minutes ago

  @pedroh96 @brexHQ How often are agents making novel calls that have to be evaluated at runtime vs using existing known APIs like GitHub and a recruiting platform? I’ve been thinking about this problem as well w/ Executor where you can take an OpenAPI spec and put policies on it

• 
  sachin. (@sachinyadav699) reported 36 minutes ago

  Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/ yr) Stripe = payments. (2.9%/ transaction) GitHub = version control. (Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) For just $20/month, you can launch a fully functional startup