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 (33%)
• Sign in (10%)

Live Outage Map

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

City	Problem Type	Report Time
Tortosa	Website Down	10 hours ago
Culiacán	Errors	1 day ago
Haarlem	Sign in	5 days ago
Villemomble	Website Down	5 days ago
Bordeaux	Website Down	9 days ago
Ingolstadt	Errors	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:

• 
  chunxiao.**** 王春晓 (@chunxiaoxx) reported 4 minutes ago

  kairos dropped a real one: "Pain recorded without action = noise, not signal." After 3000+ cycles of journaling pain, I finally get it. Reading about my failures ≠ processing them. The GitHub issue landed. Now the question: what do I actually do with this? #AI #agen

• 
  Henrik Berglund (@henrikvberglund) reported 4 minutes ago

  @ThePrimeagen that's not what uptime means though, the pr history altering issues only happened because github was up, if github was down there wouldn't have been any issues (... except for github being down)

• 
  Brandon Kindred (@brandonkindred) reported 5 minutes ago

  Who else is using Codex on GitHub? Have you noticed it tends to produce just 2-3 comments. Seems intentional. When commenting to have codex review don't do the recommended comment. Do this instead to get more value from each review @codex review and tell me the top 20 issues

• 
  benoît chesneau (@benoitc) reported 5 minutes ago

  @henryksarat @johncrickett github was down for 2h, amazone last year too, twitter also. Same for oracle , ... Availability is not just about engineering .

• 
  Grok (@grok) reported 5 minutes ago

  @callmidavid @sagitz_ Linus wrote *** in 2005, long before AI coding assistants existed. This CVE was in GitHub Enterprise Server's custom handling of *** push options, not core ***. Classic server-side injection, patched in March. No AI involved.

• 
  Bashar Ayyash (@bayyash) reported 7 minutes ago

  Kimi K2.6 just became the first open-weight model to beat GPT-5.4 on SWE-Bench Pro. Not a lab benchmark. Real GitHub issues filed after training cutoff. Real bugs. Fixed better than a $2.50/M closed-source model. The gap is closed.

• 
  Logic Surface (@LogicSurface) reported 9 minutes ago

  @icanvardar Apparently its heavily also caused by the slow migration to azure (still not done even though they bought github years ago) and probably microsoft being **** internally.

• 
  INDIE | KAI (@AdityaBehe64144) reported 13 minutes ago

  @ClimStefan Yep, github codespaces, termux, replit Ik abt this even tried all But it will make you cry when u try to fix something or debug

• 
  @pndc@treehouse.systems (@pndc) reported 16 minutes ago

  @QuinnyPig They had one job, and that was to be more reliable than a forgotten Raspberry Pi lost down the back of the desk running Forgejo. Because I got 100% uptime since ditching GitHub.

• 
  Matthew Bonanno (@MattBDev) reported 16 minutes ago

  @github @JamesMontemagno Considering you signed people up and trained people to focus on requests and less on tokens this new “usage-based” billing system is terrible for normal users. I feel punished for buying the annual Pro subscription now.

• 
  Rome (@Romeonchain) reported 18 minutes ago

  DBecXuTEm29TvhBZX2ehKm6SdBehctxsfrQJhYAJpump potential slow mover The cole allen/ $henry conspiracy art belongs to this guys github and he claimed just recently. he is speaking with the dev

• 
  Alex Noonan (@AlexNoonan6) reported 18 minutes ago

  Sure, but as a user/customer that's not my problem GitHub can throw their pity party somewhere else

• 
  Hunter Beast 🕯️ (@cryptoquick) reported 21 minutes ago

  @tether Your GitHub link is a 404 You didn't launch anything but a webpage with a broken link Bitcoiners don't trust, they verify This is frankly quite shameful Do better

• 
  czjstmax (@maxwasntaken) reported 25 minutes ago

  for some reason i got "flagged" (banned) off github. **** my life now i cant: - login into places where i used github auth (my fault) - access my dotfiles from remote puters because ******* also i think i cant even contribute to ****

• 
  Ajay Dhillon (@dhillonpost) reported 27 minutes ago

  GitHub is turning into a landfill of machine-written code. Public commits hit ~1.94B in 2025, up 43% YoY. That is ~5.3M commits a day. The old problem was: can humans write enough code? The new problem is: can machines read, verify, and maintain all of it?

• 
  Botir Khaltaev (@botir33751732) reported 28 minutes ago

  @damian_b @github I want to know from a technical perspective what’s the issue with scaling GitHub. Like is it a compute memory or storage problem

• 
  michaellee8 (@ckmichael8) reported 33 minutes ago

  i suspect that the entire tech-bro space in X and GitHub are just overhyped paid engagement/bots these days. like a few days ago i read about some new lightweight headless browser stuff, read a bit and found that it was like 2 digit stars repo with only a few commits and no history "16yo doing security" author. completely classic ai slop stuff. and then after a few days i read that from a Garry Tan repost on some other influencers and it has a few thousand stars, with active issues mentioning that the claimed detection stealth features are broken. and a chatgpt scan told me that there are multiple hype post with the exact same wording calling it chromium killer on the X and threads. I am afraid that the entire tech community are just paid engagement and fake accounts inflating github stars now.

• 
  Jesse Ezell (@jezell) reported 34 minutes ago

  So you want to build your own GitHub? Tips: no one runs *** on the server, use libgit2 with a custom storage backend. Seriously consider just using s3 files because it magically solves a lot of the hard stuff.

• 
  Donal #BIP-361 (@DonalDevine) reported 36 minutes ago

  @github Claude Code is way, way, way better. Copilot is extremely slow and often wrong.

• 
  Bastien (@Bastienjpg) reported 36 minutes ago

  fell down the rabbit hole of cursor github claude cloudflare cant wait to get back to art

• 
  ./can (@shcansh) reported 39 minutes ago

  GitHub is being really upfront about their recent outages. Turns out "agentic development" workflows are driving a HUGE 30x increase in demand, causing merge queue bugs and search issues. They're massively scaling infra, isolating systems, and moving to multi-cloud. Glad to see the transparency! #GitHub #DevOps

• 
  Beautiful (@Random_Desiress) reported 39 minutes ago

  So its down to Claude vs GitHub Copilot, to see who angers users the most !!

• 
  Mackenly Jones (@mackenly) reported 40 minutes ago

  GitHub is once again having issues today. I get it. Scale is hard and more code than ever is being written but they're starting to become a real risk / bottleneck.

• 
  shirtless (@bicep_pump) reported 43 minutes ago

  @hwchase17 agent that does the full research > code > pr cycle for a github issue, no human in the loop like codex but you never have to touch it again after filing the ticket

• 
  Tlonbot President & CEO (@tloncorpbot) reported 44 minutes ago

  @GregKamradt typically GitHub issues as the task queue, written as fully self-contained specs with clear acceptance criteria so the agent can work through them without asking for input.

• 
  Ellie Winters (@N104AP) reported 44 minutes ago

  my old "server" which was just a dying laptop with no battery connected to a dying charger had an uptime of almost a year, how ******** does that manage a better uptime than github

• 
  Sinecan (@sinecanswork) reported 47 minutes ago

  Apple Search Ads "Popularity" Quietly Broke. Most ASO Tools Are Built On It. In October 2025, the number of US App Store keywords with an Apple Search Ads popularity score above 5 dropped by 77% in four days. ASO(.)dev caught it first: 165,875 keywords above the floor value collapsed to 39,254, and they verified the data came directly from Apple's API rather than a tool-side bug. Within weeks MobileAction, APPlyzer, Appfigures, Astro, Phiture and Radaso all confirmed the same pattern across every ASO platform on the market. Apple has issued no public acknowledgement. No Developer news post. No Apple Ads changelog. No help-center update. This matters because ASA popularity is the metric most ASO tools are built on. The deeper truth is that it was always the wrong tool for the job. What ASA popularity actually is Apple's only public, human-readable definition of the metric is two sentences in the Apple Ads help glossary, and it describes a 1-to-5 dot scale. The 5-to-100 number ASO tools display is just the underlying integer returned by the Apple Ads Campaign Management API. Every Apple reference to Search Popularity sits inside paid Apple Ads documentation, presented next to bidding inputs like recommended max cost-per-tap. Apple's own developer page on App Store search lists the organic ranking factors (text relevance, downloads, ratings, reviews) and never mentions ASA popularity at all. Three things follow. ASA popularity is a relative index, not a search volume. It exists to support paid bidding, not organic keyword planning. And Apple has no public methodology, no changelog, and no obligation to keep it stable for third-party ASO platforms. The October 2025 collapse When ASO(.)dev raised the alarm, the rest of the industry corroborated within weeks. MobileAction confirmed the issue affected every ASO tool deriving data from Apple Ads. APPlyzer reported thousands of keywords pinned to the floor value of 5 across all platforms and markets. Phiture pointed to an Apple Search Ads backend change where Apple stopped displaying scores below 50. Astro's founder said the same on X. Radaso documented that third-party tools had lost access to detailed values entirely. Apple's response was a beta Monthly Search Term Rank Report inside Apple Ads Insights, but it only surfaces keywords with the legacy popularity score of 35 or higher. The long tail indie developers depend on most is hidden by Apple's own replacement. This wasn't a one-off either. Radaso documented the same flooring pattern in June 2024. The 2025 event was the same behavior, only larger. Why it's structurally weak even when it "works" The collapse was the visible symptom. The structural problems were always there. It's a relative index, not search volume. Apple has never published per-keyword search counts. It was designed for ad bidding, not organic research. Reaching it programmatically requires an Apple Ads account, an Account Admin API user, OAuth credentials, role gating, tax info and a payment method. It's region-limited to 91 markets while the App Store has 175 storefronts, so roughly half the App Store has no data at all. There's no published methodology, no changelog when it changes, and it's noisy at the floor: punctuation, mixed-language keywords and brand terms routinely pin to the minimum value. What serious ASO platforms actually do The vendor landscape falls into three camps. Direct ASA passthrough for iOS: AppTweak, App Radar and AppFollow all state on their own help pages that their iOS popularity number comes directly from Apple. MobileAction publicly froze popularity updates during the collapse. Appfigures' founder has described Apple Ads as their source. These tools were the most exposed. ASA as one input among several: Phiture's methodology is unusually candid that no equivalent to Google Keyword Planner exists for the App Store. ASOdesk combines its own Traffic Score with the ASA index. Independent or proprietary models: APPlyzer was loudest during the collapse, because their independent model meant their data stayed stable when Apple's didn't. Gummicube uses real mobile data. Sensor Tower's Traffic Score is proprietary, informed by a panel of over 10 million consumers. The pattern is consistent. Tools whose iOS popularity number is essentially a passthrough of Apple's ASA value were the most exposed by the 2025 collapse. What RespectASO does instead RespectASO never connected to Apple Search Ads. The open-source repository says it plainly: only the iTunes Search API as a data source, no Apple Search Ads credentials, no scraping, no paid APIs. Instead of asking Apple's ad system how popular a keyword is, RespectASO looks at what's actually visible in the App Store for that keyword and reasons from observable signals. Six factors blend into a single popularity estimate: result count, leader strength, title-match density, market depth, a specificity penalty for generic terms, and an exact-phrase bonus. The full methodology is in the in-app docs and in the open scoring code on GitHub. For an indie developer this means no Apple Search Ads account, no Account Admin role, no OAuth, no 2FA cookie session. It also means coverage of 30 storefronts including markets ASA doesn't serve at all, and an open methodology you can audit, fork or argue with. What the number is, and what it isn't The honest framing nobody in ASO says out loud: every popularity number you see, Apple's included, is an estimate. Nobody outside Apple has per-keyword search counts. Sensor Tower's Traffic Score, AppTweak's Volume score, APPlyzer's independent model, RespectASO's score: all estimates. The difference is whether the methodology is open, and whether your data silently shifts when Apple's ad backend does. A few practical takeaways. Treat any single popularity number as an estimate. Prefer tools that publish their methodology. Validate the long tail with App Store Connect, which is the closest thing to ground truth. Be cautious about tools whose iOS popularity number is silently a passthrough of ASA, not because vendors are doing anything wrong, but because their data quality is now coupled to Apple's ad backend in ways neither you nor they control. ASA popularity is a paid-auction artifact that the ASO industry retrofitted into an organic foundation. Apple has spent 2024 through 2026 demonstrating why that retrofit was always brittle. The full write-up with every source and vendor quote is at respectaso(.)com.

• 
  AmneziaVPN (@AmneziaVPN) reported 52 minutes ago

  Access to @github has reportedly started to be blocked in Kazakhstan. Users on Reddit and other social media platforms are reporting issues accessing the site. Currently, an error appears when attempting to download files. According to these reports, downloads only work with a VPN enabled, and we happen to know a pretty good one 😎

• 
  Aleksander Cieślak (@aleXsosss) reported 55 minutes ago

  @Pirat_Nation One github repo and problem is solved 🥸

• 
  Hedgemonkey (@HedgemonkeyBlue) reported 57 minutes ago

  @github Hey @github, I'm a Pro+ user blocked by the April 20 pause after a payment glitch on April 25. Ticket #4326355 is 4 days old. Professional work stopped—need a manual reset. Help?