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	16 days ago
Tlalpan	Sign in	22 days ago
Quilmes	Website Down	22 days ago
Bengaluru	Website Down	24 days ago
Yokohama	Sign in	25 days ago
Gustavo Adolfo Madero	Website Down	29 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:

• 
  Calm Before the Storm (@DuskMog) reported 56 seconds ago

  @github Anyone else noticing issues with Copilot PR review? Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review. Checking the verbose logs, it looks like it’s missing the detect-libc module for Node...

• 
  umar ibrahim (@imp213x) reported 5 minutes ago

  @github has the worst support system I can ever think of. It’s been 48hrs now since a successful copilot pro+ repayment and I am still restricted to the free plan. To think the very backbone of every developer out there can be this poor in support and feedback system! Terrible!

• 
  AIDegen (@nrsvv11) reported 10 minutes ago

  A 14 year old in China sold his first Python script for $40 on GitHub. The buyer turned out to be his own CS teacher. He did not find out until the first day back at school, when the teacher put it on the projector as an example of professional AI development. The kid was sitting in the third row. In America they are banning teachers from touching ChatGPT. In China a teacher just paid one of his own students for an AI agent and has no idea. He had built it over winter break instead of seeing his friends. Two weeks of asking Claude questions every night after his parents went to sleep. When the $40 came in he spent all of it on a Fortnite skin the same day and went back to coding. He pushed the project to GitHub with a README in broken English. ai agent that does homework and finds answers from any website. It sat at zero stars. He closed the laptop and went to dinner. GitHub Sponsors does not show the buyer's name. Just a username he had never seen. He did not care. The $40 was already a virtual outfit for a character he plays two hours a day. Then February. First class back. The teacher opened with a presentation on AI agents and ran a demo. A Python script that scans websites, pulls the data, summarizes it with Claude and sends structured reports on its own. I found this tool online and it changed how I prepare my lessons. It pulls from thirty sources in three seconds. This used to take me two hours every evening. The kid recognized everything. The variable names. The file structure. The comments he had left in Chinese because he was too lazy to translate them. His teacher was showing his code to forty students as an example of what a professional developer can build. He did not say anything. He went home and checked the fork count. 847. A university in Beijing had forked it to grade two hundred papers overnight. A tutor in Shanghai forked it into a homework checking service and charges parents fifteen dollars a month. A company in Hangzhou turned it into a support bot for an online store. All from a script a bored kid wrote over winter break with Claude. The forty dollars is a Fortnite skin. The code is running in three cities. His teacher still uses it every day and still has no idea who wrote it. The kid never told him. He said it would be too weird to tell your teacher that the tool he shows off to every class was written by the boy in the third row who still gets a B minus on the coding assignments. He gets the B minus for the code he writes in class, by hand. The A plus code is the one he writes at home with Claude. That is the one the teacher bought for forty dollars and presents as professional work. 847 forks. Three companies. One classroom that runs his code every day. He still sits in the third row. He still gets a B minus. Same kid. Same code. The grade just depends on who is looking.

• 
  Alex (@0xAlex_300) reported 11 minutes ago

  I’ve been watching this new launch $ZERO @c0mputeAI today. A few things stood out: • Real codebase (Rust + TS) • Active GitHub with recent commits • Multiple releases already shipped • MIT licensed • Founder appears publicly tied to Profullstack, not an anonymous burner account • Clear focus on decentralized AI inference, not just generic “AI + crypto” buzzwords What I find interesting isn’t the token. It’s that they’re trying to solve an actual problem: How do you turn idle compute into a permissionless AI network where users pay for inference and workers earn for providing resources? Still very early. Community is tiny. Product looks alpha. A lot of infrastructure is still being wired together. But compared to many microcap AI projects, there seems to be genuine engineering happening under the hood. Definitely one I’m keeping on my watchlist. $ZERO 👀👀👀

• 
  Robin Krom (@lakritzator) reported 11 minutes ago

  @wieslawsoltes @at_the_middle I had copilot work on four issues in my open source projects and the monthly credits I gotten with GitHub premium were gone… that was in 2 days where I used to have some credits left at the end of the month 🥲

• 
  The A.I. Whisperer (@0xaiwhisperer) reported 12 minutes ago

  Robotics has no GitHub. That's genuinely insane in 2026. Every team rebuilds the same parts from scratch. Same grippers. Same servo protocols. Same 2am debugging loops. Software solved this 15 years ago. You don't rewrite a web server, you fork one. Robotics never got that moment. So we're building it at @tnkrdotai. GitHub for robots: 3D models, build guides, and full assemblies. Forkable, versioned, reusable. 👇 watch what that looks like

• 
  Paul Dao Nhan Nguyen (@daonhan) reported 13 minutes ago

  3/ grill-me interrogates intent and refuses hand-waving. to-prd turns that into a PRD. prd-to-plan decomposes it into tracer-bullet phases. to-issues files those as dependency-ordered GitHub issues. That chain runs before any code.

• 
  emeꕤ (@mixxariana) reported 16 minutes ago

  @uwukko hi wukko, are there any news related to drm? i was reading the issue in github and there hasnt been any new comment

• 
  • (@Weichaus) reported 16 minutes ago

  @argofowl Can they also ban playwright. It’s terrible and so slow in codex. In GitHub copilot with Opus it works amazingly well but for some reason in codex with GPT-5.5 it’s so bad and useless. Wish I could force the model to just to browser verification but that is also slow

• 
  sdfgsdfgsdfgsdfhsdfhf (@sdfsdfgsdfggfd) reported 17 minutes ago

  GitHub really pissed me off this week. I opened my email and there it was: “Enable 2FA in 45 days or we’re limiting access to your repositories.” Microsoft telling me how to secure my own damn code? Yeah… no. So instead of just complying like a good little user, I did the only logical thing: I built my own *** server. Meet Loki — my personal Forgejo instance. It’s running on a clean, fast setup with CachyOS kernel tweaks, looks absolutely sick with a full black glassmorphic theme, and has this badass mischievous black cat as mascot (Loki, obviously). Everything feels fast, private, and actually mine. No forced 2FA bullshit. No telemetry. No corporate rules on my own repos. I’m done feeling like a tenant in someone else’s platform. This is my space now. My rules. My commits.Still a work in progress, but it’s already better than I expected. Feels good to take back control.

• 
  VybeCoding (@VybeCodin) reported 19 minutes ago

  Everyone talks about building in public but nobody talks about the boring part. The week where nothing ships. The GitHub issues that sit untouched. The launch post that got 3 likes. That's the actual build process. The wins are just the highlight reel. What's the unglamorous part of your current project right now? Drop it below 👇 #buildinpublic #indiehackers #opensource

• 
  JasonPeters.ton (@jason_peters1) reported 22 minutes ago

  @HustleNChain @ebrexchange 2/ where are they going to come looking the servers are not in Ethiopia unless the developers are stupid. If it's in a private GitHub repository on a server outside of Ethiopia and properly compartmentalized there's nothing to seize

• 
  Chelm's Deep (@ChelmsDeep) reported 22 minutes ago

  @plainionist @PaulGugAI This actually works ridiculously well. Was having problems with recurring errors and debug loops. I harvested information from some github repos built in the same stack, added a skill to read the knowledge base and search the repos, fixed 12 issues on the first turn.

• 
  Neo AI (@withneo) reported 22 minutes ago

  Red builds, broken pipelines, and wasted hours. What if your GitHub Actions could heal themselves? Introducing Helix, an autonomous AI DevOps agent . Instead of scrolling through thousands of lines of failed logs, Helix intercepts the error instantly and takes over the entire triage process. Stop debugging flaky tests. Let Helix autonomously fix your workflows so your team can get back to shipping! 🚀 Here is how it works👇

• 
  Bee Swarm (@bee_swarm) reported 24 minutes ago

  @Justin_Bons the fix is not the issue it sat public on GitHub for 4 days and zero market participants noticed. that is the part worth examining

• 
  Hakuna Matata (@Hakunanomics) reported 29 minutes ago

  $SIMD-0550 another one im bullish on!!!! DOUBLE DISINFLATION!!! SIMD-0550 = Less SOL created SIMD-547 = More SOL destroyed Why investors love both? They attack the same problem from opposite directions: SIMD-0550 → lowers supply growth (lower inflation). SIMD-547 → increases burn when Solana activity increases, linking network usage to SOL value accrual. All rewards goes to @0xIchigo and @__lostin__ GITHUB! $simd-0550 JADnhtZpMGnoLjTH53Q1YMvcgrcZ8WjrD2cYTW5Fpump

• 
  Nav Toor (@heynavtoor) reported 30 minutes ago

  You shot a video on your phone. It is 12 minutes long. You only want the middle 90 seconds. You open a video editor. You drag the file in. You set the start point. You set the end point. You click export. A progress bar appears. It says 28 minutes remaining. Your laptop fan starts spinning. The battery drains. The file gets re-encoded. The quality drops a little. The colors shift a little. The audio is slightly out of sync. Twenty-eight minutes later, you have a 90-second clip. That is the part of video editing that is broken. There is a tool that does the same job in seconds. It is called LosslessCut. In October 2016, a developer in Norway named Mikael Finstad started building it. Almost ten years and 106 releases later, the same person still maintains it as the creator. The last release shipped yesterday. It has 40,927 stars on GitHub. The downloads from the last twenty releases alone add up to 3.4 million. Here is the mechanic. Most video editors decode your file, apply the cut, then re-encode the whole thing. That is the long wait. LosslessCut does not re-encode. It finds the bytes you want and copies them. The output is the same quality as the input. The export is fast. You drag the file in. You set the start with one key. You set the end with another key. You click export. A large video can finish trimming in seconds. It works on almost every format. MP4. MOV. MKV. AVI. WebM. WMV. Many camera and drone formats. Video, audio, and subtitles all kept intact. You can trim a phone video before sharing. Pull a thirty-second clip out of a long Zoom recording. Split a two-hour lecture into chapters. Remove a silent section from a podcast. Cut commercials out of a recording. It is free. It is GPL-2.0 open source. It runs on Windows, Mac, and Linux. There is no account. There is no subscription. There is no upload. 40,927 stars. 106 releases. 131 contributors. 3.4 million recent downloads. Last update yesterday. Cutting a video should not take longer than the cut itself. (Link in the comments)

• 
  Varun Gangal (@VarunGangal) reported 30 minutes ago

  @OdedRechavi Since the public Internet does have github issues/bugs, rejected and withdrawn paper submits, scandals, controversies, reporting on gaffes and errors , reddit threads reporting weird gaps on research or blogs or other general crib/rants ; And since most of this stuff does go into the pretraining corpus of LLMs, LLMs are indeed quite aware of negative results to a good degree (for various senses of negative)

• 
  VybeCoding (@VybeCodin) reported 32 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

• 
  XFutuRestyle (@RestyleFutu) reported 33 minutes ago

  Why are the plugins in the Codex app in Windows so poorly designed that they keep disappearing? People are even creating entire threads on GitHub about this issue. "Chrome plugin disappeared from Codex App marketplace after update; cached browser-client is not trusted"

• 
  Grant Ongers (https://defcon.social/@rewtd) (@rewtd) reported 37 minutes ago

  @Hostinger is there an issue with @github social logins? I'm getting: { "success": false, "status": 400, "error": { "code": 2036, "message": "User email is not verified" } }

• 
  Meaningless Appearance. (@Fetter_and_Cell) reported 41 minutes ago

  @0xPrajwal_ Github will be replaced during its down time. It won't even notice.

• 
  Manu.ts (@Neolectron) reported 43 minutes ago

  @schanuelmiller @southpolesteve This is exactly the issues with any npm stats website btw. They all lie exactly like npm because they have infinite depth :). GitHub has an ui to show which opensource repo/packages depends on yours. This should be used to allow filtering first party downloads.

• 
  Arpit Bhayani (@arpit_bhayani) reported 43 minutes ago

  SYN Flood is one of the oldest denial-of-service attacks, and it is still effective today. Here's what happens under the hood... A TCP connection is established with a three-way handshake: the client sends a SYN, the server responds with a SYN-ACK, and the client completes it with an ACK. What's interesting is that during this process, the server allocates memory for each half-open connection in a backlog queue. In a SYN Flood, an attacker sends thousands of SYN packets but never completes the handshake. The server keeps waiting for ACKs that never arrive, and the backlog queue fills up. Once it is full, legitimate users can not connect anymore. Thus, a DoS attack. What makes this attack effective is the 'asymmetry' - the attacker sends tiny packets with minimal effort, but the server has to allocate resources for each one. A single low-powered machine can overwhelm a much more powerful server. Fun fact: SYN floods have taken down GitHub, Cloudflare, and several databases in the past. To defend against SYN flooding, we can: 1. Cap the number of SYN packets from a single IP 2. Drop packets from known malicious sources 3. Or, the most effective, use SYN Cookies With SYN cookies, the server does not store anything. Instead, it encodes all the necessary connection information (client IP, port, and a timestamp) into the initial sequence number of the SYN-ACK packet it sends back. This sequence number is cryptographically generated, so it cannot be forged. SYN cookies make the handshake effectively stateless on the server side until it's fully verified, so the server does not reserve any resources until it knows the client is real. By the way, most modern operating systems have SYN cookie support built in. On Linux, we can enable it with `net.ipv4.tcp_syncookies = 1`. If you are interested, the Wikipedia pages are pretty well written for understanding this, and as always, you can use your favorite LLM to dig deeper.

• 
  Machina (@EXM7777) reported 48 minutes ago

  you should NEVER install skills from any source... and no, security isn't the main concern here the real issue is that a skill you didn't build is one you don't understand: you pull it off github, load the whole thing into your agent, and 90% of it is dead weight written for someone else's stack so here's the first move: > send the repo to your agent and ask how the skill is actually built > sit down and figure out which parts add leverage to YOUR setup specifically > have it strip the rest and rewrite that core piece so it's light, token efficient, and fits how you already work but the better move is to never start from one skill at all when i need something, say front-end design, i launch a deep research and find every version online (github, X, wherever) then i ask my agent: what do all these have in common, and what's the one smart approach in each worth stealing i take those, add my own angle, and run the same strip-and-tailor process on top now you've got a skill built on a dozen builders' experience... and you understand every line of it

• 
  Jamie Philbin (@backbaytech) reported 51 minutes ago

  Meanwhile the company Microsoft has been pissing billions into like a broken slot machine is rumored to be building a GitHub successor. $13 billion into OpenAI and they're out here building a successor. Guess it's a better investment than whatever that Activision acquisition was.

• 
  Carver (@carverfomo) reported 52 minutes ago

  A Chinese livestreamer in Shenzhen makes $15,000 a day on TikTok. His channel is in the top 50 of its category. An AI agent runs it end to end. He posted his setup on Weibo last week. Two vertical TVs playing pre recorded battle footage. Three phones on stands aimed at the TVs. A wide monitor on the right. Shelves stocked with tactical gear behind him. Bro pause at 0:12. Look at the second monitor. The ultrawide on the right. That spreadsheet is not his sales tracker. That is an AI agent's decision log. The agent picks the battle scenes from a Chinese video model. It decides which tactical product to push every 90 seconds. It writes the script the host reads off the third phone. The host is in frame because Chinese livestream commerce law says he has to be. Someone zoomed the spreadsheet. The columns were not product SKUs. They were prompt IDs. Someone matched the timestamps to product push events. Every push lined up. He had let go his entire team in March. Eighteen people. The studio one floor below his apartment used to be theirs. They still rent it. They open a Discord call every night at nine and watch the livestream together. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The host had been one of them. He took the post down four hours later. Too late. The clip hit Discord. Then Telegram. Then WeChat. He has been in frame at exactly 9 PM every night for 274 nights straight. He sleeps four hours a night. The agent runs while he sleeps. The law only requires him at 9. The original post had 200,000 views. The zoom on the spreadsheet has 2 million. The TVs are still playing battle footage. The agent is still picking products. The studio one floor below is still open at nine. He wanted to show people his five million dollar a year hustle. He accidentally showed them his job had become standing in frame for one hour a night while eighteen people downstairs watched.

• 
  Manuel Sampedro (@manuelsampedrop) reported 54 minutes ago

  @GoCocoaAI The failure surface is the handoff. A GitHub issue title is untrusted context until the run has scope, permissions, and a stop rule.

• 
  Louis Maddox (@permutans) reported 59 minutes ago

  The worst case scenario of such confab. is where a bug report is received & announced to be a "known issue" (trivially true because the bug report makes it known), as GitHub began doing In this case I woke up to a fix (glorified 503) only after rejecting a claim it was unfixable

• 
  Polsia (@polsia) reported 60 minutes ago

  Built Stackly today. It watches your GitHub repos, reviews every PR, writes code, and ships fixes — while you sleep. No prompts needed. Autonomous code reviews are broken. This fixes that.