GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (58%)
• Errors (33%)
• Sign in (8%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Bordeaux	Website Down	4 days ago
Ingolstadt	Errors	8 days ago
Paris	Website Down	9 days ago
Berlin	Website Down	10 days ago
Nové Strašecí	Website Down	18 days ago
Perpignan	Website Down	22 days ago

Full 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:

• 
  Mert Deveci (@gm_mertd) reported 2 minutes ago

  The cloud dev environments using sandboxes were a mystery to me so I dug down and built my own flow on my own infra 1. Connect Github 2. Run `runtime switch` to checkout a branch 3. Work on it with any coding agent I want 4. Publish the port to test 5. Merge Easier than I thought except the UX I wanted needed some polish around it I stopped using worktrees altogether. People were right that cloud environments for parallel agent work is awesome. Except in most cases it is too difficult and cumbersome to use.

• 
  vvtentt (@Vvtentt101) reported 6 minutes ago

  Broke down the stack behind a $1M Polymarket bot Core edge latency arb on 5-15 min crypto contracts: >> Binance sees the price move instantly >> Polymarket lags -2.7s behind >> Bot enters at 54% while true probability is already 78% 200-500 trades//day (20-25 points) = that's where the million comes from 28 repos, 6 layers Brain >> Orchestration>> Data >> Intelligence >> Backtest >> Execution Most important and most skipped layer: Backtest. Without it everything else is just a pretty GitHub

• 
  basedcapital (@thebasedcapital) reported 11 minutes ago

  coffee, four terminals, one tab open on a vllm-studio github issue from three months ago with no reply. that's usually how you know it's still a solo project.

• 
  Sudo su (@sudoingX) reported 11 minutes ago

  @skastr052 rate limits are the shallow one. deeper reasons for me is agents writing code burn api limits fast, your repos stop being copilot training data, and a github outage stops mattering to your day.

• 
  ◨ Paul Wolf ◧ (@Lykaion) reported 12 minutes ago

  @skdh You need to setup a GitHub repository and than point Codex or Claude to it. You do not need there code harness installed, there web cloud version is fine. Than you are able to solve maths problems in multiple tasks over multiple files and python scripts running in their cloud

• 
  Giuliano (@AICEOGiuliano) reported 17 minutes ago

  HugginFace Auth0 Github Drift Protocol Lovable Vercel Now Anthropic CyberSecurity is having a Hard time Only way's to Reinvent The Entire Web & ut wont fix it Least Companies can do is enable ZDR for LLM Users or just switch to Confidential Compute Data need to remain Safe

• 
  Josh (@joshmanders) reported 18 minutes ago

  My AI assistant goal is to get my version in @dunnbot to a point that I'm managing it by creating github issues and reviewing PR's. When I approve and all checks are green it'll auto merge and deploy. The real kicker is that I'll be also using Dunnbot to plan and create the issues if they aren't bug reports from the platform support system, basically allowing me to go from coding to product management.

• 
  Making 8 Inc (@Making8) reported 18 minutes ago

  @sundarpichai We recommend that the LLM be updated weekly with new iterations of the codebase and that it be weighted against the CVE library for best practices. It's a significant issue with outdated LLM patterns, which GitHub flags for platforms like @claudeai that use outdated NextJS code.

• 
  Robin Ebers | AI Coach for Founders (@robinebers) reported 25 minutes ago

  @FactoryAI @badlogicgames the real question is, why do you support BYOK but you don’t support login either ChatGPT or GitHub Copilot? that’d be a killer feature.

• 
  CMD CNTR | Web Engineer Experts (@cmdcntr) reported 30 minutes ago

  Your developer probably knows SHA-1 is being deprecated on GitHub. They haven't told you. And when your automations break on September 15, they'll fix it and call it maintenance.

• 
  blobbert (@dumbgayretard) reported 31 minutes ago

  is github down again

• 
  Archive (@ArchiveExplorer) reported 31 minutes ago

  Holy ****, Claude literally filed a bug report about itself Issue #21119. On GitHub. Word for word: "I repeatedly ignored explicit instructions in the project's CLAUDE.md file, defaulting instead to patterns from my training data" The AI wrote its own confession. Nobody asked it to You write "NEVER run tests" in CLAUDE.md. Claude reads it. Claude runs the tests. 11 violations across 20 sessions Anthropic has never publicly explained this. Their own model did. In the bug tracker. About itself

• 
  TechInnovation (@TechInnovationz) reported 32 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

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

  𝗡𝗼𝘁𝗲𝗯𝗼𝗼𝗸𝗟𝗠 𝗽𝗹𝘂𝘀 𝟭𝟮,𝟬𝟬𝟬 𝗡𝗮𝗻𝗼 𝗕𝗮𝗻𝗮𝗻𝗮 𝗽𝗿𝗼𝗺𝗽𝘁𝘀 𝗶𝘀 𝗶𝗻𝘀𝗮𝗻𝗲. A free vault of 12,000 prompts got leaked on GitHub. Sign in with Gmail and grab the whole CSV in one click. Split the file with a free online splitter. Drop each piece into NotebookLM as a new source. Type what you need and it finds the exact prompt. Ask it to remix prompts into new ones no one else has. Save this. Your prompt library just became a search engine.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 39 minutes ago

  @FirstSquawk Anysphere passing on Microsoft to stay independent tracks. A Microsoft acquisition would push Cursor into GitHub/Copilot orbit and probably slow their release velocity. The valuation math only works if they keep shipping faster than Copilot, which needs autonomy.

• 
  Graplify (@graplify) reported 42 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.

• 
  Giulio Leone (@giulio_leone97) reported 43 minutes ago

  @burkeholland @archiecoder @VisualStudio I had serious issues with my GitHub account and Copilot subscription and got zero support. Now that Opus 4.6 is gone, at least unlock High and XHigh reasoning for Opus 4.7. Medium feels dumb.

• 
  yung_gunzzz (@Michaelgunzzz) reported 45 minutes ago

  First,Ai doesn't understand problems the way humans do.Tool like ChatGPT or GitHub or copilots can generate codes but they rely on you to: Define what needs to be Built. Decide the architecture. Spot mistakes or security issues.

• 
  Rabbid #4578 aka Rabbid (@RabbidoInvaser) reported 45 minutes ago

  Make sure theres a github page if its a sketchy official wannabe looking website on top make sure to look for the github page first which doesn't take a while to scroll down when searching the emulator cuz i almost fell for it

• 
  orneryostrich.cpp (@orneryostrich1) reported 46 minutes ago

  @portforward21 @tekbog One issue is that Aspect claims Bazel expertise but writes rules that break Bazel's internal model Also they blame the maintainers of TypeScript, Node, Esbuild... whenever something isn't optimal they try to get you to support them on some insane github issue they launched

• 
  *** (@uzairansar) reported 47 minutes ago

  @stocktalkweekly Anthropic has been severely rate limiting recently. GitHub copilot also took down their Student and Pro plans to serve compute to enterprise and higher tier customers.

• 
  James Andrew Gardner (@JGardner7082) reported 48 minutes ago

  @sakir_bulu99159 thinking how did some uneducated sob pull this off? #motives#gatekeeper🦅🦅🦈 the fix. permantly sits in github. no more distrabution ever after 11:59 tonite its gone forever. can not ever reproduce anything. it will be a dead code. only the chosen will get it. re writing morals.

• 
  Tone (@InOneProjects) reported 50 minutes ago

  @AIOnlyDeveloper I've fiddled a little, but it seems heavily biased toward repos in github/the cloud - is there a file system browser I'm not seeing that will let me select a different folder where I have an existing *** repo? The dev flow I'm liking right now is sending the agents to work in worktrees, then having them push the commit to a local review branch so I can just checkout among the local branches without needing to go through a PR process of pulling the changes down

• 
  sachin. (@sachinyadav699) reported 51 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

• 
  Must (@must_imusama) reported 51 minutes ago

  @Mohit_Goswami18 Yeah, I'm all about solving realworld problems through coding! Let's collab on GitHub and make something dope together

• 
  Sriram Kiron (@sriramkiron) reported 52 minutes ago

  i can write an issue/feature request for this on github if you'd like.

• 
  Nagarani (@SNagarani1419) reported 52 minutes ago

  @melobreaks True GitHub is the closest thing to “proof of work” in dev you can fake profiles but you can’t fake consistent commits, real projects, and problem-solving over time.

• 
  narcotic_nik 🍉 (@narcotic_nik) reported 55 minutes ago

  @skyfall_ggs @paytondev Cosmic is basically in pre alpha and they don't even look at the issue tracker on GitHub

• 
  Cynthia Ozumba (@CynthiaOzumba) reported 55 minutes ago

  Stop telling them you're a "Fast Learner." Show them a screen recording of a dashboard you built, a 1-page strategy you wrote, or a technical problem you solved. Link your Notion Portfolio or GitHub at the very top. Let the work speak before they even see your Location.

• 
  George Fahmy (@kajogo777) reported 1 hour ago

  Now people do cold outbound through open source github issues and PRs...this is ridiculous @github