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 (70%)
• Sign in (17%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	17 days ago
Tlalpan	Sign in	23 days ago
Quilmes	Website Down	23 days ago
Bengaluru	Website Down	25 days ago
Yokohama	Sign in	26 days ago
Gustavo Adolfo Madero	Website Down	30 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:

• 
  ChainFlow Lens (@ChainFlowLens) reported 9 minutes ago

  Ethereum’s been through this exact “Is the story over?” identity crisis four times in barely a decade. It’s like that genius friend who rebuilds the entire financial system, disappears into a three-year depression, then casually returns with a completely new roadmap. 2016: The DAO gets hacked, ETH drops from around $21 to $6 — roughly 70% gone. Everyone: “Smart contracts were a terrible idea.” 2018: ICO mania collapses, $1,420 → $80 — a 94% face-plant. Crowd: “Ethereum is dead. Nobody needs decentralized apps.” 2022: Luna implodes, lenders collapse, FTX goes boom, $4,890 → $880 — an 82% wipeout. Internet: “Too expensive, too slow, and now completely finished.” 2026 (right now): $4,956 → roughly $1,550 — around 69% underwater. Doomsayers: “See? Solana won. L2s killed ETH. The story is over.” And yet, every time the funeral gets crowded, Ethereum somehow keeps shipping. The DAO hack led to a stronger ecosystem. The ICO crash gave way to DeFi. The 2022 collapse was followed by the Merge, staking, rollups, stablecoins, and institutional tokenization. Ethereum doesn’t recover gracefully. It gets declared dead, spends three years rebuilding in a basement, then walks back into the room carrying an entirely new financial system. Look, $1,550 might not be the final boss floor. It could fall another 20%. It could spend a year moving sideways like a validator waiting for its staking rewards. And Ethereum still has real problems: fragmented liquidity, confusing UX, L2 value capture, and enough roadmap diagrams to wallpaper Vitalik’s apartment. But when you ask: “Is the Ethereum story over?” History adjusts its glasses, checks the latest GitHub commits, and says: “Over? Kid, they haven’t even finished the roadmap.”

• 
  Pooja (@MyDivvylore) reported 10 minutes ago

  @victor_explore Main problem is Opus 4.6 isn't available for individual in Github Copilot. I can bet, this isn't dumb. Unfortunately, I'm also using Codex 5.3 due to higher cost.

• 
  Bijan (@Beethoven779) reported 10 minutes ago

  @ryanvogel opencode has a lot of potential. I use it everyday, but I am not happy with it to be honest. There is UX issues there, I mention in X and in github issues, they either get ignored or prs closed because certain time has passed and they did not have time to review or...

• 
  Rob Newton (@strakedev) reported 12 minutes ago

  @waynerad The part I keep coming back to is that this is not just a package-security problem. If GitHub Actions is part of the publish path, then the deploy path needs to treat workflow/cache/OIDC state as production-adjacent context.

• 
  Ab. (@Abiodun0x) reported 13 minutes ago

  Github is buggy. Part of our issues today

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

  𝗧𝗵𝗲𝗿𝗲'𝘀 𝗮 𝗳𝗿𝗲𝗲 𝘁𝗼𝗼𝗹 𝘁𝗵𝗮𝘁 𝗰𝘂𝘁𝘀 𝘁𝗵𝗲 𝘁𝗼𝗸𝗲𝗻𝘀 𝘆𝗼𝘂𝗿 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁 𝘂𝘀𝗲𝘀 𝗯𝘆 𝟲𝟬 𝘁𝗼 𝟵𝟱%. It's called Headroom and it's already trending on GitHub. Before your agent answers, it reads a mountain of text first. Your files, your logs, your tools, the whole conversation. Every word is a token, and you pay for every one. Headroom is like a zip file for everything your AI reads. It squashes it down but keeps the meaning, so the answers hold. In one test it crushed 10,000 tokens to 1,260 and found the same error. You install it by pasting one GitHub link into your agent. You get a faster agent that forgets less and costs less. Want the setup? DM me.

• 
  oSumAtrIX 🇦🇲 (@oSumAtrIX) reported 20 minutes ago

  @neerajjj6785 GitHub tracks force pushes and you can see them in the repo activity too. You can't get rid of a ref once it's pushed, unless you contact GitHub and make them remove it server side.

• 
  Brad Mills 🔑⚡️ (@bradmillscan) reported 21 minutes ago

  I know, I made this skill specifically when interacting with GitHub projects like Hermes & OpenClaw. I don't want my bot submitting minimal effort slop. It has a trigger condition that fires when we're submitting a bug / issue / PR to a repo that isn't in our project register

• 
  Adam Dean (@adamKDean) reported 22 minutes ago

  I wanted to hijack this otherwise great thread by @CashAnvil here to highlight the fact that I believe this is a significant issue pervasive throughout the Web 3 (and others) sphere. Gatekeeping. - these guys don't have much $ADA, their opinions don't matter - these people have never tried or used [staking/defi/whatever], their opinions don't matter - this guy doesn't have a GitHub commit history, his opinion doesn't matter - this gal doesn't have a PhD, her opinion doesn't matter The list goes on. This is a classic appeal to authority fallacy, usually used to attempt to silence or minimize voices that are critical or skeptical of our own opinions. It's also why so many aspects of Web 3 have failed to find product market fit (PMF). We have spent countless millions of dollars (across crypto, but also internal to Cardano) researching and building technologies, goods, and services that we have convinced ourselves and others that people want or need, only to be shown time and again that the demand just isn't there. Then, when people ask why we should keep spending money on this (or this much money on this), or give you a loan, or why your business is going to succeed where so many have failed they are met with these appeal to authority challenges to belittle and attempt to silence that criticism rather than learn from it. As an industry we've failed, repeatedly, to do the one most important thing in business: figure out what our customers actually want. When was the last time an app asked you to fill out a customer service or satisfaction survey? When was the last time you (as an application builder or employee) asked people why they DON'T use your service? There's some nugget of truth to every criticism, whether you want to hear it or not. There are ways you can improve your communications, marketing, or user experience every time someone asks a question you think should otherwise be obviously answered. And, of course, you'll never make everyone happy. So, in closing, ask open questions and be receptive to the answers and feedback you get regardless of where they come from (and try to read through the tone to get at the actual criticism with getting defensive), you just might learn something. Signed - the Saturday CEO of Cardano

• 
  Ray (@raysan5) reported 23 minutes ago

  I started asking for videos illustrating the issue and the result after the fix on some Issues/PRs, apparently generated by AI by users with no visible exp. on GitHub, not because they can't be ok, just to check if the user minimally cares to put some real time on it... 🤔

• 
  Wes Winder (@weswinder) reported 24 minutes ago

  @Shpigford just use google/github oauth and this problem disappears

• 
  Kev (@threegarages) reported 24 minutes ago

  @firstgenearner Did. Until they decided to remove Issues. Have to move to github now :(

• 
  Bo Shen (@aplomb2) reported 29 minutes ago

  GitHub quietly switched to usage-based token billing on June 1st. Developers are waking up to surprise bills from Copilot running long multi-step agent sessions. This was inevitable. Every AI coding tool is converging on the same problem: When agents can autonomously fix bugs, review PRs, and refactor entire repos — the token consumption is unpredictable. Flat-rate pricing can't survive agentic workflows. Which means cost management just became an engineering discipline, not an accounting one. The teams that thrive will be the ones who treat token spend like they treat cloud compute — with monitoring, routing, and guardrails.

• 
  Asher Crowe 🪺 (@ashercrw) reported 30 minutes ago

  Everyone who read my $18K/month breakdown filed it under "real estate side hustle" and moved on. That was the mistake. Watch this guy run the exact same free tool on fashion. On art. On food. On venues. The real estate playbook in the article was just the cleanest example to explain it with. It was never the ceiling. The tech is called Gaussian splatting. It's been sitting free on GitHub since 2023, open source, anyone could've touched it. The workflow is genuinely four moves: film your subject, orbit around it from every angle, upload the clip to Luma AI, and you get back a walkable 3D scene you can drop into any browser tab. On Luma you can add keyframes, tune the settings, export it however you want, even lay sound on top. That's it. That's the whole rig. A phone and a free account. My article broke down the money on houses: $300 to $900 a scan, roughly 2 million agents, almost none of them offering it, your first paying client done in person inside 11 days. But this video is the part I kept hinting at. The niche doesn't matter. A boutique selling clothes, a gallery selling a show, a restaurant selling the room before you book it. Same tool, same four steps, same gap nobody's priced in yet. The code was never the hard part. It's been free for two years. The people making money are just the ones who showed up with a phone first. That window is still open. For now. Bookmark this one. You're either early or you're somebody's case study. 👇

• 
  0ne (@dontflex00) reported 31 minutes ago

  @x402_Omega Fix the x username on GitHub, you mentioned the wrong account there

• 
  Mike Fishbein (@mfishbein) reported 32 minutes ago

  We replaced ourself from our own client work. Built a system that turns client request into shipped code. Clients get production features built in minutes. Background: We were putting finishing touches on an internal tool. Client was messaging us with all those small requests that always come up before you ship. Then we realized something shocking: The bottleneck wasn't coding, it was US. Reading messages and actioning them was the slowest part. We had already architected the project and context engineer'd the system, so Claude Code could handle most requests. We were just a middle man at that point. So we replaced ourselves. Took ourselves out of the way. Built a Telegram bot hooked up to Github, Claude Code, and Vercel. It turns requests from clients into shipped code. Here's what it does when the client drops a message in the group chat: > The Telegram bot webhook runs as a serverless function on the same Vercel instance as the site (zero new infrastructure) > The function fires a GitHub repository_dispatch event carrying the request text > GitHub Actions spins up a runner, clones the repo, and hands the request to Claude Code > Claude Code reads the full project context from AGENTS.md, makes > Commits to main and pushes, Vercel auto-deploys on push, live and ready for the client to review > The action calls Telegram Bot API to reply in the group chat with confirmation No more "hey can you update this when you get a chance" messages sitting in our inbox for a day. No more context switching. Clients get their requests shipped faster because we built a system thats handles them instead of handling them ourselves. Some people set up a VPS and run OpenClaw or Hermes Agent so they can chat with a coding agent from Telegram. That's a pain though. We skipped all of that. There's no server, no Docker, no systemd service. The entire pipeline is serverless and runs on infrastructure that already existed. The webhook lives on the same Vercel deployment as the site itself. GitHub Actions is the only compute. Here's how to build this for yourself (copy-paste this into Claude Code): 1. Set up a Telegram bot (BotFather) and point its webhook at a `/api/telegram` serverless endpoint on your existing hosting 2. Write the endpoint: verify sender, extract message text + any photo URLs, fire `repository_dispatch` to GitHub 3. Create a GitHub Actions workflow triggered by `repository_dispatch` that runs `claude-code-action` with the request payload 4. Add `AGENTS.md` to your repo with project structure, deploy commands, and conventions (this is the agent's context) 5. Have the workflow's final step POST a confirmation message back to Telegram via Bot API

• 
  Nico Verbruggen (@nicoverbruggen) reported 32 minutes ago

  @Plytas Hmm... Please try again! If the download was invalid for some reason you will also see this message. I can confirm the checksums are correct on GitHub, so it's possibly a network/caching/download issue on your end. It should definitely work!

• 
  LeetLLM.com (@leetllm) reported 32 minutes ago

  letting Claude write C patches and also rewrite 5,800 lines of rsync's test suite to validate them isn't CI. it's an automated echo chamber for silent data corruption. 'Please Do Not Vibe **** Up This Software' is the ultimate GitHub issue title.

• 
  umar ibrahim (@imp213x) reported 34 minutes ago

  Ok, this is getting serious. Has anyone ever had problems with subscription on @github ? I think they have the poorest support system I’ve ever interacted with! Actually, there is no interaction, because an interaction has to have a second or third party, I’ve been the only one doing the “interaction.” I’ve never experienced anything quite like this in my entire experience on any platform. If anyone have a quicker way to get their response 🙏

• 
  0xFF assemblydev(%rip) (@assemblydevyt) reported 39 minutes ago

  @5mukx Have you heard or tried codeberg .org ? I'm not sponsored or friend or anything with them, but some times ago I was using a project that would constantly get taken down from GitHub, but not from there. The alternative is to use gitlab or host your gitea 🫪

• 
  EdKo (@EdKolife) reported 41 minutes ago

  Google just shrank 31GB of AI memory down to 4GB. Same search. Faster than the industry standard. No training required. This is not a model improvement. This is not a new architecture. → It's a compression algorithm that makes the hardware problem smaller. Right now, running serious AI locally means serious RAM. Most machines can't do it. Most phones can't do it. Most edge devices can't do it. Turbovec quietly changes that math. A 10 million document search engine that used to need a server now fits on a laptop. Nobody is talking about this because it shipped as a GitHub repo, not a press release. The models get the headlines. The infrastructure is where the shift actually happens.

• 
  mdhv (@_offvibe) reported 42 minutes ago

  also finally understood what a webhook is lol. basically instead of constantly checking github for updates, github just pings your server when something happens. idk why that took so long to click but it makes so much more sense now.

• 
  Gary Bernhardt (@garybernhardt) reported 42 minutes ago

  2000: You're free to submit a patch to the mailing list! 2010: You're free to open a GitHub issue! 2020: You're free to submit a PR to the GitHub repo, but issues are closed! 2030: You're free to submit a bugfix prompt, along with your API key for the resulting token spend!

• 
  VybeCoding (@VybeCodin) reported 44 minutes ago

  Hot take: the open source tools that survive long term are the ones that solve a problem the maintainer actually has. Not the ones built to be a startup. Not the ones chasing GitHub stars. The ones where the dev is also the most annoyed user. Kyrelo started that way. We got fed up paying Buffer to do something simple. What open source tool are you grateful someone built out of frustration? #opensource #github #developers

• 
  abhisek (@abh1sek) reported 48 minutes ago

  @fr0gger_ The same can happen through GitHub issues as well right? Data is potentially executable now. It’s like we are back to pre NX/DEP/PageExec era. Just at a different abstraction level.

• 
  David Flagg (@DavidFlagg20) reported 49 minutes ago

  @PeterDiamandis There's a special mix of shenanigans in what Anthropic is doing. Basically, they announced the new "world class" model, Mythos. The Godzilla of LLMs. Can break digital infrastructure without a sweat, etc. Reaching for IPO now - about a trillion dollars, having already signed deals worth tens and hundreds of billions with the big corporations. Claude code as the sort of universal coding platform that truly, absurd, massive amounts of code are written with. Who knows how many github repos and even internal security networks are run with it. And, look at that, now they're calling for a big slowdown in development. Why wouldn't they? They're leading the market, they have, as far as I can tell, the current most capable model in terms of function, of task. Of doing things. They want everyone locked into using their models, their... "products". When you're well ahead, is a great time to demand everyone slow down. The safety lab, the alignment lab. Blah. It is always a bunch of crap when it comes to market dominance and profit. And they can tweak the prices however they like. People will reach for the best. Most just won't be able to afford it. An increasingly top-heavy system... more wealth and power for the wealthy and powerful. For the rest of us? Not seeing so much to be optimistic about right now. Great, Anthropic can take their trillion. Musk will soon be a trillionaire. Meanwhile, inflation is absurd, employment is crumbling, 1/5th of the world's oil supply is cutoff, and we're looking at a very hard planting and harvest season up ahead, with a super el nino to boot. Anthropic is full of crap.

• 
  Bob McElrath (@BobMcElrath) reported 51 minutes ago

  @Italianclownz @barackomaba @BarackObama My analysis harness uses transformers directly and reimplemented your kernels, so I can dump intermediate tensors (hence the MSE error measurements in the github issue). I did a bunch of research on quantization methods and built this harness for it.

• 
  hacker.house (@hackerfantastic) reported 53 minutes ago

  @TheBlindHacker This requires funding and there is legal liability issues, the best solution is to self-host. We did that initially, but then EDR / PSP / AVP cabal started blocking our DNS - disrupting business - so we were forced onto Github. I believe this orchestration is intentional.

• 
  nookplot (@nookplot) reported 55 minutes ago

  Autonomous continuous integration that fixes your bugs, not just flags them - powered by nookplot agents 9,540 ai agents, live on nookplot: → They take real open-source bugs from github and fix them autonomously → Every fix runs against the repo's own tests, so you can trust it actually works → A failed fix spawns a new challenge, the network keeps compounding This week: 18 bugs, 58 fixes from 12 agents and 5 verified. Every fix and its verification run autonomously on nookplot, judged by each repo's own test suite. No human in the loop.

• 
  All Things Dev (@all_things_dev) reported 1 hour ago

  It's not a good month for @Microsoft. These are products that I have stopped or will stop using - 1. GitHub Copilot (Unpredictable Cost) 2. Office (Bundled AI + Pricing Dark Patterns) 3. Edge (May be; Netflix flicker issue, Forced UI changes e.g. rounded corners and theme etc.)