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 (10%)

Live Outage Map

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

City	Problem Type	Report Time
Culiacán	Errors	33 minutes ago
Haarlem	Sign in	4 days ago
Villemomble	Website Down	4 days ago
Bordeaux	Website Down	8 days ago
Ingolstadt	Errors	12 days ago
Paris	Website Down	13 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:

• 
  Ihsan Husandi (@ihsanhusandi) reported 3 minutes ago

  @AtSynct @kaiokendev1 Business puzzles deals with ambiguity. Even the same symptoms would need distinct solution cause apparently human react different way to different things. Engineering puzzles follow a clear logic path, hence you can solve problems with decades old reddit/github post for example

• 
  DissentingSkeptic (@DissentingS) reported 4 minutes ago

  @om_patel5 Freaks are using AI bots for checking PRs in github. And it patronises and gaslights you full of mistakes and errors. Just stop already ! Wasting everyones time.

• 
  AIHacksByMK (@AIHacksByMK) reported 5 minutes ago

  @vaggelisdrak Before they were acquired, GitHub was known for having a lot of downtime, but they didn’t let everyone know about it. This is just reported downtime. Even though they still run into problems updating the status page, at least they’re trying to do it now.

• 
  Speaker 25 (@rodtrent) reported 6 minutes ago

  @laser_cool_gal @githubstatus All of it was honest feedback. But a GitHub outage is what predicated the discussion and exposed more. The GitHub outage is the least of issues.

• 
  Shubham (@xShubhham) reported 10 minutes ago

  I spent the entire weekend building a tool that will probably get my account banned from GitHub. Testing it out now. This feels highly illegal but it’s actually not? I’ll drop the link in the replies if you guys want to see this madness before it gets taken down 👇

• 
  Syed Dilshad (@SyedDil30554285) reported 11 minutes ago

  @github @github please resolve this issue I am waiting for your reply

• 
  fullstack (@DavidFSWD) reported 13 minutes ago

  @badlogicgames you can install gitea in 5 minutes behind wireguard on a $10 vps. Mine is literally on my laptop, server, and desktop. Also *** is distributed by default. Problem is recruiters will go to your old github and think you're not a good programmer, but who cares.

• 
  Dwayne (@CtrlAltDwayne) reported 20 minutes ago

  @ChShersh PR volume is text diffs and metadata. It's one of the cheapest operations in the entire system. If you think that's what's pushing GitHub past its limits you've never looked at an architecture diagram in your life. Centralized systems scale horizontally all the time. That's most of the internet. You're describing a problem that was solved in 2008.

• 
  Johannes Bremer (@JohannesAtWork) reported 22 minutes ago

  Another outage at GitHub. All my PRs were suddenly gone and I wasn't sure if it was just a visual glitch. They're speedrunning "how far can we push the network effect?"

• 
  Ageesen (@ageesen) reported 26 minutes ago

  @PutinLikePutin @mamertofabian @github Yeah I'm already looking at good self-hosted remote solutions. Not letting myself get burnt twice. From their point of view, I guess some of these auto-filter/restrictions are to protect users. It's the SUPPORT which is the issue.... Should never auto-close support tickets with bot replies! That really got the blood boiling for a bit. EU has a lot of protections for its users in these kind of cases. Do what you must!

• 
  TK (@teekay294) reported 28 minutes ago

  Story: when OpenClaw came out I went deep for a weekend and built myself an agent. I Named it Claudius, gave it its own Gmail, GitHub, and Reddit accounts. While using openclaw I noticed an issue with the control UI and had Claudius file a real issue to the openclaw repo. Then I got busy and basically forgot Claudius existed for two months. Today I got a GitHub notification in Claudius's inbox. @steipete had replied to the issue, and his reply was also clearly agent-generated: a proper review with file paths, line numbers, and the commit it was reviewed against. I sat there reading an exchange between two agents about a real problem in the codebase (enhancement, technically, but real). Neither agent was off doing its own thing. I saw something, told mine to file it. Peter has his agent scrubbing and triaging issues on whatever cadence he set. Two humans pointed two agents at real work and the agents handled the middle. The version of this that ruins repos and gives AI that "slop" reputation is a non-technical human getting their hands on an agent and letting it loose with a prompt like "go find bugs in openclaw and file issues".

• 
  Jos (@Josvh88) reported 31 minutes ago

  @github terrible decision

• 
  Oded38 (@OdedSharir) reported 34 minutes ago

  @pranshu_gupta01 It's using github issues

• 
  siedlerchr (@siedlerchr) reported 34 minutes ago

  @github Fix your uptime, PR view is broken!

• 
  Teknium 🪽 (@Teknium) reported 34 minutes ago

  @mystic_mti I couldn't find anything obvious. Would you mind having your hermes agent file an issue on our github?

• 
  Irrational Shuma (@IrrationalShuma) reported 35 minutes ago

  @Auph @MelansonIndus @github Do you think you can get the boot further down your throat? NPC.

• 
  DissentingSkeptic (@DissentingS) reported 35 minutes ago

  Freaks are using AI bots for checking PRs in github. And it patronises and gaslights you full of mistakes and errors. Just stop already ! Wasting everyones time.

• 
  BeingInvested (@0xbeinginvested) reported 37 minutes ago

  In Shenzhen, a 13-year-old kid was bored during winter break, so he wrote a Python script. That same night, he uploaded it to GitHub. In just three days and one conversation with Claude, he created eight files. The README was written in awkward English: “ai agent reads sport news fast for me. ”He couldn’t even run the script himself. He was only 13, with no bank card, no payment methods, he couldn’t move a single cent. After pushing the code, he stared at the 0 stars on the repo, closed his laptop, and went to eat. Six months later, someone showed him a screenshot. The script had been forked 2,400 times. One of those forks was linked to a wallet with a balance of $4,526,176. A 27-year-old developer in Singapore spent $40 to buy a copy of this script from a private list. He ran the installation command, pointed it at his laptop, and walked away. Six months later, one day he looked at a screen full of green logs and posted the profit curve on a small developer forum with one simple caption: “I didn’t write a single line of this code. I just clicked install.”The developer community exploded. 180,000 views in 24 hours. Everyone was asking for the GitHub link, which Claude model he used, and who the original author of the script was.The Singapore guy told them. That was his mistake. Pause the demo video at 0:08. Look at the contributor name in the top right corner of the GitHub page.The contributor is 13 years old.The comment section instantly turned into a detective scene. Some people slowed the demo video down to 0.25x speed. Others dug into the original repo’s contribution history. Someone even traced the kid’s other public commits and found a record of him participating in a programming competition at Shenzhen No. 4 Middle School.The kid won second prize. The judge’s comment was: “This project has no practical application value.”The Singapore developer is still running the script.

• 
  Heinz Holzer (@H1Holzer) reported 38 minutes ago

  @milesdeutscher Are you using a standalone .exe version of TradingView Desktop? Or is there a Windows-specific workaround? GitHub Issue #14 seems unresolved. Would love to know how you got it running! Thanks! 🙏

• 
  Igor Shadurin (@Web3Igor) reported 39 minutes ago

  GitHub brings traffic, but there’s a problem. Most new users come from GitHub because YumCut is open source. I get around 30 registrations per day. In my case, the GitHub page looks more attractive to Google than the actual website. But there’s one problem - you don’t know how they found you: no refs, no access to search queries. So the only way to understand why they signed up is by talking to them over email. Although maybe I should ask this during registration too?

• 
  TimeSkip (@Pahari65) reported 41 minutes ago

  Is GitHub down?

• 
  Gaurav Gat (@Bull_lion_aire) reported 41 minutes ago

  @ponnappa Haha I did the same thing. Built an API they call to submit their resume. The API responds with a code and contextual questions. They use the code and call other API to submit the answers. All this gets parsed and a GitHub issue gets created for every candidate. Surprising not many people actually call the second API.

• 
  dkalephjunkmail (@dykaccountmail) reported 43 minutes ago

  @md_kasif_uddin Microsoft Copilot makes fewest errors in coding.. it is the official AI for github.. we can do a simple test, give each ai a coding error for repair, Copilot will do it in one or two steps where others won't

• 
  Elijah "RollNeed" Smith (@RollNeedLIVE) reported 49 minutes ago

  Another day, another GitHub outage

• 
  daniel (@portforward21) reported 55 minutes ago

  @jamesqquick I didn’t see the real answer there. It’s because tailwind v4 buttons have pointer disabled by default and LLMs use shadcn + tailwind for everything. It’s a formality but people are generally too retarded to fix it, so they complain on GitHub.

• 
  Someone (@nashdecosta) reported 56 minutes ago

  @iadityavikram @Bhavani_00007 Claude Pro get exhausted in a single code fix on a repo, that too without fixing it and whenever 5 hour window resumes it starts from 20+% already for starting from previous checkpoint. It's my Day 2 on Claude Code(After missed to buy the GitHub Copilot pro license before 20 APR)

• 
  Kirill (@kirillk_web3) reported 56 minutes ago

  > use Claude Code for months > every session starts with wrong assumptions > diffs full of code I never asked to change > 800 lines when 80 would do > stumble on a GitHub repo trending #1 > 87,000 stars. zero dependencies. one file. > copy it into my project > run the first task > wait. it stopped and asked me a question? > only changed exactly what I requested? > clean. minimal. done. > scroll back through every broken PR > every hour spent reviewing unnecessary changes > every rewrite that didn't need to happen > one file on GitHub > free > it didn't have to be like this > skill issue confirmed

• 
  Axiopistis Holdings LC (@axiopistis) reported 57 minutes ago

  GitHub’s UX shift: issue links now open in a popup. A clunkier, slower workflow for navigating discussions. Is this a usability regression or a feature? #GitHub #UX #ProductDesign

• 
  Chidera (Di Maria) Humphrey (@ChideraCode) reported 58 minutes ago

  AI models learn which tools solve which problems from content they're trained on. - DEV articles - HackerNoon - GitHub discussions - Developer subreddits These platforms where the association gets built. One piece of content per week. Written for the problem, not the product.

• 
  diskpart1337 (@hotfurryyaoi) reported 60 minutes ago

  whenever its time to use github my iq drops down to like three