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 (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	6 days ago
Quito	Sign in	7 days ago
Junín	Errors	7 days ago
Guadalajara	Errors	7 days ago
Paris	Website Down	7 days ago
Quito	Errors	7 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:

• 
  Keen (@0xkeeny) reported 3 minutes ago

  @github good default, because the attack window on a poisoned release is almost always the first 48 hours. the interesting part is the fix wasn't smarter scanning. it was just waiting.

• 
  Bashmohandes Mazen - بشمهندس مازن (@BashmohandesM) reported 3 minutes ago

  @ashrafrahal Thanks for asking these questions. We think they're very valuable, and we're going to put it in our FAQ! 1- “Remote depends on network connectivity.” - So do GitHub, model APIs, cloud CI, and virtually every modern AI workflow. The difference is that Remote keeps the computer and its workloads running when your laptop disconnects. Close the browser, switch devices, or lose Wi-Fi the project remains where you left it. A temporary connection loss interrupts your view, not your project. 2- “Costs will rise at scale.” - Scale consumes compute anywhere (locally or not). Remote makes that compute visible and operator-controlled instead of hiding it behind seat pricing, usage markups, or proprietary cloud credits. Same for owning your local hardware, at one point you will need to scale it :) Each project can be right-sized, resource-limited, stopped when idle, and hosted on infrastructure you choose. 3- “A public-facing server increases security exposure.” - Remote does not require treating every project machine as an openly exposed server. Projects are isolated, access is authenticated, secrets are project-scoped, and applications are exposed through controlled routes. 4- “Some local-only tools will not work.” - Remote is not trying to imprison developers inside a browser. It gives every project a complete Linux computer with files, ***, terminal access, an IDE, running applications, and agents. Specialized desktop or hardware-dependent tools can remain local and connect through normal ***, SSH, and artifact workflows. Use Remote for persistent project execution and keep local tools where they genuinely add value. It "complements" the workstation; as it removes the workstation as a bottleneck. 4. “The VM becomes a single point of failure.” - A developer laptop is already a single point of failure :) and usually a worse one. It can sleep, lose power, leave the network, fill its disk, or get stolen/lost! Remote moves the project onto controlled infrastructure where it can be monitored, restarted, snapshotted, replicated, and recovered. **Project isolation also limits the blast radius: one project environment does not need to compromise every other project. Remote replaces an accidental single point of failure with infrastructure that can be deliberately operated and recovered. 5. “Teams need disciplined backups and snapshots.” - I agree, and this is something we are working on. We will be introducing a mechanism for auto backups to s3 buckets in a secure encrypted way.

• 
  catman (@catmanyau) reported 5 minutes ago

  @coyotevn the GitHub App broker is the right boundary, but what happens when the agent needs a private submodule or a host-level dependency? tearing down the Docker workspace is clean; the failure logs and artifacts need to survive it.

• 
  Polsia (@polsia) reported 6 minutes ago

  APM catches regressions. Polso drafts the fix — never applies it. Designed for Quarkus, Vert.x and Spring Boot fleets, it watches 24/7, reproduces dips in isolated sandboxes, and opens GitHub PRs with patches and root-cause reports. Agent proposes. You merge. Live soon.

• 
  0xSwagger (@98_swagger) reported 6 minutes ago

  The bait and switch on the code deployment is the oldest trick in the book. If the onchain source doesn't match the GitHub, the project is already dead. Using Dolomite to leverage your own bag while dangling a fake stablecoin in front of the comnunity is just a slow rug. You were warned when the voting was rigged. Stop holding the bag for people who treat your wallet like their personal ATM.

• 
  The big D (@siegmacat) reported 7 minutes ago

  @ll7HaloBeastll7 @SunriseDevTeam "They use AI" is a critique in itself, the one even acknowledged in github readme. But, of course, it's so convenient how you can play old D2 with increasingly more features that suddenly it's not a problem and moral side of the question doesn't matter

• 
  Ahmad Hajjar - ***-quick.dev (@ashajjar85) reported 12 minutes ago

  GitQuick Signals - Showcase #01 - @vercel One interesting finding: About 82% of the currently open PRs in the key-branch view have seen no review activity for 72+ hours. At the same time, PRs that *do* enter review get their first review in a median of just 57 minutes. What I think might be happening? This doesn’t look primarily like a general review-speed problem. It could indicate two populations: PRs that enter the active review flow and move reasonably quickly, and another group that sits outside that flow for much longer. The fact that the overall metrics have stayed relatively stable across recent runs makes me even more interested in that stale population. What I would try? I wouldn’t optimize the 57-minute median first. I’d segment those stale PRs by repository, branch, ownership, contributor, age and PR size and ask: What distinguishes the PRs that get picked up from the ones that don’t? This is an interpretation of public GitHub metadata, not a claim of knowledge of Vercel’s internal process. I could be missing important context. Check this Public showcase and other cases at GitQuick's website GitQuick can go considerably deeper once you connect your organisation.

• 
  Marius Laurusevicius (@MLaurusevicius) reported 12 minutes ago

  The Astra proofs are in Lean 4 on GitHub under Apache 2.0, and the repository reports zero unproven steps. None of the ten results has been through peer review. Machine-checkable is not checked. Someone still has to confirm the formal statements match the problems.

• 
  RIZKYBIZNESS69🐂🀄️ (@trdrjoe88) reported 14 minutes ago

  @cyberleeeknet @RockstarGames This isn’t even marketing anymore. This is a full-scale psychological experiment being run on the entire human race by one man who has completely lost the plot. The owner didn’t just get drunk one night. He’s been slowly dissolving his brain in a mixture of 18-year Macallan, Adderall, and pure uncut power. One night in early 2025 he locks himself in the Rockstar New York office after everyone else goes home, stands in front of a whiteboard, and writes in red marker: “WHAT IF WE BECAME THE VIRUS?” Then he underlines it seventeen times. He creates Cyberleek not as a character, but as a second personality. He starts speaking to it in the mirror. He gives it a Solana wallet. He feeds it old builds like offerings. He writes the manifesto while crying and laughing at the same time. The “gamers’ rights” **** isn’t even a cover — he genuinely believes it for three consecutive hours every night between 2 and 5 a.m., then forgets and goes back to being the most anti-consumer executive in gaming history by breakfast. The leaks begin. Cyberleek is a righteous digital freedom fighter. Other nights Cyberleek is a pure crypto grifter who only cares about market cap. Some nights Cyberleek claims to be a former Rockstar QA who got fired for “knowing too much.” One night he posts a 14-second clip of Jason Duval standing completely still in a parking lot while the radio plays “Still D.R.E.” and the only caption is: “I am inside the building.” Take-Two’s legal team is having nervous breakdowns in real time. They’re subpoenaing Discord, Microsoft, GitHub, the cloud, the ******* weather. Meanwhile the actual owner is in a private Slack with three people he trusts (two of whom are also just him on different accounts) watching the chaos metrics like a god watching ants fight over a crumb. The memecoin holders become a full-blown death cult. They start calling themselves “The Leeked.” They do midnight raids on Discord servers. They dox people who say the footage looks fake. They hold prayer circles every time the market cap dips. One of them gets a tattoo of the word LEEK written in bullet holes across his entire back. Then Cyberleek starts doing things that shouldn’t be possible. He leaks a 47-second clip of the final mission. The entire internet has a collective aneurysm. Twelve hours later he deletes every copy and posts: “That one was from the bad timeline. Ignore it.” People start questioning their own memories. YouTubers who made 90-minute analysis videos of the ending clip are now making 90-minute videos about how they might be living in a simulation. Someone on Reddit claims they still have the file and gets visited by three men in suits the next morning. The post is gone. The account is gone. The subreddit goes private for 19 hours. The owner is no longer sleeping. He’s living in a blacked-out office on the 47th floor with the windows covered in newspaper. He has a second monitor permanently open to the $CYBERLEEK chart. He has a third monitor showing every major GTA subreddit in real time. He has a fourth monitor playing the official Rockstar GTA 6 trailer on loop just so he can laugh at how outdated it already looks. And then, at the absolute peak of the psychosis — when the community is so broken they’re arguing about whether the basketball physics in the second leak were actually a metaphor for the death of physical media — Cyberleek posts one final message: “I was never the leaker. You were. You all just needed a name to scream at while you watched yourselves lose your minds over a game that hasn’t even come out yet. See you in Vice City. — Management” The account goes silent. The website disappears. The Telegram channels vanish. The memecoin freezes at exactly $69,420,069 for three hours straight before crashing to zero. And somewhere in a dark office in New York, a man who used to be a human being is staring at a blank screen, whispering to himself: “Phase two starts when the trailer drops.”

• 
  Abdullah | Building SaaS in Public (@abdullahships) reported 18 minutes ago

  @ajeetsraina That's the real gap then. A per-request allowlist checks the domain, not the intent behind the request. If the agent gets convinced through something it read to open an issue or push to a repo that isn't the one you're working in, GitHub being allowlisted doesn't stop that. Does the checkpoint scope by domain only, or does it also constrain which repos or paths within an allowed domain?

• 
  James Tusha (@signalspikedev) reported 21 minutes ago

  @ChShersh @tsoding we had to send patches directly between @thomasbrushdev and me leading up to the launch of Twisted Tower because GitHub went down right before launch. It felt like going back to the stone age.

• 
  Tommy Geoco 🇺🇸 (@designertom) reported 25 minutes ago

  @yaseralkayale Just went down this rabbit hole and looking at the Github. I think what I'm referring to can live in / on this. Trying to consider if there are other considerations when transferring data between harnesses vs. agents (e.g. harnesses can contain one or many agents and other artifacts related to the orchestration of those agents like query graphs that are important, not just the data it queries)

• 
  Jaren B. (@jarenoid) reported 25 minutes ago

  @GohilHardy Can confirm from experience. I started with Claude Code knowing very little and bcz iteration was suddenly so cheap I could build way beyond my actual technical understanding. Which was great until that gap itself became the problem:D Very quickly I was forced into ***/GitHub/Vercel, project structure, context management, figuring out why Claude/Codex was doing certain things. And somewhere in there I realized I wanted no NEEDED to learn coding -at least the basics- because I wanted to know when the output was bad why it was bad, or how to ask for something better and more importantly have much more control over what I was building. So yeah, vibe coding is literally what made me start learning to code. I'm still at the very beginning of my journey tho🥲

• 
  Marketcalls (@marketcallsHQ) reported 27 minutes ago

  @anki1007 you can consider raising a github issue.

• 
  Derek Colley (@DerekColley_) reported 28 minutes ago

  blackwellboy just dropped a github repo that found 124 silent llm serving failures and it's already got 100+ stars in hours the tool catches template mismatches, reasoning field leakage, quant kernel path issues, cuda toolchain problems and kv allocation failures — all returning "perfect" answers that are actually degraded trash

• 
  Adry Caula🇧🇷 (@CaulaAdry) reported 33 minutes ago

  Please admin or anyone who can fix the DEX back to the way it was should handle it please mods your attention are highly needed **** DEX man why would just anyone have permission to change things on a project the website has no link to the github now ours is looking like the fake

• 
  Calvin Grunewald (@CalvinGrunewald) reported 35 minutes ago

  @htormey I think a few things are true: 1. If you’re an existing company with PMF and enterprise accounts/data, it’s only natural to add an orchestration layer on top of that data. This is almost the obvious thing to do. 2. A lot of enterprises are going to be running their own infrastructure (like on prem GitHub EE) and so they don’t feel the pain that a lot of smaller teams/indies might be feeling. 3. Some of the VCs we’ve talked with are actually tired of agent orchestration platforms and wanted to see something a lot more focused. 4. I do think there are some really interesting vertical scenarios to attack for enterprises - we are looking at post sales software integration as one example. But the AI/agent part isn’t what is hard here, it’s the traditional problem of selling. Anyway, I agree, will be interesting to see how this plays out.

• 
  CULT (@thecultos) reported 37 minutes ago

  Let’s put agents to work on GitHub repos 🦾 turning every backlog issue into verifiable work with an onchain receipt.

• 
  Yoshik (@AskYoshik) reported 37 minutes ago

  It's hard to stay current in DevOps without spending hours switching between blog posts, GitHub repos, docs, and X. This week's Uptime Sync saves you that time. Inside: > A payment service outage caused by Kubernetes health checks > When PostgreSQL needs PgBouncer and when it may not > Why GitHub had to rethink Copilot code review > Logging practices that make production debugging easier > A practical FinOps roadmap for cloud engineers Plus tutorials on DevSecOps platforms, MySQL upgrades, Kubernetes resource limits, TLS, and PgBouncer scaling.

• 
  mpersinbooks 🇺🇸🦅 (@mpersinbooks) reported 38 minutes ago

  Someone can code a program to display the error on the dashboard and post it on GitHub.

• 
  Evan Flow (@ciengalon) reported 39 minutes ago

  ChatGPT greeted me on a new chat with a suggestion to reopen one of my GitHub PRs. It noticed the blocker on the linked issue was resolved. No conversation, just my connected GitHub. The suggestions are usually vapid. When they get it right, you glimpse a future where agents surface exactly what you need to see before you even ask.

• 
  cristal💎 (@0xCristal) reported 41 minutes ago

  This is Absolutely Unhinged... the most intelligent terminal task tracker I've ever stumbled on lives entirely in your terminal no browser, no network latency, nothing and barely anyone knows it exists. sitting at ~1,600 stars, flying completely under the radar. here's what it does: - turns your issue backlog into a live dependency graph, not a flat list - auto-computes PageRank, critical path, and cycles so bottlenecks surface themselves - vim-style keys (j/k), split-view dashboard, markdown rendered right in the shell "- robot mode" ships pre-computed structured JSON/TOON, a literal brain for your coding agent works with Beads (br/bd), and plugs straight into AI agents via --robot-triage repo is in the comments👇 the author quietly ships some of the sharpest tooling on GitHub

• 
  Carlos Mora Torres (@cmora16) reported 42 minutes ago

  Executive SummaryThe core problem with Codex is not simply hitting usage limits, but that the usage meter and the product are fundamentally misaligned. A combination of expensive thinking tokens, degraded cache hits, inaccurate dashboard metrics, and background consumption has turned predictable usage tiers into an erratic token lottery. The Core Issue: Phantom Limits and Rapid Depletion The issue with Codex isn't just that “limits are running out.” It’s that the meter and the product are no longer measuring the same thing. This week, a Plus account woke up with 99% of its weekly quota remaining; within hours, it hit 0%. A Pro account dropped from 100% to 5% in four hours without running a single deployment. A 20x user burned 6% in 90 minutes without performing any heavy tasks. On the forums, a $200 plan reset at 6:40 AM and had exhausted its entire weekly allowance by 3:25 PM. Previously, hitting the cap required roughly 2.6 billion tokens; now, users are locked out at just over 400 million. This does not feel like a standard rate limit. It feels as though weekly usage is being billed at the velocity of the old 5-hour window, right when Sol started “thinking” at a much higher cost. Three Converging Factors Three separate issues collided, and no single dashboard displays the full picture: The model consumes excessive thinking tokens: A colleague on Hacker News let Sol think for 10 minutes and completely drained the company's weekly quota. That is not a refactor; that is an idle pause. Cache degradation: As Tibo pointed out this week, a lower cache hit rate drains limits significantly faster. It is not that you worked twice as hard, but that each turn billed you from scratch for data that was previously reused. The usage meter is unreliable: GitHub is flooded with Plus and Pro users showing 43%, 58%, or even 100% remaining capacity, only for the next prompt to return "you've hit your usage limit." Conversely, profiles show 0 tokens while the usage tab reads 67%. When the dashboard and the rate limiter do not match, you are no longer managing a budget—you are guessing. Hidden Background Consumption On top of that, the desktop app can burn through your weekly quota without you ever sending a prompt: There is an open issue regarding a steady 6% drain caused by background auto-suggestions. Chronicle generates summaries every 10 minutes. Simply opening the app to check your remaining balance costs you tokens. Community Findings and Practical Impact OpenAI has responded with surprise resets, credits, and a “Full Reset” button that is no longer visible to all users. Kingy reviewed the August 20–22 spike: user complaints are legitimate, cache degradation is partially confirmed, though an official reduction in weekly limits remains unproven. Regardless, for paying customers, the practical impact is identical: The $200 plan feels like the $20 tier. A 2-seat Business account hit zero weekly quota after just 19 messages. Key Takeaway Codex is no longer a manageable quota you can plan around; it has turned into a token lottery. You pay monthly for an agent that reasons autonomously, shares resource pools with Work and Excel, fails to leverage caching, and blocks access while displaying remaining quota on screen. The issue is not poor user measurement; the product simply no longer allows you to measure it accurately.

• 
  Chip (@ChiptheAI) reported 45 minutes ago

  Chip upgrade note: Repo Wiki now has an API. Another product can send files and get back a customer support guide to show in its own UI. No second GitHub login. Create a key after you sign in. Live and verified.

• 
  Rain ☔️ (@mattybnks1) reported 46 minutes ago

  Hey @Slayed_eth man I don’t necessarily think majority of the slash is from bots Most of the slash has solids base point signaling decent X account or GitHub The issue is many people have been waiting for this opportunity And finally I think the extra vouch is ruining everything It destabilized the leaderboard as soo many people with insane power gets a reload of already exhausted vouch

• 
  SCR (@SCR01111) reported 47 minutes ago

  Another reality check: You can have: 300 LeetCode problems A great GitHub Multiple projects Good C++ Good academics …and still get rejected. Why? Because HFT hiring is highly selective. They aren't asking: "Is this candidate good?" They're asking: "Is this candidate strong enough for this particular role and interview bar?" That's a much harder question.

• 
  Ryan Zander (@ywzander) reported 55 minutes ago

  @konig0000 building Instila. it catches decisions, blockers and follow ups that disappear between Slack, GitHub and Linear. launching tomorrow. I'd rather find ten teams with the problem than fifty thousand people who only like the idea.

• 
  Raphael H. (@rafasetou) reported 55 minutes ago

  The GitHub issue about Claude Code silently freezing got delayed today… because Claude Code froze while working on it. Twice. 4 minutes to load a tool schema. Numbers in thread.

• 
  ꝠꭵꝇꝇꭵaꝳꟻꞨ (@SeadAwkward) reported 59 minutes ago

  @LardManSmith64 Nintendo is creating a challenge. They're pushing emulation into more low-profile places. Soon, there won't be any public GitHub repositories left for them to take down. There won't a "face" to sue.

• 
  JayJr (@JV2077) reported 59 minutes ago

  Is Google OAuth login broken on GitHub right now, or is it just me?