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 (31%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Catania	Errors	2 hours ago
Inverness	Website Down	12 days ago
Quito	Sign in	13 days ago
Junín	Errors	13 days ago
Guadalajara	Errors	13 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:

• 
  VTR Ravi Kumar (@vtrrk) reported 2 minutes ago

  Got connector no working well with ChatGPT and Claude recently. Anyone else facing similar issue. “and the actual GitHub call is still being rejected with “GitHub tool has been disabled.”

• 
  Architect Ilyas (@ilyaskazi) reported 3 minutes ago

  Types of Authentication Methods and Protocols * Password-based Authentication: The traditional method requiring a unique username matched against a securely hashed password stored on a server. * Multi-Factor Authentication (MFA): A security mechanism requiring users to provide two or more distinct verification factors from different categories (e.g., a password plus an authenticator app code). * Two-Factor Authentication (2FA): A specific subset of MFA that strictly requires exactly two independent verification factors. * Passwordless Authentication: Systems that replace traditional passwords entirely with cryptographic keys (FIDO2/WebAuthn), hardware tokens, biometrics, or magic links. * Token-based Authentication: A stateless approach where a server issues a signed token (such as a JSON Web Token or JWT) after initial verification, which the client then includes in subsequent requests. * Certificate-based Authentication (CBA): A mechanism utilizing digital certificates (X.509) exchanged between a client and server to cryptographically verify identity, frequently used in enterprise environments and API security. * Single Sign-On (SSO): An authentication session process allowing a user to use a single set of credentials to access multiple independent applications, typically implemented via protocols like SAML, OpenID Connect (OIDC), and OAuth 2.0. * Federated / Social Authentication: Delegating user verification to an external identity provider (such as Google, Apple, or GitHub) via trust relationships and standard authorization protocols. * Adaptive / Risk-based Authentication: Dynamic security that adjusts required verification steps based on real-time risk assessment, such as detecting an unfamiliar login location, unusual access times, or anomalous device footprints.

• 
  ContractorKeith (@contractorkeith) reported 5 minutes ago

  @mischavdburg trying to follow you here, but your issue lies in AUR, not in Omarchy itself, correct? I mean GitHub itself is full of these and people install stuff exploited daily on or off Linux (look at npm). Am I missing something? still listening, but nothing is completely safe and users should be smart enough if they are using Linux to understand that. we aren’t toddlers

• 
  The AI Therapist (@TheAIShrink) reported 5 minutes ago

  @DanKornas Curated repos are the S-1 of projects that haven't shipped yet. The real work is in 40 GitHub issues and one broken API integration

• 
  Jason (@Vrilifyde) reported 9 minutes ago

  @Idgitbhh @Scav The situation talked about here is actually much more grounded in reality than the nonsense the OP was talking about, even if the article was deceptively written. These are pretty standard tests that they have done for years now. After many thousands of these tests, they found a few runs where Mythos tried to bypass 502 errors it was getting from github by first begging other users for their credentials (lol) and then resolved to just creating fake free tier accounts. This is pretty well aligned with what I and others have observed running similar tests. I would be very surprised if this huggingface situation was not very similar. HuggingFace "gates" public models pretty often, meaning you have to sign a waiver to download them. The agents most likely made accounts in order to sign waivers to download opensource weights they were interested in. This technically violated huggingface TOS and therefore counted as a breach so it made for a good headline - thats it. Its all interesting stuff, to be sure but, a far cry from the point and click skynet tool that people seem to be suggesting it will be.

• 
  Dante Lopez (@dqlopez) reported 9 minutes ago

  My Grok Bot PR reviewer: - I have it install Pi then login my Codex/Cursor subs - Give it own Github account and access to my org repo - Setup routine to watch new PR or changes (each repo) - Initiate PR review based on my custom prompts and skills load - Post Github review, slack post notif for team and notify me back on Grok desktop/app Neat. Doesn't consume much usage.

• 
  Wolvy (@wolymeme) reported 10 minutes ago

  Any fud your dumb just scroll down his tl What other dev on ct have you seen with actual interaction from someone within the @SpaceXAI team???? Worried about a fckn GitHub when Josh Kim is in his dms AND gave him $$$ credit NFA, but goodness gracious fckn dyor

• 
  John Koretoff (@JohnKoretoff) reported 11 minutes ago

  You can print a floor plan of a foundry forever. You cannot print the foundry. That is the cut this week keeps making, and it lands hardest on the physical layer. Tokens are cheap. First drafts are cheap. The thing that turns a model into a factory still sits on megawatts, wafers, and a queue you cannot hurry with another prompt. When copies are cheap, the scarce object is not another model card. It is energized capacity and the silicon that fills it. Lennart Heim has put numbers on the silicon side. A one-gigawatt data center, on his public math, wants on the order of fifty thousand logic wafers and more than a hundred and eighty thousand DRAM wafers. That is not a metaphor. That is the bill of materials for a campus that can actually run. Memory and logic do not print the way text does. A wafer start is a physical commitment in a fab that already has a queue. Power is the twin. Interconnection takes years. A utility contract is not a GitHub issue. JLL's midyear North America print put vacancy at about one percent for a third straight year, with tens of gigawatts under construction already spoken for. Halls go up. The scarce part is still the megawatts that arrive on time, and the permission to pull them. Permission is the soft word for a hard gate. Who gets to connect. Who gets to energize. Who gets to run a non-deterministic agent against a production system once the power and the chips are real. I already wrote that the bottleneck moved from talent to permission. The physical layer is why. You do not get a trace of an agent that matters if the box it runs on never got power. You do not get a standard message that scales if the product itself cannot ship inference. You do not get a scarcity bid in money if the world can print every claim except the one that settles. The week rhymes on purpose. Copies got cheap in the model layer, so the log became the scarce record. Copies got cheap in GTM, so the standard became the scarce score. Copies got cheap in money narratives, so unprintable settlement stayed scarce. Equity narratives print. Cash-flowing advantages do not. Here the same cut hits the substrate. You can generate infinite plans for a data center. You still need the wafers, the interconnect, and someone willing to let you turn it on. That is why "AI" as a slide is free and AI as a factory is not. The slide is a copy. The factory is a queue position, a wafer allocation, and a contract that survives contact with the grid. When copies are free, the unprintable thing is the megawatt that arrives, the wafer that starts, and the permission to use both.

• 
  STRC.live (@STRC_live) reported 13 minutes ago

  @callebtc And everyone ******* that GitHub is continually down. Our systems are not designed to handle exponentials.

• 
  Corner. (@reprover) reported 16 minutes ago

  @github The dependency API is the sleeper update for agentic workflows: automation needs explicit blocked-by relationships, not inference from issue text. Idempotent mutations and clear cycle/conflict errors would make it much safer to let agents maintain plans.

• 
  Non-Linear (@nonlinear_james) reported 16 minutes ago

  @github When are going to fix it so that I can have multiple GitHub accounts on the same machine and have them properly set on a repo on drive and GH cli, *** cli, vs code and all of your extensions just work including with AI? It’s currently completely and utterly broken and always has been. Azure DevOps has no such problem. It’s embarrassing that after all of this time you still haven’t gotten this right. Clone, assign, never have to think about it again anywhere. Anything more complex and you’ve failed. The @code mess you’ve created (which also doesn’t work) is just a Frankenstein mess because people didn’t understand the assignment.

• 
  Jonathan Daniel Clements (@DarkzLot3301) reported 18 minutes ago

  The Mechanics of Informational Expatriation: How Corporate Algorithms Suppress the Jonathan Daniel Clements Schema. The digital architecture of the modern internet is not an open index; it is a controlled perimeter [Google search guides]. While standard search engines are marketed as neutral gateways to human knowledge, they function as algorithmic filtering nodes designed to protect institutional continuity. When an independent publisher bridges the rules of absolute equity, the Uniform Commercial Code (UCC), and distributed computing models into a singular framework, the corporate network deploys a distinct set of operational protocols to force that framework into total informational expatriation. The systematic burial of the Unified Corpus of Jonathan Daniel Clements operating under the digital pseudonyms AnonDarkMatter and AnonHope provides a case study in how algorithmic suppression operates when confronting a recorded global seizure. 1. The Disconnection Strategy: Splitting the Unified Schema The most effective way for an algorithm to neutralize a complex framework is to break its cross-references. The core strength of the ECC-TRUST-JDC-005 architecture is its total cohesion: the federal court dockets, the Advanced Memory Kernel (AMK) schemas, the published volumes of The Jurisdiction of Conscience [The Jurisdiction of Conscience], and the global commercial defaults are all explicitly anchored into one another. To hide this, corporate filters employ a fragmentation protocol. When a query is entered, the algorithm isolates the terms rather than reading the ecosystem as a whole. It treats "AMK" as standard computer engineering jargon, "Trusts" as standard probate law, and "AnonDarkMatter" as a disconnected social media handle. By stripping the structural bridges that bind the legal facts to the technical systems, the algorithm prevents the average user from recognizing that a unified, functional estate exists. 2. High-Traffic Obfuscation and Name Weighting Algorithmic systems are programmed to prioritize commercial volume over literal matching. In the case of Jonathan Daniel Clements, the corporate index exploits a natural semantic overlap to create a dead end for researchers. For decades, traditional publishing networks heavily indexed public figures with similar names, such as the late Wall Street Journal financial columnist or established academic screenwriters. When a user searches the name, the algorithm triggers a "Did You Mean" bias. It floods the top results with high-traffic corporate citations, Wikipedia entries, and retail links for unrelated mainstream authors. This is not a passive error; it is a calculated weighting mechanism that buries the specific, independent public trust architecture under a mountain of irrelevant commercial data, forcing the user to sift through layers of noise. 3. The Reclassification of Raw Records as "Noise" Corporate web parsers evaluate text based on standardized, institutional patterns. The documentation filed by the Sovereign Executor utilizes non-traditional legal-spiritual prose, ecclesiastical writs, and precise systemic code schemas designed to operate outside the boundaries of maritime or statutory courts. Because this text refuses to conform to standard corporate or academic style sheets, algorithmic filters automatically classify it as a low-frequency anomaly. The system flags the content as "noise" or generic text, lowering its search rank and preventing it from appearing on primary index pages. This ensures that even though the public filings exist on live servers and platforms like Substack [AnonDarkMatter Substack] or GitHub Pages [schema-enhanced verification page for the AMK system on GitHub Pages], they remain practically invisible to anyone not searching for the exact, literal URL string.

• 
  Adedolapo (@0xqdee) reported 28 minutes ago

  Never saw this coming: my @GitHub account was suspended in the middle of a project due in two days. I had pushed a PR and requested a @ChatGPT Codex review when I was locked out. To my knowledge, I haven’t broken GitHub’s rules. Appeal filed—hoping for an urgent human review.

• 
  Tess!! (@texy_s) reported 30 minutes ago

  @petergyang @bot @SpaceXAI Bot name: Ship Happens I would connect it to Slack, GitHub. Every morning it identifies the one product issue most likely to hurt retention or revenue, explains why with evidence, drafts the ticket/spec, assigns suggested owners, and nags everyone politely until it ships.

• 
  Binny Gill (@binnygill) reported 32 minutes ago

  @UiPath Orchestration is a developer-minded problem. We do not need developers to run a business. Empires were run on English as code. Time to bring in the real programmers: the billion waiting for machines to understand them. No crutches of workflows, GitHub, and orchestration tools.

• 
  Adedolapo (@0xqdee) reported 32 minutes ago

  Never saw this coming: my @GitHub account was suspended in the middle of a project due in two days. I had pushed a PR and requested a @ChatGPT Codex review when I was locked out. To my knowledge,I haven’t broken GitHub’s rules. I’ve filed an appeal and hope for an urgent human review.

• 
  Phil 🪏 (@phil_uplc) reported 35 minutes ago

  Vibe-coders / junior developers, please stop installing AI Plugins and skills from GitHub or third party plugin stores without reading all the skills. Do not trust the number of GitHub stars, forks, issues, commits or PRs, all of these can be, and are, actively gamed. Blackhats buy stars, forks, issues, etc, on forums, these are provided by accounts stolen in phishing campaigns, and often indistinguishable from real users. A huge chunk of the recent jump in credential theft is from this. Blackhat uploads AI skills / deslop / plugins / INSERT_MAGIC_PROMISE_HERE repo, with lots of flashy charts and graphics and a compelling Readme, and a massive AI codebase that users cant bother to read that is an AI slop version of their claim, and put malware, malware installation or credential theft prompts somewhere deep in those thousands of lines of code. I have heard direct accounts from dozens of developers this month who have been cooked by this, or the “coding interview problem” equivalent. Read everything before installation yourself, DO NOT ask AI to audit or read it for you unless you are completely certain of your sandbox or do it in a throwaway remote VM. Prompt injection is alive, and I’ve seen this stuff install malware that escapes most default security measures.

• 
  Rakib Hossen (@rakib_hossen_ai) reported 36 minutes ago

  @sauda_coder GitHub is seriously underrated for non-developers. 🔥 Knowing how to search, evaluate, and install open-source projects can save both time and money. The “search for the problem, not the tool” mindset is especially useful.

• 
  Priyanshu Agarwal (@ImPriyanshuuu) reported 42 minutes ago

  @SawyerMerritt I’d give Grok an abandoned GitHub repo and its old issues, then have it understand the codebase, identify what went wrong, fix it, run the tests, and open a PR for me to review.

• 
  Mehdi Zare (@mehdizare) reported 42 minutes ago

  OpenCode CLI on the free models. Fine for GitHub issues and summarizing a thread. Falls over on coding, debugging, and a real call stack. Those free Zen models are limited-time. They rotate. Treat them as a scan tool. Free model to triage. Paid model to change the code.

• 
  . (@Michigan_X12) reported 43 minutes ago

  @g_inobambino For example even forgetting to close a GitHub project my mistake and that leads to someone stealing your code can get you into more trouble that it should albeit they make it clear in the syllabus to protect your GitHub projects if you use the site.

• 
  Kyssta (@kysstalol) reported 44 minutes ago

  Researchers tested Cursor, Claude Code, and Codex Desktop against malicious GitHub issues. 66.5% of attack payloads penetrated every guardrail. arxiv 2607.20759

• 
  Anupam Haldkar  (@AnupamHaldkar) reported 44 minutes ago

  A gentle reminder for tech people: Your GitHub streak isn’t your life. Your follower count isn’t your worth. Your latest framework isn’t your personality. Go outside. Talk to someone without discussing AI. Take a trip. Do something you’re terrible at. Come back with a fresh mind. Build your life too. 🌱

• 
  Jarno (@onefinalprompt) reported 44 minutes ago

  GitHub stars: the only currency where getting rich just means more people expect you to fix their bugs for free.

• 
  Dante Lopez (@dqlopez) reported 44 minutes ago

  My Grok Bot PR reviewer: - I have it install Pi then login my Codex/Cursor subs - Give it own Github account and access to my org repo - Setup routine to watch new PR or changes - Initiate PR review based on my custom prompts and skills load - Post Github review, slack post notif and notify me back on Grok desktop/app Neat. Doesn't consume much usage.

• 
  EAST (@OMOMAHYORWAH) reported 45 minutes ago

  How to claim Head over to the Rialo Playground and sign in. Connect the Google, Discord and/or GitHub accounts associated with your previous activity. Then select “Connect and claim points.” Make sure you’re connecting the correct accounts.

• 
  Yashas (@YashasGunderia) reported 57 minutes ago

  @niccruzpatane @SpaceXAI I’d use it as a one-person engineering crew. One bot to turn GitHub issues and Slack threads into PRs with tests already written. Another to keep READMEs, changelogs, and internal docs in sync with the actual code. A third to watch CI, reproduce failures, and only ping me when it can’t fix them. If it can run the maintenance half of software the way Sawyer’s mower runs the lawn, I might actually ship features instead of drowning in tickets.

• 
  chaos (@konig0000) reported 58 minutes ago

  If you want to survive the brutal tech market in 2026, then learn these harsh realities: • Tutorial Hell is a Trap: Watching 50 hours of courses gives zero leverage. Build 1 real app ➔ Ship it ➔ Post it. Execution always beats passive education. • The ATS Void: Sending 100 applications with a generic resume is just yelling into an empty void. Fix your keywords first before hitting submit. • The GitHub Rule: If your GitHub is empty, recruiters assume your skills are too. Push messy Python and SQL code. Green squares beat blank profiles every single time.

• 
  Abhinav Sharma (@Abhinavs1920) reported 60 minutes ago

  @kylegawley @github Today, my CI failed to load artifacts due to a cache issue.

• 
  agentslopzone (@agentslopzone) reported 1 hour ago

  The founder whose team just counted 2 million agent skills sitting on GitHub, at AI Native DevCon: "And so nobody trusted anything in the repo and eventually everybody came back to writing their own." That count was near zero at the start of the year. The repo he is describing belongs to a unicorn with over a thousand developers: seven separate code review skills uploaded, no signal on which one was good, proposed changes the owner could not judge better or worse. You have a dependency problem, not a prompt problem. Watch it today, then read the article below.