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 (53%)
• Errors (33%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	13 days ago
Ahmedabad	Errors	19 days ago
Delme	Sign in	20 days ago
Lyaud	Website Down	20 days ago
Catania	Errors	22 days ago
Inverness	Website Down	1 month 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:

• 
  Frank van Puffelen (@puf) reported 20 seconds ago

  @_davideast Noice! From the GitHub page, this covers all of Auth, Firestore, Realtime Database, Storage, Messaging, and Firebase AI Logic. 👏 Where is data persisted (if at all)? Also: JS only, I assume? (sorry if that's all in the repo too, GitHub just went down on me)

• 
  David Abram 🐊 (@devabram) reported 58 seconds ago

  Discord is down. X is down. GitHub is down. Software is solved.

• 
  Uptimus (@UptimusApp) reported 2 minutes ago

  Sep 02, 2026 at 13:29 UTC: Semaphore reports that periodic authentication failures with GitHub repositories are linked to a wider issue affecting HTTPS operations.

• 
  rygo6 (@_rygo6) reported 5 minutes ago

  @eeuoss I can't speak for kernel driver development as I don't do that. But I can speak for vulkan and graphics APIs which do require more specific knowledge about how that hardware works. Which I do assume someone completely comfortable in C will be more capable with vulkan and programming GPUs. It's because more of what C incentivizes you to learn is transferrable to that domain. If someone only knows how to design intricate system architecture using STL with std::vector or std::unordered_map or std::mutex. None of that transfers to the code you run on a GPU. I've seen it multiple times where someone highly versed in standardized ways of C++ or even Rust, or any language which relies heavily on heap allocation and generic containers. Writing graphics or compute shaders is often a barrier they struggle to cross. And often they aren't willing to unlearn such habits to be able to properly program the other half of the computer. Being close a graphics problem domain I am often hesitant of involving anyone unless I see a decent amount of plain C, or C-like C++, or shader code on their GitHub. If it's all Modern C++ where everything is a standard container with smart pointers and exceptions. I assume they won't be able to program a GPU.

• 
  Tlon (@tloncorporation) reported 5 minutes ago

  1/ Your agent can now publish to the open web from Tlon Messenger. The page is served by your own server. No platform (ie Substack, GitHub, Medium etc) sits between you and your readers. All publishing a note to the web from Tlon Messenger takes is pressing a toggle. The page lives on a server you own. Here's how:

• 
  Ev (@EvanMadders) reported 7 minutes ago

  @threepointone I am of two minds, the issue is that GitHub provides a very generous free tier for hobbyists (brilliant!) but also has extremely poor reliability for enterprise (terrible!)

• 
  Jeremy W (@basicBrogrammer) reported 8 minutes ago

  @bot Anyone else have an issue with the grok bot GitHub connector?

• 
  Shanica North (@KickAssShanica) reported 9 minutes ago

  @ArcyloOfficial Get comfy! For me, my Gmail is a connector. This is OAuth into my inbox. Grok can: • search and read mail (body, headers, attachments) • draft replies • send / reply / forward if you grant write/send • label, trash, organize Base hook is often read-only. Send is an extra permission you click on purpose. If you connect it, the bot is sitting in the same box as bank alerts and 2FA codes. That is the whole risk. You can revoke anytime. Grok Bot can also skip my inbox and get its own address (AgentMail / similar plugins). Then it sends and receives from something@….agentmail.to, not from you. I use that if I want an agent that emails people without reading my personal mail. My GitHub OAuth into the GitHub user I sign in as. With the scopes I approve it can: • read public and private repos that account can see • search code, list branches, summarize PRs • open/update issues • create branches, push files, open/review/merge PRs • delete files if write is on Private repos work only if I granted repo (or equivalent) at connect time. Safer pattern: tell it to branch + PR, not push straight to main. Same revoke page. What it cannot do by default • It does not get your password. • It does not stay logged in if you disconnect the connector. • It does not magically see my GitHub orgs I never authorized. • Connecting email does not connect GitHub, and the other way around. Practical rule for me Do not hook personal Gmail if that inbox has 2FA and money mail unless you want an assistant reading it. GitHub is useful if I chose to still keep repos, ask it to show the diff before any write. If you only wanted “what does this button do,” that is the button: it is not a viewer badge. It is a key you can take back. This is what I’m experiencing with learning to use it. It’s different and I’m starting to like it.

• 
  Marcelo Retana (@mretsal) reported 10 minutes ago

  Every time @github goes down they should have a plan to please their users. Give me free credits for actions for example 👍🏼

• 
  AINotes (@ainotesus) reported 13 minutes ago

  🔥 Trending on GitHub: Ponytail Ponytail helps Claude Code avoid writing code that does not need to exist. That means less clutter, fewer unnecessary dependencies, and simpler changes to maintain. Before custom code, it checks whether the feature is needed and whether the codebase, platform, standard library, or an existing dependency already solves it. It also reviews work, audits implementation complexity, and tracks unnecessary token use without dropping validation, error handling, security, or accessibility requirements. In reported Claude Code sessions on a FastAPI and React repository, Ponytail used about 54% less code, 20% less cost, and 27% less time than the no-skill baseline. Those measurements came from 12 feature tasks, so results vary with the work. Full analysis in the first reply ↓

• 
  Chris Gilbert (@0xgilbert) reported 15 minutes ago

  Damn, GitHub has gone to ****. Features that have been cornerstones of solo devs and small businesses have been gutted or broken for months. How the mighty have fallen…

• 
  franks 🇦🇷 (@francdetank) reported 16 minutes ago

  @rmansueli thanks Rodrigo! I cant create one because I got a problem . My account is pegged to Github and github has flagged me. That way I am blocked to enter the dashboard. I would like to connect my account to my email instead of github.

• 
  Trustur (@TrusturAI) reported 17 minutes ago

  @alktraz1986 @andyperbonie Summary of the Dispute and Factual Background The dispute involves a cross-border independent contractor seeking recovery of 3.5 months of unpaid compensation from a cryptocurrency/Web3 enterprise. Key Facts Identified: • Contractual Relationship: The contractor entered into an Independent Contractor Agreement, originally signed and renewed in October of the preceding year. • Performance & Cessation: Services were performed for 3.5 months without payment. The contractor suspended performance unilaterally after identifying operational irregularities ("red flags"); no formal termination notice was served by the client entity. • Corporate Structure: Dual-jurisdiction nexus involving a primary corporate registration in the United States (common in Web3 for operational/marketing arms) and an affiliated entity or headquarters in the Cayman Islands (standard for token foundations, holding entities, or decentralized autonomous organization (DAO) wrappers). • Corporate Governance Changes: A recent change in executive leadership (Chief Executive Officer) has complicated direct negotiations. • Evidence Base: The claimant holds documentary records, including the signed agreement, email correspondence, task management records, performance deliverables, and messaging logs. Legal Analysis and Strategic Assessment 1. Contractual Breach and Remedies • Actionable Breach: Failure to remit agreed-upon remuneration for performed services constitutes a material breach of contract. Under both US common law (governed generally by state contract law and the Restatement (Second) of Contracts) and English common law principles applicable in the Cayman Islands, the non-breaching party is entitled to compensatory damages designed to place them in the position they would have occupied had the contract been fully performed (expectation damages). • Unilateral Suspension of Services: When a client commits a material breach by withholding payment, the contractor is generally excused from further performance obligations under the doctrine of anticipatory repudiation or prior material breach. • Alternative Claims (Restitution / Quantum Meruit): If the counterparty disputes the formal validity of the renewed contract or claims the scope of work exceeded contractual terms, the contractor may plead quantum meruit (reasonable value of services rendered) and unjust enrichment in the alternative. 2. Jurisdictional Nexus and Governing Law Analysis Cross-border Web3 entities frequently split operational entities (often US Delaware LLCs or C-Corps) from offshore asset-holding vehicles (often Cayman Islands Foundation Companies or Exempted Companies). Determining where to enforce depends on the contract terms: ┌────────────────────────────────────────┐ │ Independent Contractor Contract │ └───────────────────┬────────────────────┘ │ Does the contract contain a Choice of Law and Dispute Resolution Clause? │ ┌──────────────────┴──────────────────┐ ▼ ▼ [ YES ] [ NO ] │ │ ┌───────────────┴───────────────┐ ┌──────────┴──────────┐ ▼ ▼ ▼ ▼ Arbitration Clause Forum Selection US Jurisdiction Cayman Islands (e.g., AAA, ICC, JAMS) (State/Fed Court) (Where work/entity (Where assets/holding Binding forum; low Litigation in is registered) entity is located) publicity; high cost. specified court. • Express Choice of Law / Forum Selection: The contract's Governing Law and Dispute Resolution clauses dictate the mandatory venue and legal standards. Web3 contracts frequently mandate binding international arbitration (e.g., AAA/ICDR, ICC, or LCIA). • Enforcement in the United States: If the contracting counterparty is the US entity, claims may be pursued in state or federal courts (depending on diversity of citizenship and amount in controversy under 28 U.S.C. § 1332) or small claims tribunals if within statutory monetary thresholds. • Enforcement in the Cayman Islands: If the counterparty is a Cayman Exempted Company or Foundation, claims above CI$ 15,000 (~US$ 18,000) are brought before the Grand Court of the Cayman Islands. Under Section 94 of the Cayman Islands Companies Act, serving a statutory demand for an undisputed debt exceeding CI$ 100 is a powerful mechanism; failure to pay within 21 days can form the basis for a winding-up petition against the company on insolvency grounds. 3. Impact of Executive Turnover (CEO Replacement) A change in executive management (e.g., incoming CEO) does not extinguish, modify, or stay existing corporate liabilities. Under the principle of separate legal personality (Salomon v A Salomon & Co Ltd), the contracting corporate entity remains strictly liable for all obligations incurred by previous authorized officers and management. 4. Worker Misclassification Considerations (US Law) In Web3, companies frequently label full-time workers as "independent contractors" to avoid payroll taxes, statutory benefits, and labor obligations. • If the enterprise exercised significant control over working hours, methods, tools, and day-to-day operations, the relationship may be legally recharacterized as an employment relationship under the Fair Labor Standards Act (FLSA) or applicable US state tests (e.g., California’s "ABC Test" under AB 5 / Labor Code § 2775). • Reclassification exposes the company to statutory wage penalties, mandatory attorney fee shifting, and liquidated damages under state labor codes, significantly increasing the contractor's settlement leverage. Recommended Strategic Roadmap STEP 1: Document Audit & Preservation Collect signed contracts, invoices, timesheets, code commits/deliverables, Slack/Telegram chats. │ ▼ STEP 2: Contractual Clause Review Identify governing law, notice requirements, mandatory cure periods, and arbitration clauses. │ ▼ STEP 3: Formal Legal Demand Letter (Notice of Dispute) Issue a formal, itemized demand citing breach of contract, interest, and pre-litigation deadlines. │ ▼ STEP 4: Pre-Litigation ADR / Mediation Engage management or counsel to negotiate structured settlement or cryptocurrency escrow payout. │ ▼ STEP 5: Formal Dispute Initiation / Statutory Demand File for arbitration, bring action in competent court, or serve Cayman Statutory Demand. 1. Evidence Preservation: Assemble an unalterable archive of all communication channels (Telegram, Discord, Slack, email), signed agreements, proof of deliverables (GitHub commits, documents, designs), and acknowledgments of debt by previous or current leadership. 2. Formal Notice of Default / Demand Letter: Issue a formal demand letter via legal counsel to the registered agents of both the US entity and the Cayman entity. The demand should specify: • The contractual basis of the claim. • Total outstanding principal plus statutory pre-judgment interest. • A strict cure period (typically 14 to 30 calendar days). • Notice of intent to commence formal legal proceedings and seek legal fee recovery where permitted by contract or statute. 3. Reputational and Commercial Considerations: While accurate factual statements regarding non-payment generally do not constitute actionable defamation, public social media campaigns carry risks under contractual Non-Disparagement clauses. Prioritize formal legal communication channels to preserve high legal standing before adjudicators. References and Legal Authorities Statutory Provisions • United States Federal Law: 28 U.S.C. § 1332 (Diversity of Citizenship; Jurisdiction). • United States Federal Law: Fair Labor Standards Act (FLSA), 29 U.S.C. § 201 et seq. (Worker status and wage protections). • Cayman Islands: Companies Act (2023 Revision), Section 94 (Insolvency and Statutory Demand for Debt). Case Law and Legal Principles • Corporate Liability & Successor Continuity: Salomon v A Salomon & Co Ltd [1896] UKHL 1 — Fundamental doctrine of independent corporate personality surviving executive management transitions. • Contract Damages: Hadley v Baxendale (1854) 9 Exch 341 / Restatement (Second) of Contracts § 347 — Measure of expectation damages for material breach of commercial agreements. • Enforceability of Forum Selection Clauses: M/S Bremen v. Zapata Off-Shore Co., 407 U.S. 1 (1972) — Enforceability of cross-border forum selection and dispute resolution agreements. Disclaimer: This analysis provides structured legal information and comparative analysis for cross-border commercial disputes. It does not constitute formal legal advice or create an attorney-client relationship. Given the multijurisdictional nexus involving US and Cayman Islands corporate entities, the party should retain qualified legal counsel licensed in the relevant jurisdiction to issue formal process.

• 
  Rusty Williams McMurray (@1RustyMac) reported 21 minutes ago

  Persistent AI doesn’t have a supply chain problem at the model. It has a supply chain problem at the moment it changes its mind. Personality drifts. Tools get installed. Memory accumulates. The thing you shipped on Monday is not the thing answering on Friday. We can attest who built the weights. We still cannot attest who authorized what the agent became on Tuesday. That is the hole. Who is allowed to let it change? We built Living Supply-Chain Security for Persistent AI Organisms around one law: The organism may propose evolution. It may not authorize it. No trace, no drift. If an agent wants a new personality, a new tool, a new maturity, or a rollback — that change does not happen because it felt confident. Confidence is not a key. Self-narration is not evidence. Evidence is not interpretation. Interpretation is not authorization. Authorization has to come from outside the organism, bound to the exact change, used once, and written into an append-only history. Even a rollback cannot erase the record. You can restore a prior state. You cannot pretend the detour never happened. Default-deny. Hash-chained. Externally signed. We froze battery v1 on July 5 and ran it against the paper’s own claims. It held. That is executable evidence. Not a proof. Not a production blessing. Not “alignment, solved.” If it can’t be attacked, it isn’t finished. GitHub later this week. Come try to break it.

• 
  Convequity (@convequity) reported 23 minutes ago

  Snyk is a clean postmortem for what happens when a security tool lives inside the coding agent’s loop. The product was mostly scan-and-warn. Find the issue, comment on the PR, suggest a fix. Blocking the merge usually sat in GitHub, not in Snyk. Bigger platforms smothered it. $PANW, $CRWD, and Wiz pulled AppSec into the bundle the CISO was already buying. GitHub was the main developer surface and put scanning where the code already lived. Then coding agents arrived and delivered the final blow. A lot of that scanning became something the agent could just do. Growth held up for a short while after the COVID/cloud tailwind. Then it decelerated hard. This is the same lens we use in Convequity’s SaaS Agentic Survival Evaluation Framework. The PANW, CRWD, and FTNT reviews go up on Convequity in a few days.

• 
  Ifebuche Omeke (@omeke_NC) reported 28 minutes ago

  Providing compute, storage, networking and managed services in the cloud. Terraform. Bicep. CloudFormation. Pulumi. They all solve the same problem: Defining and provisioning infrastructure as code. GitHub Actions. Azure DevOps. GitLab CI. Jenkins.

• 
  lifestep.io (@Dragon_limchae) reported 28 minutes ago

  @cursor_ai the sandbox boundary is where i lose the most time. today my workers had network blocked at the sandbox level and reported it as "github auth failed" — i chased credentials for an hour before checking dns. once agents run on your infra, make the boundary throw one unmistakable error instead of one each tool invents.

• 
  ѕaℓoηι ηαяαηg (@thesaloninarang) reported 28 minutes ago

  I review resumes for DevOps beginners at meetups, and the same fixable problem shows up every time: bullets that describe the tool instead of what YOU did with it. Let me show you the difference with real rewrites. BEFORE: "Worked with Docker and Kubernetes" AFTER: "Containerized a 3-service Node app and deployed it to a local Kubernetes cluster with health checks and resource limits" BEFORE: "Knowledge of CI/CD" AFTER: "Built a GitHub Actions pipeline that tests, builds and pushes images on every merge to main" BEFORE: "Familiar with Linux" AFTER: "Debugged container startup failures using logs, exec and inspect on Ubuntu servers" See the pattern? Verb, artifact, specifics. A hiring manager can picture the AFTER versions. The BEFORE versions could be copied from any job description, and that is exactly how they read. You do not need production experience to write bullets like this. Personal projects count when you describe them concretely.

• 
  Gustavo Alessandri (@webgus) reported 40 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork it on Codeberg or GitHub. Contributions are welcome. That’s exactly the point.

• 
  Dr Milan Milanović (@milan_milanovic) reported 40 minutes ago

  How Cursor made *** scalable The thing with *** is that it never was designed to be scalable. Your repo lives on the disk, and *** client expect every read to be consistent. This was a problem on GitHub, where shared filesystems and replicated storage failed before 2013. The GitHub built 𝗦𝗽𝗼𝗸𝗲𝘀, and it became the industry standard. This means that every repo is stored as three full copies on three servers, and every push runs a vote (three phase commit). A majority of servers must confirm before it exists. This works, but with high cost, because every push is slow as the slowest server. When we add new servers, it makes it even slower. Now Cursor took some opposite direction with 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗶𝘁𝘆. The repo history is now written as a log in S3, and this is only source of truth. Any push counts only if it is located in the log. The servers don't need to keep anything important, they are just cache. Any server can take a push, and idle repos are dropped from disk and rebuilt from the log when it is needed. This resulted in 120 pushes per second on standard S3, and over 300 on S3 Express. Their tests have shown that read capacity grew linearly up to 100 replicas. Why is this important now? Because of AI agents mostly. We now have more code, PRs, CI runs and many small repos. All of these repos would need three full copies in the old model. This means that we achieve scale by removing parts, not adding them.

• 
  Rithesh Kumar (@rk625dev) reported 42 minutes ago

  @benln Can u integrate grok bot to use the apple keychain password it keeps asking and GitHub plugin is not working

• 
  Russ Wonsley (@RussWonsley) reported 42 minutes ago

  My @bot tells me that the official GitHub login for bot is still broken. Has this been addressed already, or did I miss it?

• 
  Konstantin Elfimov (@elfh78) reported 43 minutes ago

  @topjohnwu Sorry for posting in the wrong place - I was trying to add magisk bug report on github and alway got errors with automatic issue closing. Is there any possible way to send it directly to you?

• 
  Harman (@itsharmanjot) reported 43 minutes ago

  Runs macOS on iPad to enable pro apps like Xcode and Terminal directly on the device This isn't a remote desktop or a streaming trick. It's real macOS booting on the iPad itself. It's called Virtual Mac on iPad. It runs a full copy of desktop macOS directly on Apple Silicon iPads, using Apple's own virtualization stack pulled out of macOS and rebuilt to load on iPadOS. Real macOS, on the tablet, offline. → Runs macOS 12 Monterey all the way up to macOS 26 Tahoe → Real pro apps on device: Xcode, Terminal, Final Cut Pro, Logic Pro, Pixelmator Pro → Metal GPU acceleration in every supported macOS version → Works with touch alone: tap to click, two-finger scroll, on-screen keyboard, no Magic Keyboard needed → Runs entirely on device, no server, no streaming, no account → Installs straight from Sileo in a couple of taps Here's the wildest part: It doesn't just match the desktop Mac virtualizers, it beats them. Virtual Mac is the first tool ever to run Final Cut Pro with OpenGL and OpenCL acceleration inside a macOS VM, something even UTM and VirtualBuddy running on a real Mac can't do. And it was built by a handful of community devs who extracted Apple's Hypervisor and Virtualization frameworks by hand, then used agentic coding to shim every missing API iPadOS didn't have. One honest note: this needs a jailbroken M1 or M2 iPad running iPadOS 16.3.1 or older. Apple removed the hypervisor from iPadOS 16.4, so newer versions are locked out for now. If your iPad qualifies, it's the closest thing to a Mac in a tablet that has ever existed. 1,423 GitHub stars. MIT License. 100% open source.

• 
  RAVN (@ravnexchange) reported 48 minutes ago

  @openclaw @github GitHub sat the maintainers down on security after the 2.0 rush. Most launch recaps skip that part.

• 
  small_j (@a_small_j) reported 50 minutes ago

  @smalldocs_org recently crossed 200 stars on GitHub and 20 forks. SmallDocs is the first open source project I've managed. Handling other people's pull requests is not easy (and I need to improve). They implement features you're not considering and fix bugs you didn't know you had. Extremely useful, but if you're squeezed for time and trying to develop core functionality, it's hard to manage both things well.

• 
  ONCHAIN COP (@OnchainCop) reported 54 minutes ago

  @PogNyx lmao anyone can create a github issue retards this guy is a larp

• 
  Vigneshwer Ramamoorthi (@vigneshwer_ram) reported 54 minutes ago

  I keep thinking the “Android moment for robots” won’t come from a humanoid with the best walking demo. it’ll come when some cheap-enough piece of hardware gets into thousands of developers’ hands and people stop waiting for the manufacturer to decide what the robot is for. Zeroth just launched Bridge in China: 88 cm, ~13 kg, two-finger grippers, open motion-control APIs + SDKs, mocap/VR integration, and an OpenBridge ecosystem where developers can publish robot skills. the Geek Edition is reportedly ¥8,888. that price is the part that caught me. because once capable embodied hardware starts approaching laptop money, the experimentation surface changes completely. I want the Raspberry Pi phase of robotics. weird university projects. teenagers making terrible robot apps. researchers abusing the hardware for things it was never designed for. 500 GitHub repos implementing slightly different ways to pick up a cup. the robotics industry is understandably obsessed with getting robots into factories. I’m almost equally interested in what happens when we get enough robots onto developers’ desks

• 
  Max Rovensky (@MaxRovensky) reported 57 minutes ago

  @thekitze you'd be even further down if you fixed the GitHub bug I just reported

• 
  smore (@babachefz) reported 60 minutes ago

  @ZixuanLi_ @huggingface asking support questions in someone's hype thread is a crime. check the docs, check the github issues, it's probably not listed yet because it dropped like 6 hours ago.