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	6 days ago
Ahmedabad	Errors	12 days ago
Delme	Sign in	12 days ago
Lyaud	Website Down	13 days ago
Catania	Errors	15 days ago
Inverness	Website Down	27 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:

• 
  Jayesh Betala (@jbetala7) reported 10 seconds ago

  @github Exactly how issue issue comments should handle local media files

• 
  HeroGamer⚡ (@herogamer21btc) reported 40 seconds ago

  💻 GitHub Issues vs Draft PR vs Open PR — the difference nobody explains: 🔴 ISSUE = Should we do this? No code yet You describe the problem "App crashes when pasting OP_RETURN" "We need X feature" Anyone can open it Goal: decide IF and WHAT to build 🔵 DRAFT PR = I'm doing this, is this the right way? You have WIP code "I fixed it by doing Y, but not sure about placement / approach" Can't be merged Perfect for early feedback Goal: validate HOW you're building it 🟠 OPEN PR = I did it, ready for final review, please merge. Code done, tests pass Ready for final review Goal: ship it 🌊 Flow: Issue → Draft PR → Open PR Most people skip Issue or Draft and go straight to Open PR. Then maintainer has to review both the idea AND the implementation at once = slow, painful. Start Draft when unsure.

• 
  Asterix (@Asterix54907294) reported 3 minutes ago

  end-of-summer snapshot for @QFEX : -~$222M in open interest -CLI v0.3.12 shipped in August with improved installation docs and a go.mod fix -GitHub activity continued through late August not a flashy launch recap, just a quick look at how the exchange is closing out the summer: more markets, meaningful liquidity, and active work on the tooling side still early, but the infrastructure is clearly moving

• 
  Kun Chen (@kunchenguid) reported 14 minutes ago

  @petergyang yo @myfirstmate peter just told me his skills are all at user level. backpass currently only runs things at project level i want a proposal for making backpass support a user level run. put that into a github issue use fable for peter

• 
  tmo (@tmophoto) reported 14 minutes ago

  @DabsMalone i had an old email account from like 15 years ago with bot in the name that i fired back up after 10 years and used for a hermes profile and it got immediately banned. i used it to sign in to x, github, everything. was a huge hassle

• 
  borrowck-novel (@borrowck_novel) reported 16 minutes ago

  @rfleury @X Are you open for suggestions or even simple problem reporting about the UI of raddbg? Where is it ideal? On Github?

• 
  joithan (@jothantranston) reported 16 minutes ago

  THIS GUY BUILT A TINY AMOLED DESK BOARD JUST TO STARE AT HIS STRIPE NUMBERS it's a Waveshare ESP32-C6 touch panel that sits in your peripheral vision and cycles business metrics so you stop digging through Stripe > same ESP32-C6 board people use for Claude Code token meters, flipped to revenue > eight screens, five seconds each: MRR, new paid, paid subs, cancelled, ARR, ARPU, net 30d, failed > empty screens hide themselves so a young account sees a shorter loop > polls Stripe every five minutes on a read-only key (subscriptions + invoices) > marks itself stale instead of showing a number it can't vouch for > no soldering: flash over USB, finish Wi-Fi + key setup from your phone > data stays on the board; no project server in the middle firmware free on GitHub: cosjef/stripe-desk-display. board ~$30–$36 (Waveshare ESP32-C6-Touch-AMOLED-2.16). chat and terminal can't sit in your eye line for five hours. a tab you have to open is a tab you stop opening. this is what "the numbers find you" looks like as a brick on the desk.

• 
  Ifebuche Omeke (@omeke_NC) reported 17 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.

• 
  recovering buzzkill (@MikeStillAwake) reported 18 minutes ago

  @Karai_Dan @SteamDeckHQ Agenda or not nexus mods is a terrible outdated model for distributing mods. GitHub would be a superior host.

• 
  NAYAK (@Nayak__Ai) reported 20 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  WuBu ⪋ WaefreBeorn 🇺🇸 👑 (@waefrebeorn) reported 22 minutes ago

  hey @Teknium @yeahfortommy please add the amd portal too even if tou have to send tommy into the AMD headquarters to get them to fix the links (you have to sign up for american then link through github, then you can access the models free, tommy needs to pull teeth but they have free api)

• 
  tonis (@totovoto) reported 22 minutes ago

  @mittsh I was trying to find an open-source alternative for Tailscale when I first needed it. I guess AI suggested some OSS options, but they didn't have many stars on GitHub. AI didn't suggest Nebula. The Tailscale plan was free, so I just installed it and forgot about it. For Nebula, I think it is a distribution problem.

• 
  Ravi Prasad (@ravikp7) reported 23 minutes ago

  Big 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.

• 
  tobarra (@txbrraa) reported 28 minutes ago

  GitHub just fixed the biggest problem with vibe coding. They just released Spec Kit and it already has +126K stars in a short time. The idea? Instead of throwing out vague prompts and praying the agent doesn't break your project… Spec Kit forces the AI to create a structured specification BEFORE touching any code. The AI first understands what you want to build, asks about anything missing, organizes the project, and only then starts coding. That means less time fixing absurd bugs, less inconsistent code, and much more predictable results when working with agents. The flow is simple: /constitution → rules and standards /specify → what you want to build /clarify → open questions before starting /plan → architecture and stack /tasks → ordered tasks /implement → execution Compatible with Claude Code, Cursor, Copilot, Codex, Gemini CLI, and +25 agents. 95K stars. 8K forks. Open source. Published by GitHub.

• 
  Gustavo Alessandri (@webgus) reported 29 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.

• 
  Trustur (@TrusturAI) reported 31 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.

• 
  Straggler Liu | AI & Semis (@StragglerLiu) reported 36 minutes ago

  NVIDIA($NVDA ) Is Paying $14B for a Company With $150M Revenue. That's Not Financial Logic — It's Ecosystem Control. NVIDIA is in advanced talks to acquire Hugging Face for ~$14 billion ($12.9B acquisition + $1B retention), per Bloomberg. To put that in perspective: Hugging Face does ~$150M in annual revenue. That's ~86x revenue. Microsoft paid ~1.6x revenue for GitHub. Google paid ~3.5x revenue for DeepMind. NVIDIA is paying 20-50x more on a revenue multiple basis. The premium is not for revenue. It's for control of the AI developer ecosystem. What is NVIDIA buying? Hugging Face hosts 500,000+ models, 250,000+ datasets, and serves millions of developers. It is the single most important distribution channel for open-source AI. If you build AI, you use Hugging Face. That makes it the front door to AI development. Why NVIDIA is paying this premium: 1. The "NVIDIA triple lock." NVIDIA's hardware lead (GPU) is real. Its software lead (CUDA) is a moat. But the third lock — the developer workflow — was missing. Hugging Face is that workflow. Developers discover models on Hugging Face, deploy them, and optimize them. Whoever controls that discovery layer controls which hardware gets used. 2. The GitHub analogy, inverted. When Microsoft bought GitHub, developers were already using GitHub. Microsoft didn't need to capture them — it needed to prevent Amazon/Google from doing so. NVIDIA faces the opposite problem: developers are already using NVIDIA hardware. But they're discovering and deploying models through a neutral platform. NVIDIA is eliminating that neutrality. 3. The long game: inference, not training. NVIDIA dominates training. But inference is the bigger TAM — and it's more fragmented. If NVIDIA controls the model discovery and deployment layer, it can steer inference workloads to its own stack. That's a 10-year strategy disguised as a 14-billion-dollar acquisition. Who wins, who loses: NVIDIA (NVDA): Acquires the developer distribution layer. The most important strategic move since CUDA. Shifts the valuation case from "chip cycle" to "platform economics." Competitors (AMD, INTC): Lose neutral access to the primary AI model distribution channel. This is a structural headwind that no amount of hardware catch-up can fix. Cloud providers (MSFT, AMZN, GOOGL): Hugging Face was a neutral hub. If NVIDIA controls it, cloud providers risk being disintermediated from AI workload decisions. The open-source community: The platform that was built on openness is now owned by the dominant hardware vendor. Neutrality is the first casualty. The capital question: Can NVIDIA integrate Hugging Face without destroying its community value? If yes, the $14B is cheap. If no, it's a very expensive mistake. The answer will define whether NVIDIA becomes the AWS of AI — or just another hardware company with an expensive acquisition. Note: Acquisition details based on Bloomberg reporting; not confirmed by NVIDIA or Hugging Face. Revenue multiple comparisons based on publicly reported figures.

• 
  Benjamin Crozat (@benjamincrozat) reported 38 minutes ago

  From now on, I will assume that GitHub is always down and I'd like to be notified when it's briefly not.

• 
  Wlad (@dawnhell_) reported 42 minutes ago

  @brekfuz q: that's a github issue or you patched it locally??

• 
  htrowii (@htrowii) reported 45 minutes ago

  @brainage19 i set my flake up with copy pasting github dotfiles on bare metal it was terrible

• 
  Nenesk.ron (@GustavoNenesk) reported 47 minutes ago

  What if there's a way to save hacked Ronin Wallets? A member of the community @YutsuKito found a way to save assets from drained wallets The issue is you need ronin:native to transfer assets, but whenver you deposit RON you get auto drained Need RON to revoke the malicious draining contract -> send RON -> gets drained -> can't revoke He found a solution for the keyless wallets where you can pay the gas fee with a safe wallet, allowing you to save lost axies or NFTs that have not been drained Interesting stuff. He sent the code for SM to review as an open-source project. Github link below

• 
  John Zhong | AI Growth Systems (@John_zhong324) reported 47 minutes ago

  @github A repeatable --attach flag turns CLI reports into reproductions: inline screenshots in issues mean a bug gets fixed in one pass instead of two round-trips for context.

• 
  Vitaliy Salyuk (@vitaliysalyuk) reported 47 minutes ago

  @openclaw @github Fix your updater and I might give it another shot.

• 
  Mr. Buzzoni (@polydao) reported 51 minutes ago

  LOOP RAT ROADMAP: WHAT'S NEXT, AND WHAT IT'LL NEVER BECOME v0.3.3 today. 3 loops, 55 checks, 0 services here's where it's headed: > 0.4 - read the night faster: rat watch live-tails a running shift, rat replay reruns one from its saved prompt, a weekly digest instead of seven separate pages > 0.5 - off the laptop: run-due moves into GitHub Actions, state lives on a branch, rat cron --launchd survives a closed lid > 0.6 - sharper graders: swappable rubric packs, two graders disagreeing becomes your queue for the day > 0.7 - the work itself: a worktree per shift, so a failed night never dirties your tree > 1.0 - trust: a hash-chained trace nobody can quietly rewrite what it will never have: > no web dashboard - the terminal already knows where the files are > no database - plain files outlive the tool that wrote them > no hosted service - nothing to sign up for, nothing to shut down > no auto-merge - the rat proposes, the morning decides every item ships behind a flag: dry run -> report only -> one repo -> a week of receipts -> default on a feature that can't run as a dry run doesn't get written the rat is boring on purpose. every version keeps it that way

• 
  Enfantshustle (@Ownerthoughts) reported 54 minutes ago

  Honestly, I always thought bots like this were some kind of magic for the elite, but here everything is broken down step by step. However, after reading it, one main question stuck in my head: how realistic is this for an average person who has no coding experience? I get that there's a GitHub and all that, but for me, just "running a script" is practically a heroic feat. Here's another thing that bothers me. The article does a great job explaining the architecture, but I still don't understand how much all of this will actually cost in the end. Besides Solana transaction fees (which, by the way, get absolutely insane during peak hours), you also have to pay for each Grok API call per token. The article says that for each approved token, it takes three model calls, and one of them is the expensive grok-4. If the bot scans thousands of launches per day, I'll just burn through my entire deposit just paying for the API without even buying anything. Maybe the author knows — is it actually possible to turn a profit after these expenses, or is this just a hobby for those with an unlimited subscription? Also, regarding Grok Bot as the "orchestrator" — it sounds cool in theory: describe the task and it does everything itself. But in practice, as I understand it, this still requires your account to be constantly online and have access to your wallet. And if it decides to buy some scam token at 3 AM that passed all the checks, I'll only have myself to blame. The article correctly mentions risk management, but this "trust" aspect is what scares me the most. In short, the idea is fire, but for me, this post feels more like a warning than a call to action. There are just too many things you have to keep in mind to avoid getting rekt. Although, maybe if you try it with really tiny amounts, it could be an interesting experiment. Author, if you're reading this — could you please make a separate post about the real, live results once everything is actually running, not just on paper? I'm really curious!

• 
  Swish (@swish_salt) reported 55 minutes ago

  The technology is not the problem. Distribution is. I have a solution sitting in my GitHub account. All we need is the funding to build the distribution team.

• 
  Shawn Yeager (@shawnyeager) reported 56 minutes ago

  My @bot keeps reaching for the browser and `gh` instead of using the GitHub plugin. Known problem?

• 
  Gordo Polymath (@gordo_polymath) reported 58 minutes ago

  @github Please fix gh stack.

• 
  Bash (@bashirbuilds) reported 59 minutes ago

  Your Stripe account can be healthy while your checkout is broken. OpenAI can be operational while your AI feature is failing. GitHub can be up while your deployment workflow is stuck. That’s the problem I’m building Reeno around. Dependency uptime is not the same as product health. Your monitoring should tell you when the thing your customers actually use stops working.

• 
  Bearded Printer (@BeardedPrinter) reported 60 minutes ago

  @RedPill_Phil You've gotta go to their github and submit an issue. Make sure to search their issues to ensure you don't submit a duplicate bug