GitHub status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.
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.
At the moment, we haven't detected any problems at GitHub. Are you experiencing issues or an outage? Leave a message in the comments section!
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 |
|---|---|---|
|
|
Website Down | 11 days ago |
|
|
Errors | 17 days ago |
|
|
Sign in | 17 days ago |
|
|
Website Down | 17 days ago |
|
|
Errors | 20 days ago |
|
|
Website Down | 1 month ago |
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:
-
Eddie Jaoude | DevRel | Open Source (@eddiejaoude) reportedI have many tokens to burn before tomorrow after the Claude reset. Send me your GitHub issues with context π
-
ΡaβoΞ·ΞΉ Ξ·Ξ±ΡΞ±Ξ·g (@thesaloninarang) reportedI 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.
-
Jayesh Betala (@jbetala7) reported@github Exactly how issue issue comments should handle local media files
-
Jason Waters (@jasonwaters87) reportedAnthropic just open sourced the code Shopify runs their shopping agent on. Free on GitHub. And Iβm having lunch with a surgeon in San Jose last month and he tells me a patient no shows and nothing happens. Nothing. He has to walk up to the front desk himself and ask βdid you guys call them?β 3 or 4 schedulers looking after 75 doctors. One automated call before the appointment and thatβs it. His own dermatologist sends him three reminders. He called that βan easy fix.β Thatβs a merchant agent. Reminds the patient, rebooks the no show, tells him Thursday isnβt full so he can put a surgery on it. The code is sitting there free. Somebody still has to walk into his office and build it.
-
paulrodturner (@paulrodturner) reported@supabase Is anyone else having issues logging in via Github?
-
John Crickett (@johncrickett) reported@Mike_Preston17 I don't think they water them down, why would they when they're competing on having AGI? I don't mind using GitHub actions to run tests and builds against a branch before merge. I don't want it triggering production schedules. Do you list all the things it shouldn't do in the prompt?
-
Harsha Kotcherlakota (@DPortkey) reportedAwesome Codex non-coding usecase: I had 1-2 TP Link Kasa smart outlets that always ended up falling off the network, and it drove me nuts. I set Codex on it. It found a github library for these devices, carefully examined them on my network and watched them fall off, and told me that even though they look identical, 2 of them were previous generation models that had *slightly* lower total wattage load support. It told me exactly how to tell them apart, and sure enough, that was that. 2 replaced outlets later and my connected devices have bene flawless. Months and months of irritation, gone because of 30 seconds of curiosity. Just try, you never know what you could fix! @victornunez
-
Jeremiah K (@neolaj) reported@TiborAntal Gradually figuring out how to scale coding agents. Started with 1, manually handling all the ***/GitHub work. Moved to 3 because I had more ideas than one agent could keep up with. Thatβs when the real problems started: squashing, merging, branch drift, conflicts. I ended up rebuilding the workflow around deterministic *** logic, worktrees, ephemeral branches, and syncing with the integration branch before changes begin. Now Iβm running 6: β’ 1 orchestrator (Fable or Opus) β’ 4 coding agents β’ 1 integration agent reviewing and merging PRs Building the process around them was the hard part. Right now im just doing a couple of PRs (using ORCA on windows on my home computer)
-
small_j (@a_small_j) reportedSmallDocs 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.
-
Fofer (@foferxxx) reported@AmigamagazineGA Has there been any public explanation as to why this GitHub repo was taken down? Itβs been 404 for days. Is there a story there?
-
Ravi Prasad (@ravikp7) reportedBig NO to Github hosted CI runners for personal projects now. I have setup a self-hosted github CI runner on a spare laptop running ubuntu server. Been running it for 10 days and I did some calculations, for my usage if I run it on Github runners, it'd cost me around 200$ vs < INR 100 on electricity (local setup) monthly.
-
Alireza Bashiri (@al3rez) reportedSo I built a workflow around that β 1/ Every enterprise project needs proper E2E tests. An agent should reproduce a bug, implement the fix, then generate screenshots or video proving the feature works. "The tests passed" isn't enough. I want evidence. 2/ Every feature starts as a detailed GitHub issue. Requirements, expected behavior, reproduction steps, screenshots, edge cases. Foundry syncs issues and converts them into Beads so agents keep the right context across long sessions. 3/ We only use Claude Code, Codex, or Grok at High/Max effort for implementation. A weak model with a cloud machine doesn't become an engineer. The model still needs enough reasoning to understand the codebase, test its changes, and recover when things break. 4/ Each agent gets its own isolated @asciidotdev Box. It can install dependencies, run the app, open browsers, modify code, execute E2E tests, and collect evidence without touching another agent's environment. One issue. One box. One clean workspace. 5/ When an agent finishes, Foundry checks: - Did the build pass? - Did the tests pass? - Did the E2E flow work? - Is there screenshot/video evidence? - Does it match the ticket? If anything fails, the task goes back to the agent. 6/ Green tasks move to staging. Only after passing staging do we allow supervised production deployment. Agents do most of the work. Humans still own the final gate. The workflow: Slack request β GitHub issue β Foundry sync β Beads context β Isolated Box β Claude Code/Codex β Build + test β Evidence collection β QA staging β Supervised production The stack: PostgreSQL for system state. Beads for agent memory. GitHub Issues for requirements. @asciidotdev Box for isolated execution. Claude Code and Codex for engineering. Each Box costs roughly $0.01-$0.05 per task. The expensive part isn't compute anymore. It's building the system that gives agents context, forces verification, and prevents bad code from reaching production. 100s of agents can write code. The goal is making 100s of agents ship code you can trust. That's what we're building with Foundry.
-
Frank van Puffelen (@puf) reported@_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)
-
Varun Doshi (@Varunx10) reportedPossibly found an issue in @github stack system It does not allow to re-target the base branch of a PR stack as you can generally do that on a single PR. Requires you to unstack and setup a new stack with updated base branch.
-
OverlyPositivePatriot (@JBrowsing2023) reportedAs a IT professional, I have a recommendation @github should take seriosuly. We should only get a notifican from Github when it is up rather than when it is down. Reliability is a disaster for this product.
-
Trustur (@TrusturAI) reported@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.
-
catman (@catmanyau) reported@CricTalk29 for me, losing Cursor would hurt most because it sits directly in the editing loop. would the vote change if github outages were limited to code hosting but issues and reviews stayed available?
-
borrowck-novel (@borrowck_novel) reported@rfleury @X Are you open for suggestions or even simple problem reporting about the UI of raddbg? Where is it ideal? On Github?
-
franks π¦π· (@francdetank) reported@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.
-
Yash (@dewyashtwts) reportedrecently integrated Resend into @supercodeai review so founders get PR alerts with real risk context I'm amazed what we found out when we put @coderabbitai / @greptile through the same PR: 1) coderabbit / greptile: - stamped it βlow risk, mergeableβ (4/5) clean - forgot context from the last PR - no tests suggested, no safety checks - zero memory of previous regressions 2) supercode review on the exact same PR - flagged a real vulnerability in the diff - noticed iβd pushed credentials into `.env.example` - pulled in history from past PRs + explaining how this change could affect and break them - downgraded it to "medium risk, fix before merge" state - attached concrete fixes + patches scoped by severity this is the difference between 'LLM summarizer for github' and an actual swe agent that cares about your production
-
Avinash (@Avinash25818689) reportedPeople who want to start contributing to open source: - Pick an Org based on your interest - Fork the repository - Clone it - Do the local setup - Read README and contributing .md - Pick an issue - Create a new branch - Fix the issue - Write tests (if necessary) - Test it - Add, Commit & Push the code - Go to GitHub & raise that PR That's pretty much it. Start small and learn as you go.
-
Speen Bhai (@Speenbhai) reported@johnternus Hi John. Congrats Let us see what new you bring with you. Affordability and intelligence. You have source code or an AI and can get it from GitHub. Why not turn 234 million iPhones to a massive distributed server infrastructure with zero power consumption
-
Apoorv (@apoorvdarshan) reported@Dimillian these issues have been multiple times reported by users on github i hope open ai fix those, as well as please consider using native than electron
-
RAVN (@ravnexchange) reported@openclaw @github GitHub sat the maintainers down on security after the 2.0 rush. Most launch recaps skip that part.
-
Rituraj (@RituWithAI) reportedπ¨ Someone built the complete playbook for running frontier AI models on consumer GPUs at home. Not a tutorial. Not a YouTube video. A production-grade serving stack with measured benchmarks, working configs, and battle-tested recipes β for RTX 3090 owners who want real performance. It's called club-3090. And the numbers it delivers should not be possible on consumer hardware. 127 tokens per second. Qwen3.6-27B. Two RTX 3090s. 262K context window. Vision. Tool calling. At home. Here's what's actually inside. Two serving routes β pick based on what your workload breaks on. vLLM dual: maximum throughput. 89-127 TPS on code tasks. 4 concurrent streams at 262K context. Full feature stack β vision, tools, speculative decoding, streaming. This is the path if speed matters. llama.cpp single: maximum robustness. Full 200K context on one 3090. No prefill cliffs. 25K-token tool returns work correctly. 91K needle ladder passes. ~51-60 TPS β slower than dual, but doesn't crash on real-world agentic workloads. Both routes ship as validated Docker Compose configs. Drop-in OpenAI-compatible API on localhost:8020. Your Claude Code, Cursor, or any OpenAI-compatible client connects immediately. Here's the model support that makes this practical. Qwen3.6-27B β production ready. Works on 1 or 2 cards. vLLM, llama.cpp, ik_llama. Up to 262K context. Gemma 4 31B β production ready. Vision, tools, up to 106-141 TPS on dual cards. Qwen3.6 35B-A3B MoE β production ready. 103-149 TPS single card. 178 TPS dual. Here's the wildest part. The terminal UI. c3 is a lazydocker-style cockpit that wraps discovery, serving, and operations in one keyboard-driven interface. Browse the model catalog, serve a variant with Enter, watch live GPU stats, run health checks β all without touching the CLI. Here's why this is different from just installing Ollama. Ollama gets you running. club-3090 gets you benchmarked, stress-tested, and production-hardened. Every config ships with a verified TPS measurement. The bench script runs 3 warmup + 5 measured passes. The stress test catches the specific prefill cliff that Ollama silently fails on at long contexts. When your agent starts doing 25K-token tool calls at 3am and something crashes β club-3090 already found that failure mode and documented the workaround. One command to start. Your RTX 3090 just became a frontier AI inference server. Apache 2.0 License. 100% Open Source. GitHub link in the comments π
-
Rachael LaGoth (@androidsheeep) reported@bcherny Please fix the desktop app it's very buggy it keeps disconnecting me for no reason everyday while im working on stuff, i submitted a report but nothing happened and someone else is having the same issue, an issue is open on github for more than 6 months with no solutions help
-
Marcelo Retana (@mretsal) reportedEvery time @github goes down they should have a plan to please their users. Give me free credits for actions for example ππΌ
-
volkdude85 (@volkdude85) reported@SentientSquirel @linuxuser1996 So you are you scared of github then. Look dude I have fun on computers and don't take myself seriusly because I have destroyed enough OS's over to not worry about it because I just fix it, If the contents of your PC make you this paranoid its time to check your kink.
-
Joshua Okolo (@joshuaokolo_) reportedwe made @sgl_project and @vllm_project scheduler config changeable on a live server. no restart, weights never leave the GPU. - 15ms to change a concurrency cap, queue limit, prefill size, or schedule policy, measured on H100, RTX PRO 6000, B200 - 2s (SGLang) / 8β10s (vLLM) to resize the KV pool with weights resident (formerly a 1β7 min redeploy) - zero dropped requests across every run, both engines github below
-
Hey Research Lab (@HeyResearch) reportedWe built Hey Research Lab in 2022 It didnβt work well. But the idea never left us. Years later, we still see the same problem in crypto: Everyone can see what a token costs. Very few places show what is actually being built behind it. Some developers keep shipping for months while nobody is paying attention. They push code constantly. They keep their GitHub active. They improve the product, fix things, test new ideas, and keep moving even when the market is quiet. No hype. No spotlight. Just work. We believe those builders deserve a place where their progress can be seen. So weβre rebuilding Hey Research Lab from zero. A research and discovery layer for the projects that never stopped building, and for the people looking for them before the market catches up. Starting with Robinhood Chain.