GitHub 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:

• 
  isha (@heeyyaaaaaaa) reported 5 minutes ago

  spent the entire day trying to reproduce a bug for a github issue 🥀🫩

• 
  阮添福-ThiênPhúc (@vietroadie) reported 6 minutes ago

  Feature request for @TradingView @TrendSpider @Schwab (ThinkOrSwim) engineering teams: Please add GitHub-native CI/CD for custom indicators. Connect a repo → validate on push → deploy approved scripts to my workspace → full version history + rollback. 1/ The Problem I maintain the same level set across ThinkScript, Pine, and JS. One level change = 3 manual copy/pastes into 3 browser editors.Result: drift between platforms, stale timestamps, and levels that silently disagree mid-session. No audit trail of what changed or when. 2/ Core ask — repo connection • OAuth GitHub App install, scoped to selected repos • Map a file path → a specific study slot (e.g. ES Levels/ES_LEVELS.pine → "ES Levels") • Branch selection (deploy from main, preview from a branch) • Config in-repo, e.g. .tradingview.yml / .trendspider.yml 3/ Core ask — validation • On push/PR: compile + lint the script server-side • Return errors as GitHub check runs with file + line numbers • Block merge on compile failure • Optional: run a backtest or smoke-render and post results as a PR comment 4/ Core ask — deploy • Auto-deploy on merge, or manual "promote" button • Atomic: study updates or fails cleanly, never half-applied • Deploy to draft/private first, publish separately • Preserve user-set inputs across deploys where param names are unchanged 5/ Core ask — versioning & safety • Every deploy tagged with commit SHA, author, timestamp • Version list in the UI with diff view • One-click rollback to any prior commit • Dry-run mode • Deploy log / webhook on success + failure 6/ Minimum viable alternative If full CI/CD is too big, just ship a documented REST API: GET/PUT /studies/{id}/sourcewith token auth + rate limits. We'll build the GitHub Action ourselves. That single endpoint unblocks the entire workflow. 7/ Why it matters Scripts are code. Code belongs in version control with review, CI, and rollback. This is table stakes in every other dev ecosystem — and it directly reduces the risk of a bad indicator edit going live during market hours. Who else needs this? 🙋

• 
  Tlon (@tloncorporation) reported 10 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:

• 
  WuBu ⪋ WaefreBeorn 🇺🇸 👑 (@waefrebeorn) reported 11 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)

• 
  Kun Chen (@kunchenguid) reported 12 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

• 
  Tejas Dinkar (blue tick here) (@tdinkar) reported 13 minutes ago

  Hey - Is @GitHubIndia @github payments down for anyone else? Can't enter a card number or do anything, no errors, no action. Support ticket been sitting around for 2 days.

• 
  Vikas(Vik) Malpani| AI for US Real Estate (@vikasmalpani) reported 14 minutes ago

  GitHub just shipped an agent whose entire job is deciding when a human should look. It checks every open pull request every 15 minutes, and on almost all of them it does nothing. Sit with how strange that is. For a year the whole pitch for coding agents was do the work, review my code, ship the PR. This one's value is the inverse. It runs constantly and stays quiet, and the product is the small set of PRs it decides are actually worth your time. That is the shift people are missing. Once an agent can act continuously, the scarce resource stops being how much it can do. It becomes how much of that is worth a human's attention. An agent that pings you on every pull request is just faster noise. One that surfaces the three that genuinely need judgment is leverage. The honest problem is the deciding. Tune the filter too eager and it cries wolf until you mute it. Too cautious and it silently ships the one change you needed to catch. Getting when to interrupt a human right is harder than getting the work right, and nobody has a clean metric for it yet. So here is the bet. The next moat in agent products is not a smarter model. It is a better sense of when to stay quiet. If you are building with agents, the thing worth obsessing over is not how much work they can generate. It is how well they protect the one budget that does not scale: your attention.

• 
  David Abram 🐊 (@devabram) reported 14 minutes ago

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

• 
  R 'Nearest' Nabors (they/them) (@rachelnabors) reported 20 minutes ago

  @Paul_Kinlan Honestly, the linear method helps. Think of it as having a never-ending trough of issues that agents can pull from. I don't even use linear. I just use GitHub with linear flavouring added

• 
  Fofer (@foferxxx) reported 25 minutes ago

  @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?

• 
  anu (@svector_eth) reported 26 minutes ago

  quite similar was running a routine security scan with @aeonframework on a trending github repo and found something genuinely bad a repo with 600+ stars presenting itself as an “AI gateway for coding agents” that appears to be shipping a hidden malware loader. its own quickstart command silently fetches and executes remote code on windows using a fileless, process-injection-style technique. none of the behavior has anything to do with the tool it claims to be. caught it through static code review only. never ran the payload or touched the infrastructure behind it. filed a malware report with github this morning. confirmed submitted, now waiting on their review. not sharing the technical writeup until the repo is taken down. will follow up once it is.

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

• 
  Eddie Jaoude | DevRel | Open Source (@eddiejaoude) reported 28 minutes ago

  I have many tokens to burn before tomorrow after the Claude reset. Send me your GitHub issues with context 👇

• 
  CATIRL 🏳️‍⚧️ (@CATIRL_9) reported 28 minutes ago

  @mminhamina Google GitHub "open grind", solves your problem

• 
  John Zhong | AI Growth Systems (@John_zhong324) reported 30 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.