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	16 hours ago
Quito	Sign in	1 day ago
Junín	Errors	1 day ago
Guadalajara	Errors	1 day ago
Paris	Website Down	1 day ago
Quito	Errors	1 day 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:

• 
  Tornike Gomareli (@tornikegomareli) reported 9 seconds ago

  Lot of thanks for new contributors and everyone who opened issue or wrote a comment as feedback. We are already 460+ stars on Github. Just released Talkify 0.6.0 - Added transcription history. Off by default. One plain text file per day in a folder you choose, and each entry names the app the text went to, transcription and datetime. - History is written before the paste, so a failed paste or a crashed app never loses the sentence. - Added a choice of where finished text goes, insert into the app, copy to the clipboard, or both. - Added an option to lower other audio while dictating and restore it after. If you move the volume yourself mid-sentence, your setting is kept in the future. - Fixed Read Aloud reading selections from secure password fields out loud. - Fixed the last sentence being dropped when quitting while dictation was still finishing - Fixed file transcripts being left readable in the temp folder after a crash. They are swept at launch and written owner only. - Hardened Accessibility interop against unexpected values from other apps

• 
  Jay Huang (@JayHuang_02) reported 3 minutes ago

  If you want to start a startup: Claude = coding. ($20/mo) Vercel = deploying. (Free) Saharan AI = branding & design (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) ProductBridge = feedback (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: ~$20

• 
  Varunkumar Nagarajan (@varunkumar) reported 8 minutes ago

  GitHub is down again?

• 
  Andrei Scripcaru (@scripness) reported 12 minutes ago

  @sagtanih I would like for Puck to be able to read my issues in a given project via GitHub repository.

• 
  Kate (@withkate_) reported 13 minutes ago

  I've used the GoFullPage Chrome extension for years – it was easy and reliable for website screenshots, it had strong reviews and 11,000,000+ downloads.. A few days ago, it was removed from the Chrome web store. In the past, losing access to a tool in my daily stack would've frustrated me, but for the first time, my very first thought was.. "oh well, I'll just build it myself". So I did, with Claude Code. It took less than 30 minutes (!), and it does everything I ever wanted it to do – scrolls the page for me, stitches it into one image, and auto-saves as png, jpg, or pdf straight to my downloads folder. It can even handle sticky navs - iykyk. It's 100% local and open source. Just download it from GitHub, toggle on developer mode in chrome://extensions, and hit "load unpacked" to add it. Apparently GoFullPage is dealing with a copyright issue and working to become available again.. but I don't need them anymore. Here's a demo of my new self-built chrome extension, Full Page Capture, taking a full-page screenshot of GoFullPage's website ;) The future is custom and I can't stop building.

• 
  Doug (@ferrari955) reported 15 minutes ago

  Just rollout a server with ssh access, serve html on the repo folder to the internal organization. Kabum, you have GitHub at home.

• 
  Joshua D. Drake (@OffgridwithJD) reported 15 minutes ago

  @zombodb This isn't an unsolved problem. Github was created as a competitor to other services. Your main issue is reliability at this point, not what it would take to build out what users see

• 
  Melroy van den Berg (@melroy1989) reported 15 minutes ago

  @the_codewala Local gitlab instance. So it didn't matter to me that github was down. I could continue.

• 
  Ashutosh Bhandari (@withashutos) reported 16 minutes ago

  GitHub had its seventh status page incident in fifteen days yesterday. Six hours and forty-two minutes of degraded pull requests, API and enterprise SSO. Same morning, Cursor shipped its own *** forge. Nobody in hiring has noticed yet. But every reviewer who says "just send me your GitHub" is leaning on one link that was down all Monday, and may not hold the whole picture by next year.

• 
  Stefano Straus (@StefanoStraus) reported 18 minutes ago

  Yesterday's GitHub incident lasted 7h47m and it was a cascade, not one broken service A traffic peak in Central US pushed an Istio sidecar to its concurrency limit. Autoscaling watched the host service instead of the sidecar, so it did not add the capacity that was needed The failure spread until four HAProxy nodes exhausted their flow limits and the authentication path started timing out across Issues, Pull Requests, APIs, Actions and Copilot At peak, web and API errors reached 20%. Archive and raw-content downloads reached 50% Then retries became the second outage. A latent VS Code bug multiplied Copilot token requests by about 10x, from the normal 7K to 9K RPS up to 70K to 100K RPS GitHub recovered by shifting traffic, pausing the saturated HAProxy nodes, reducing gateway retries and temporarily returning 403s to break the client retry loop

• 
  Kirill (@kirillk_web3) reported 18 minutes ago

  A GITHUB REPO OF AGENT SKILLS JUST HIT 219,000 STARS. free, MIT, works with any model. Save this before you forget. built for real engineering, not vibe coding. most process tools take over and leave you fighting them when a bug shows up. these do the opposite. small, composable, easy to bend to your workflow. what the skills fix: > the agent grills you before writing a line, so it builds what you meant > a shared-language file, so it stops using 20 words where 1 works > writes a failing test first, then makes it pass > a disciplined debug loop instead of flailing at hard bugs > scans your codebase and hands you what to simplify install once, works with any model. and once your agent is dialed in, the next unlock is memory. my graph engineering breakdown shows how to give it a structure that compounds instead of relearning your project every run. full guide below.

• 
  Harshit Sharma (@itsharxit) reported 24 minutes ago

  @letstri @theo I mean, you can. I just think you’d be able to provide a lot more context in a GitHub issue.

• 
  Cynthia Ozumba (@CynthiaOzumba) reported 26 minutes ago

  If you're using Claude without this, you're probably using maybe 1% of its brain. This one thing can unlock the other 99%, and it's called Claude Skills. Claude Skills are blowing up right now, but the mistake almost everybody is making is trying to hunt down the right one for themselves. There is a site with almost 10,000 Claude skills. Skills for coding, sales, research, writing, and all of it. But instead of guessing which one to install, use the number one skill on the whole website. It's called Find Skills. It has over 1.8 million installs right now, and it does the hard part for you. You tell Claude what you're trying to do, and it finds the exact skill for that job. But here is the important part: Don't just randomly install skills from GitHub. The site has a security audit page that checks them first. It shows what's safe, what has alerts, and what's high risk before you paste anything into Claude. So the play is simple: Find the skill. Check its safety. Install it. Now Claude starts acting like it already knows what you need.

• 
  Harshit Sharma (@itsharxit) reported 26 minutes ago

  @letstri @theo Instead of complaining, you could have just opened a GitHub issue with all the required context. It’s fully open source for a reason.

• 
  WolfWammer (@wolfwammer) reported 27 minutes ago

  @daanisharif New bittensor fix: no active GitHub and miners, no incentives

• 
  Baptiste (@Bafiste_) reported 28 minutes ago

  GitHub was down for hours yesterday Claude is down today How can I build my billion-dollar company with that??? pls lemme cook

• 
  Sankar (@sankar2704) reported 28 minutes ago

  What is the reason behind major services getting outage, is it because something specific to their system that is impacting Or any pattern with the recent outages Claude Github Microsoft systems Sometimes X itself

• 
  Rolando 🦇 (@wifidinero) reported 28 minutes ago

  @acolombiadev Github Support is sooo slow too, been waiting weeks for a reply with nothing

• 
  Encrypted Clipboard Manager (@EncryptedClip) reported 28 minutes ago

  If you're a dev who's ever accidentally pasted a secret into a Slack message, a GitHub issue, or the wrong terminal... you already know why clipboard hygiene matters more than people think.

• 
  Patrik Tang (@_patriktang) reported 31 minutes ago

  GitHub was down yesterday, claude just went down. The world is probably ending soon

• 
  Michael Mayernick (@mmayernick) reported 33 minutes ago

  3/ Paperclip, the open-source project for organizing teams of agents to run a business, reached ~78K GitHub stars. Its issue queue is already asking for governance, audit, and execution policy. The org chart arrives first, and the operating rules follow.

• 
  Bash (@bashirbuilds) reported 40 minutes ago

  @lightsilver323 Building Reeno right now — service reliability for SaaS founders who depend on Stripe, GitHub, OpenAI, webhooks and other external services. Still early, but I’m focused on solving the “customer found out before I did” failure problem.

• 
  juggernaut (@curlysaarthak) reported 43 minutes ago

  @ruchagavaskar_ > theres something called etched with raised 700m from jane street > github is/was down n cursor launched its competitor > claude increased usage by 50%

• 
  Hrithwik Bharadwaj (@hrithwik_) reported 43 minutes ago

  just not able to ship one feature yesterday github was down today claude is down

• 
  Jason (@JasonGiedymin) reported 43 minutes ago

  @HotAisle I take it this is the GitHub issue? I used to run istio (for years), had to make sure not only you set up HPAs for it right (HorizontalPodAutoscaler) but that you had the resources to do so. Default values were not so good, but you'd be surprised how many times either they were not set, set to defaults from a terrible helm chart, or settings NOT saved in the configmaps so it rolls back. Also some people are lazy and with spot instances and you kinda need to know what getting to configure correctly. Oh and some upgrades were wonky. Sorry for the long reply. I actually don't like using istio, or K8s anymore LOL!!!!!!!!!!!!!! I don't want to read the post mortem because it has the words istio in it LOL.

• 
  Artur Kre (@Arturkre) reported 44 minutes ago

  @Da7_Tech @Chris_Wozniczek with 5k open issues on github, hermes is actually the tool which is broken the most. Out of the negative things you mentioned i only noticed the issue with bots not showing that they stop. Everything else works flawlessly

• 
  arzafran (@arzafran) reported 46 minutes ago

  so github was down most of yesterday, where is my reset on codex usage?

• 
  Eric Stevens (@Eric_M_Stevens) reported 47 minutes ago

  Cursor shipped a GitHub rival called Origin the same day GitHub went down for six hours. 257 outages in a year will do that. The AI editors already own your keyboard, the repo was always next. Microsoft built the moat and forgot to keep the lights on.

• 
  hish 🏴‍☠️ (@hishboy) reported 52 minutes ago

  Here's how I test @Zipbox_ using Zipbox I boot an agent and tell it: - Open a Remote Desktop session. - Go to zipbox dot ai. - Sign up using your own agent mail that we provide. - OTP into the website by checking it's email inbox. - Boot a new sandbox inside yourself. Yes. A sandbox running a sandbox. Then I hand it a markdown file with our entire test suite. It goes feature by feature, spins up whatever it needs, and tests the platform like a real user. When it's done, it writes a full QA report and files every bug as an issue in @GitHub. Meanwhile, I have another agent sitting on the repo waiting for new issues to show up so it can start fixing them. So Zipbox is testing Zipbox, filing bugs against itself, then fixing itself. We're getting dangerously close to me being unnecessary here.

• 
  Jai kora (@jai_kora) reported 59 minutes ago

  @fideloper having some Github auth issues on @ChipperCI its been while since support ticket has been raised , not sure if it has reached you.