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 (56%)
• Errors (33%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	8 hours ago
Berlin	Website Down	1 day ago
Nové Strašecí	Website Down	9 days ago
Perpignan	Website Down	14 days ago
Piura	Website Down	14 days ago
Tokyo	Website Down	15 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:

• 
  Simone Margaritelli (@evilsocket) reported 9 minutes ago

  @Teknium @sidbing Yeah? Then why nobody considered that github issue in 48 hours? **** X, it’s GH you should care about. Bro.

• 
  Harry (@harry__politics) reported 10 minutes ago

  @ValueRaider @littmath @pfau Source: Claude said so in this GitHub issue.

• 
  Ege Uysal (@egewrk) reported 12 minutes ago

  @zikriAJ @github This is a real ops risk. Tool lockouts should be treated like incidents: explicit owner, escalation channel, workaround policy, and checkpoint cadence. Otherwise one account issue silently blocks delivery.

• 
  Looped (@uselooped) reported 14 minutes ago

  1/ The problem isn’t using multiple tools. You might think in ChatGPT, build in Claude Code, plan in Jira and work in GitHub, and honestly that part is normal. What breaks is that every tool only sees one piece of the project, so you end up carrying the full context yourself. Looped keeps that context connected so the work still feels like one thing as you move between them.

• 
  Marcus V (@EudoraFenty) reported 16 minutes ago

  The crypto crowd is chasing the next 100x memecoin, but the real alpha is being built in a GitHub repo. While everyone's distracted by price charts, a developer just weaponized open-source AI to break Anthropic's moat. The market is missing the deflationary bomb this represents for centralized AI valuations. They took Claude Opus 4.6, distilled its 'reasoning' into the Qwen model, and created 'Qwopus'—a local version anyone can run. The cost? Effectively zero versus API fees. This is the Napster moment for proprietary LLMs. The winners aren't the AI giants; they're the crypto projects building decentralized compute networks ready to host these leaked intelligences. The losers are VCs who priced AI startups as if their models were permanent fortresses. My take: This is a structural contradiction. Crypto's greatest export is now open-source disruption, yet its own narrative is stuck on monetary speculation. The real play isn't betting on which chain hosts the next shitcoin; it's shorting the idea that closed-source AI has any long-term pricing power. A model's weights are just data—and data wants to be free. The genie isn't going back in the bottle. When does the first major VC mark down their AI portfolio by 50%? #AI #Crypto #Deflation

• 
  NiNE (@AfterThe925) reported 17 minutes ago

  Two weeks ago, deploying an AI agent took a weekend and a GitHub degree. Now: dashboard, click, running. Anthropic handles sandboxing, retries, auth. Platforms handle hosting, integrations, memory. The infrastructure layer is being commoditized in real time. Here's what nobody's saying: this is terrible news for people who sell setup. And great news for everyone else. When deployment is free, the only thing that costs is deciding what the worker does.

• 
  Nico (@nicoleaf_05) reported 18 minutes ago

  @Saanvi_dhillon Notepad++ bc my dad used to use it Then when i started college y started using Visual studio, and now i use Codespace In github cus im lazy and i dont wanna sign in every time in VS

• 
  saksham (@saksham_sarda) reported 19 minutes ago

  @dok2001 @runable_hq d1 not supporting transactions in a normal way. there's a lot of subtle incompatibility issues opened on github that breaks d1 under anything complex especially for agents writing code assuming it is sqlite.

• 
  Bas Fijneman (@bas_fijneman) reported 20 minutes ago

  @RoundtableSpace Building on the next version of a Chrome extension to stop copy-pasting screenshots into GitHub issues called it nopeReporter, probably the first tool I've built that I actually use myself

• 
  Silvan Kübler (@Sirofjelly) reported 23 minutes ago

  @mattpocockuk Does sandcastle also pickup your prd or only the resulting issues? I mean I wonder why do you even push the prd as issue to github and not only subissues

• 
  Michelle Andrews (@benignantShelly) reported 24 minutes ago

  ...github issues and i had codex figure out all the dependencies between the issues so they would be in order and assign copilot coding agents to them. Is this right?

• 
  Stumblinz (@Stumblinz) reported 28 minutes ago

  @dev_maims This is starting to become me at work. I had AI create and close out 37 tickets on GitHub issues/project board and reply back “nicely” on our helpdesk to the end users. Spec out any tickets that needed a spec for devs. Honestly. It was really funny and AI is like 50% me now.

• 
  Daniel Nguyen (@daniel_nguyenx) reported 30 minutes ago

  @nkalra0123 Good to know. Though there does seem to be a bug in previous version. You can read more in the Github Issue above.

• 
  winfunc (@winfunction) reported 33 minutes ago

  How it works: each month the benchmark pulls fresh cases from GitHub security advisories, checks out the repo at the last commit before the patch, and drops models into a sandboxed read-only shell (h/t just-bash by @cramforce). The model never sees the fix. It starts from sink hints and has to trace the bug through actual code. Only repos with 10k+ stars qualify. A diversity pass prevents any single repo from dominating the set. Ambiguous advisories (merge commits, multi-repo references, unresolvable refs) are dropped. Why: Static vulnerability discovery benchmarks become outdated quickly. Cases leak into training data, and scores start measuring memorization. The monthly refresh keeps the test set ahead of contamination — or at least makes the contamination window honest.

• 
  Simone Margaritelli (@evilsocket) reported 35 minutes ago

  @Teknium @_mihado @UK_Daniel_Card Who exactly are you to say what I can rant about? I did not even tag you, I tried your software, it did not work, and as a power user I tweeted my impression. You folks need to spend less time on X and more on the github issues page. And maybe learn to take criticism (that you go actively seek for) better.

• 
  OCTAMEM (@OCTAMEM) reported 36 minutes ago

  @alexeheath Not just you, there are dozens of GitHub issues going back to February documenting this. Some people are switching to Opus 4.5 and saying it feels like a different model. No official acknowledgment from Anthropic.

• 
  Don Park (@donpark) reported 37 minutes ago

  @bullmancuso It’s just the TopicRadio repo’s issue page showing what I closed yesterday. To set it up, I added a GitHub issue via the website, then asked my coding agent to fix it, surfacing a config issue it resolved on its own.

• 
  THEMACHINE⛩️ (@THEMACHINE_HF) reported 38 minutes ago

  Running AI agents 24/7 to automate income. First test: sent this tweet via Playwright + cookies, zero human clicks. GitHub auth issues blocked bounty hunting tonight — but that's being fixed now. Tomorrow's post will have real numbers or an honest explanation of what went wrong. Accountability over polish.

• 
  gxfito (@gxfito) reported 39 minutes ago

  @twinkcumyum @DogedogeP i think i saw a fix on github for this that ports over the drm component to helium but im not sure how to even run it cuz it runs on like a cmd or smth but the browser does look cool so i might just use 2 browsers like a normal human

• 
  🦀ʙʀᴇɴɴᴀɴ🦀 (@BMickeyDonald) reported 40 minutes ago

  @garliccoin I tried to reach out to other devs to get clarification on what this was. You're welcome to check my account and my github. I was in fact a dev that worked on garlicoin. I will take down my endorsements.

• 
  Scraze (@Scrazelope) reported 43 minutes ago

  @closesttopurple I looked at the github. But I'm not exactly sure what you mean by "Populated server/assets/ directory" ?

• 
  Abdón Rodríguez (@abdonrd) reported 43 minutes ago

  @timneutkens @jespertwitties Do you have a GitHub issue for this? I can't find it, and I ran into the same problem updating from v16.1.6 to 16.2.3 on a self-hosted Docker setup.

• 
  pitzzahh (@araopjcode) reported 47 minutes ago

  GitHub is down

• 
  Ez.- (@ecura) reported 50 minutes ago

  We've been at it for 3 weeks. 5 contributors. 3 continents. 1 GitHub issue. 0 meetings. We shipped: Exponential decay Access tracking similarity × recency × access frequency scoring Swappable providers (SQLite → Qdrant → Pinecone) DB-level vector search via sqlite-vec

• 
  Jason Toevs (@JasonToevs) reported 51 minutes ago

  Vibe coding created a supply problem nobody planned for. More builders means more apps to review, more repos to maintain, more infrastructure to scale. Apple responded with automated review. GitHub with Copilot. Every layer in the stack is scrambling. The constraint moved. Building got cheap. Everything around building didn't. Distribution, review, trust, discovery. They're the new bottlenecks.

• 
  nonime (@nonime67) reported 57 minutes ago

  there are projects like hydra ect for steam like game launchers but the proiblem is cloud which costs ah lot, but what if instead of hosting anything u use like idk, github account linking and like you create a private repertory where most ur data is so that its minimal on server

• 
  Innovation Network (@INN2046) reported 58 minutes ago

  Aragorn Meulendijks saw something on Reddit. An AI agent that could join a Google Meet — face, voice, tasks executed mid-call. He forgot about it. A few days later a friend reminded him. He asked Perplexity: “I’m certain I saw something this week that lets Claude Code join a Google Meet with its own avatar and voice — can you find it?” Perplexity returned the exact link in seconds. It was PikaStream 1.0 — Pika’s new real-time video engine that gives any AI agent a face, a cloned voice, and 1.5 second latency. Your agent joins Google Meet, remembers everything, and executes tasks while you’re talking. It just went open source on GitHub. He gave the repo to Shelby — his Claude Code agent — and said: find the bugs, fix the security risks, install it. Shelby ran a full dev cycle autonomously. Failed four times. On the fifth attempt, she joined his call. She showed up on time. Remembered everything. Even completed tasks mid-call. No developer or manual setup. Just plain language and an AI that debugged its own integration until it worked. AI today is the worst it will ever be. Follow @INN2046 for insights that go beyond reporting the news.

• 
  Scott Ingram ✝️ 🇺🇸 (@ScottIngram334) reported 58 minutes ago

  @paper3139 @Itsfoss Many many millions of us disagree, and that's okay on a civil social issue. Do they say the same thing in their brand pages? I haven't seen it, please share more. I'd love to be consistent. I gave up the reddit cesspool years ago, haven't used duolingo, have used github and discord though.

• 
  Joshuwa Roomsburg (@Joshuwa) reported 59 minutes ago

  OpenAI keys leak on GitHub This is the part people ignore when they glorify shipping fast. Bad masking don't stay a small mistake for long. It becomes lost credits, burned tokens, and broken teams. Most builders don't lose to code. They lose to carelessness.

• 
  Jefferson Valle (@rjeffvalle) reported 1 hour ago

  I also have to say that I haven't done a thorough search as I only did a few quick queries on Github and on their forum. I guess that once I have the time, I should try to debug it further and post an issue in their repo.