Independent profile — not affiliated with CoreWeave
CoreWeave
CoreWeave, Inc. (Nasdaq: CRWV), headquartered in Livingston, New Jersey, sells GPU and CPU cloud infrastructure, storage, networking and software to businesses and developers; its customer terms, billing rules, SLA credit deadlines, suspension rights and support and privacy contacts are quoted from its own pages below. The lawsuits identified in its SEC filing and the court dockets checked on September 30, 2026 are a January 2026 securities class action in the District of New Jersey and four related shareholder derivative actions, which are allegations that CoreWeave says are without merit. USAComplaints has 0 complaints about CoreWeave, its Trustpilot profile was unclaimed with no reviews, and the four BBB searches run on September 30, 2026 returned no business profile named CoreWeave.
Independent Sources
Shown for context — not merged with USAComplaints' own numbers.
Contacts & Login
- Official website: https://www.coreweave.com/
- Customer support and billing questions: [email protected]
- Contact support (Cloud Console Help portal - CoreWeave's recommended route): https://docs.coreweave.com/support/contact
- Corporate office (registrant telephone number on the SEC Form 10-K cover page; not a customer-suppor: (973) 270-9737
- Cloud Console login: https://console.coreweave.com/login
- Service status page: https://status.coreweave.com/
- Privacy requests: [email protected]
- Privacy requests (number given in the Privacy Policy): 1-888-349-5038
- Security vulnerability reports: [email protected]
- Status page 'Report Issue' link: [email protected]
Locations
| Type | Address |
|---|---|
| Headquarters | 290 W. Mt. Pleasant Avenue, Suite 4100 Livingston NJ 07039 |
CoreWeave customer? Where billing, SLA credits, suspension and support are handled
Key deadlines and rules in CoreWeave's published terms (details, exceptions and quotations follow below; a signed order form or master agreement may differ):
- Compute outage credit (main Terms of Service): notify technical support within 10 days of becoming eligible, with server log files; credits are capped at 50% of the month's amount due.
- AI Object Storage credit (its own SLA): request to [email protected] within 30 days, with the availability zone and request logs; the top tier is 100% of the affected monthly bill for that availability zone (uptime below 94.999%); credits are not a cash refund.
- Invoices under $20,000: charged automatically to the card on file. $20,000 or more: paid by ACH or wire, payable on Net 15 days.
- Late fees and offsets: unpaid amounts carry a finance charge of 1.5% per month (or the highest lawful rate, if lower), and amounts due may not be withheld or offset.
CoreWeave sells cloud infrastructure mainly to businesses and developers. Two CoreWeave documents matter for disputes. The Terms of Service at docs.coreweave.com/policies/terms-of-service is the page the coreweave.com footer links to (the footer links it as "Terms of Service"); it is displayed with "Last modified: June 30, 2022," calls itself "a binding contract between CoreWeave and the Customer" and "a binding legal contract; the Customer's acceptance of it is required to use CoreWeave Services," and incorporates a Data Processing Agreement, an Acceptable Use Policy and the Privacy Policy. A separate Terms of Use at docs.coreweave.com/policies/terms-of-service/terms-of-use ("last updated on July 8, 2024") governs use of CoreWeave's websites (CoreWeave.com and Cloud.CoreWeave.com and other CoreWeave-operated sites); it says that use of CoreWeave's products and services through the sites "is governed by our Terms of Service" and that "In the event of a conflict between these Terms and our Terms of Service, the Terms of Service shall govern." The footer of coreweave.com does not link the Terms of Use as of September 30, 2026. Which document applies to a particular dispute is a legal question this page does not decide. Larger customers may also sign order forms or master services agreements (CoreWeave's Form 10-K refers to such agreements with its largest customers); those contracts are not public and can differ from the web terms, so check your own signed paper first.
- Billing. The Terms say CoreWeave services other than prepaid rendering are "billed monthly in arrears based on the Customer's prior month's usage," and, unless agreed otherwise, fees "are due and payable upon receipt of invoice." Invoices under $20,000 are "automatically charged to the Customer's credit card"; invoices of $20,000 or more "must be paid by bank transfer (ACH or Wire)" and are "payable on Net 15 days." Unpaid or past-due fees "are subject to a finance charge of 1.5% of the unpaid balance per month (or the highest rate permitted by law, whichever is lower)," and amounts due "shall not be withheld or offset by you against amounts due to you for any reason." Fees for Reserved Compute Instances or Bulk Credits are due under the Order Form. CoreWeave's changelog lists a Billing entry dated April 21, 2026 announcing a Billing insights page in the Cloud Console (the linked release-note page is itself titled "April 20, 2026 - Billing insights"); the release note says the page shows billable usage, measured usage and exclusions and that access requires the Billing Viewer IAM role. A changelog entry dated September 11, 2026 says the FOCUS Billing Export API is "now available in public preview" and pulls hourly CoreWeave usage "in FOCUS 1.2 JSON or CSV format"; the release note adds that it returns "usage quantities only" (cost fields, project-level attribution and per-resource rows are not included) and needs an API access token and FOCUS export enabled for the organization.
- Disputing an invoice. CoreWeave's Billing documentation says "If you need help with billing, you can contact the support team at [email protected]." In the Terms of Service, Billing and Contact support pages opened on September 30, 2026, no separate invoice-objection procedure, escalation path, response deadline or refund policy for disputed usage charges was identified (the only refund language found in the Terms concerns a cancelled Reserved Compute or Bulk Credits Order Form, below). Because the Terms bar withholding or offsetting, a customer disputing a charge may want to raise it in writing with support, keep the invoice and a usage export (Billing insights, and the FOCUS export API while it is in public preview, which per its release note returns usage quantities only), and check the signed order form or master agreement, which may set its own dispute terms.
- Outage credits (SLO) - deadline 10 days. The main Terms set a monthly uptime objective of 99.9% or more for instances in multiple regions and 99% or more for instances in a single region. For multi-region instances the credit is 10% of the affected monthly bill at 99% to 99.9% uptime, 25% at 95% to 98.999% and 50% below 94.999%; for a single region it is 10% at 95% to 99%, 25% at 90% to 94.999% and 50% below 89.999%. To receive a credit you "must notify CoreWeave technical support within ten (10) days from the time Customer becomes eligible" and provide "server log files showing loss of external connectivity errors and the date and time those errors occurred"; otherwise the right to the credit is forfeited. The SLO section of the Terms does not mention the status page as evidence; it names server log files. Credits are capped at 50% of the amount due for the month, are applied "to future use" within sixty days of the request, and the Terms call this "Customer's sole and exclusive remedy" for missing the SLO. If a dispute arises, the Terms say CoreWeave "will make a determination in good faith based on its system logs, monitoring reports, configuration records, and other available information," which it will make available for auditing by the customer at the customer's request. Exclusions include pre-general-availability features, causes outside CoreWeave's reasonable control, problems from customer software and "downtime caused by in-advance communicated maintenance." The Terms also state that no credits are available for SLO failures in the EWR1 data center as of August 1, 2022.
- Other services have their own terms, and different deadlines. CoreWeave AI Object Storage (the cwobject.com endpoint) is governed by its own Service Level Agreement, which says it "solely governs service levels for such service, and not the SLO" in the main Terms: 99.9% target; credits of 10%, 25% or 100% of the affected monthly bill; a request to [email protected] within thirty (30) days with the availability zone and "request logs documenting the dates and times of each Error"; and credits do not "entitle you to any refund or other payment." Spot Services terms say the SLO in the main Terms "does not apply to the Spot Services" and that CoreWeave may remove access to Spot node pools under its preemption process. The ARENA evaluation program terms say a customer "is not entitled to any support or service level related credits." Check which product and which contract your usage falls under before counting days.
- Suspension and termination. Two provisions in the Terms of Service are worded differently. The broader one says CoreWeave "reserves the right to deactivate, terminate, prevent access to, disable services for, and/or suspend or delete a Customer's account or access to any CoreWeave Services at any time for nonpayment, late payment (if applicable), or failure to maintain at all times current, valid, complete and accurate Payment Methods." The narrower one says that if fees are past due, "we may suspend your API access after we provide you written notice of late payment." The Acceptable Use Policy ("Last updated September 17, 2021") lets CoreWeave suspend or terminate use if it determines in good faith that the policy was violated, "even if a violation is committed unintentionally." If CoreWeave cancels a Reserved Compute or Bulk Credits Order Form for a material violation, the Terms give a refund of the prorated balance, offset by on-demand rates for usage to the cancellation date. In the Terms of Service, Acceptable Use Policy, Billing and Contact support pages opened on September 30, 2026, no published appeal, reinstatement, emergency-escalation or data-export procedure for a suspended account was identified; [email protected] and the Cloud Console Help button are the channels CoreWeave documents for problems generally.
- Maintenance and status. CoreWeave's Maintenance Policy says it may perform unplanned maintenance "at any time, in its sole discretion, without notice," gives at least 24 hours' notice for planned maintenance it deems "critical," and states "It is a user's responsibility to ensure they are subscribed to the status notifications relevant to their CoreWeave Cloud deployments." Status is posted at status.coreweave.com, which offers email, RSS, Slack, Microsoft Teams and webhook subscriptions.
- Closing an account and your data. Two different things are covered by different documents. Customer Data (data you process on CoreWeave) falls under the Terms of Service: customers can delete it during the term, and after an account is closed or an Order Form expires the Terms say CoreWeave will, "after a recovery period of up to thirty (30) days," delete Customer Data on instruction "within a maximum period of one hundred eighty (180) days," and that the customer "is responsible for exporting" data it wants to keep before then. Personal data that CoreWeave holds about you as a website visitor or account contact falls under the Privacy Policy (last updated February 24, 2026): requests go to [email protected] or 1-888-349-5038, the policy says "We will verify your identity before responding," and it says CoreWeave cannot respond "if we cannot verify the identity or authority to make the request." The Privacy Policy also says it does not apply where CoreWeave acts solely as a processor for a customer, and that an individual whose data sits in a customer's account "should direct their query to the third party or CoreWeave customer" (the data controller).
- Contacting CoreWeave. CoreWeave's support page says "The recommended way to request help from our support team is through the help portal on the Cloud Console" (the Help button in the Cloud Console; "Client Support Report" for general requests, "Quota Increase" for quotas) and, "If you cannot use the Cloud Console contact form," [email protected]; it asks for priority (Low, Medium, High or Urgent), the organization administrator's email, the organization name and the namespace. Personal-data requests go to [email protected] and vulnerabilities go to [email protected]. Keep your invoices, usage exports, log excerpts and ticket numbers, and send credit requests in writing inside the deadline in your contract.
- Governing law and dispute clauses. The Terms of Service are governed by New York law, with the parties submitting to the exclusive jurisdiction of state and federal courts in New York County, New York for "any lawsuit or court proceeding permitted under the TOS," and they say CoreWeave may amend them "without notice to Customer." The separate Terms of Use (July 8, 2024) contain different dispute language for the websites: "At Company's sole discretion, it may require you to submit any disputes arising from these Terms or use of the CoreWeave Sites ... to final and binding arbitration under the Rules of Arbitration of the American Arbitration Association applying New York law"; a clause (in capitals in the original) that disputes "WILL BE RESOLVED INDIVIDUALLY, WITHOUT RESORT TO ANY FORM OF CLASS ACTION"; and a clause that claims must be commenced within one (1) year after the cause of action accrues. The New York-courts clause in the Terms of Service is therefore not the only dispute provision CoreWeave publishes.
If you arrived here because of investor notices rather than a service problem, see the litigation section below.
Company background
CoreWeave, Inc. is a Delaware corporation with principal executive offices at 290 W. Mt. Pleasant Ave., Suite 4100, Livingston, New Jersey (Form 10-K cover page; telephone (973) 270-9737). Its Class A common stock trades on the Nasdaq Stock Market under the symbol CRWV. According to its Form 10-K, the company "was originally formed as a Delaware limited liability company in 2017 and then converted to a Delaware corporation in 2018," "was founded in September 2017" and "launched our CoreWeave Cloud Platform in 2020," and completed its initial public offering in March 2025. SEC EDGAR also lists an earlier company name, Atlantic Crypto Corp (2019). The 10-K adds that before 2022 the company "had limited revenue, most of which was derived from our past crypto mining offerings, which were discontinued."
CoreWeave describes itself as "The Essential Cloud for AI" and its platform as combining GPU and CPU compute, networking, storage, managed Kubernetes and software; its 10-K lists Weights & Biases, Inc., OpenPipe Inc., Marimo Inc. and Monolith AI Limited among its acquisitions. Company-reported figures in the 10-K for 2025 include revenue of $5.1 billion, 2,189 employees at December 31, 2025, and roughly 67% of revenue from its top customer, Microsoft. The 10-K says it leases data center space in the United States, the United Kingdom, Spain, Sweden and Norway, and that the multi-class structure of its common stock concentrates voting power with its Co-Founders. Its coreweave.com About page lists Mike Intrator as Chief Executive Officer and Nitin Agrawal as Chief Financial Officer.
Recent company-reported items: according to its Form 8-K filed September 22, 2026, CoreWeave on that date "completed its previously announced upsized private offering of $4.2 billion aggregate principal amount of its 2.875% Convertible Senior Notes due 2033", including $500 million of notes from the initial purchasers' option exercised in full; these are financing terms for noteholders, not customer terms. Its Form 10-K says that "committed contracts," which it describes as take-or-pay, accounted for "over 98%" of its 2025 revenue, that customers generally buy through multi-year committed contracts, and that it had $60.7 billion of remaining performance obligations at December 31, 2025. Both its 10-K and its Form 10-Q for the quarter ended June 30, 2026 state that "all of the GPUs used in our infrastructure today are NVIDIA GPUs" because of obligations in current customer contracts (a supplier-concentration disclosure). In a press release dated August 4, 2026, CoreWeave announced its first Asia-Pacific expansion, three facilities in Indonesia totaling 360 megawatts of contracted IT power that it said are "expected to come online in 2028" (announced plans, not operating capacity).
On security, the 10-K states "To date, we have not experienced any cybersecurity incidents that have materially affected our business strategy, results of operations, or financial condition." CoreWeave's Trust Center says compliance reports and audit documentation are provided on request, under NDA, through the account team; this page has not reviewed those documents. CoreWeave's Vulnerability Disclosure Policy directs reports to [email protected].
Public review and complaint profiles (USAComplaints, Trustpilot, BBB), and CoreWeave's own service-status data
Sources that track complaints or reviews are reported separately and are not combined into one figure. Counts below are as displayed on the page and date named; they can change.
- USAComplaints: 0 complaints submitted about CoreWeave on this site as of September 30, 2026.
- Trustpilot: the profile at trustpilot.com/review/www.coreweave.com was labelled "Unclaimed profile" and displayed "0 reviews" in the last 12 months and "This company hasn't received any reviews yet" when opened on September 30, 2026.
- BBB: four searches on bbb.org were run on September 30, 2026 (result-page addresses are listed in this page's sources). "CoreWeave" with location "Livingston, NJ" returned "No results"; "CoreWeave, Inc." returned no results; "CoreWeave" with no location returned three differently named businesses (CareWave Group LLC, Corewave Designs, Coreware, LLC) and no CoreWeave; "Core Weave" returned 562 loosely matched results, and the first page of 15 contained no CoreWeave entry (later pages were not reviewed). No BBB business profile named CoreWeave was found in those four searches; the result is limited to those queries and that date.
- Service-status data, not complaints - CoreWeave's own status page (status.coreweave.com, opened September 30, 2026) displayed "5 Incidents Last 30 Days," "20 Maintenances Last 30 Days" and "2 Upcoming Maintenances." These are rolling, company-published dashboard counts on a page CoreWeave runs (the page footer says "Powered by Status.io"); they are not complaint totals and were not independently verified, and this page did not review the individual incident write-ups.
The absence of public reviews or complaints on these sites is not information about customers' experiences, good or bad. Customers with a dispute over billing, credits or suspension can use the support channels listed above and, for contract disputes, the dispute provisions in the documents that apply to them (see the terms section above).
Securities class action and shareholder derivative suits (investor claims)
The lawsuits identified in CoreWeave's SEC filing (Form 10-Q for the quarter ended June 30, 2026, Note 9) and in the court dockets checked on September 30, 2026 are investor suits: a securities class action and shareholder derivative actions. They are not customer suits over service, billing or credits, and they are allegations, not findings. This is a list of what those sources showed, not a statement that no other proceeding exists; the 10-Q itself says the company "may be subject to various proceedings, lawsuits, disputes, or claims in the ordinary course of business."
Securities class action. Masaitis v. CoreWeave, Inc., No. 2:26-cv-00355 (D.N.J.), was filed on January 12, 2026 against CoreWeave, Michael Intrator, Nitin Agrawal and Brannin McBee. The complaint seeks to represent purchasers of CoreWeave securities between March 28, 2025 and December 15, 2025 and asserts claims under Sections 10(b) and 20(a) of the Securities Exchange Act of 1934. It alleges the defendants overstated CoreWeave's ability to meet customer demand and understated the risk from reliance on a single third-party data center supplier, and it cites CoreWeave's November 10, 2025 lowered revenue guidance, which the company attributed to "delays related to a third-party data center developer who is behind schedule." A February 13, 2026 stipulated order suspended defendants' time to respond until a lead plaintiff and lead counsel are appointed, with a schedule for an amended complaint to follow. Several competing lead-plaintiff motions were filed starting March 13, 2026, and some were later withdrawn. No lead-plaintiff appointment order was visible in the accessible CourtListener/RECAP entries through September 29, 2026 (51 entries; the page itself says its data "may not be up to date"). Because RECAP can be incomplete, and the text of two September 29, 2026 notices was not available, the court's official docket on PACER is the definitive record of the case's current status.
Derivative actions (four filed). CoreWeave's Form 10-Q reports that two stockholder derivative actions were filed in the District of New Jersey on February 10, 2026 and a third on March 5, 2026 (together the "New Jersey Derivative Actions"), and that another was filed in the District of Delaware on May 12, 2026. The dockets identify them as Smith v. Intrator, No. 2:26-cv-01305 (D.N.J., filed February 10, 2026), Roy v. Intrator, No. 2:26-cv-01345 (D.N.J., filed February 10, 2026), Erez v. Intrator, No. 2:26-cv-02321 (D.N.J., filed March 5, 2026) and Sussman v. Intrator, No. 1:26-cv-00553 (D. Del., filed May 12, 2026). The derivative claims are brought on behalf of the company against current and former officers and directors and, per the 10-Q, "seek unspecified damages based on substantially the same allegations as the Securities Action."
Consolidation and stay - the steps in order. The 10-Q and the dockets record different steps of the derivative-action consolidation, and this page does not treat them as inconsistent. March 11, 2026: Smith entry 4 is a "STIPULATION AND ORDER CONSOLIDATING CASES AND APPOINTING CO-LEAD COUNSEL" providing that papers in the Consolidated Derivative Action are maintained in one file under No. 2:26-cv-01305; the Roy docket shows a stipulation and order the same day and the Roy case terminated. April 1, 2026: Smith entry 9 is an "ORDER OF FILING OF RELATED CASE" stating that, pursuant to the Consolidation Order, co-lead counsel submits that the Erez action be consolidated with the Smith action; the 10-Q gives this date: "On April 1, 2026, the U.S. District Court for the District of New Jersey consolidated the New Jersey Derivative Actions under the name In Re CoreWeave, Inc. S'holder Deriv. Litig." May 15, 2026: a "NOTICE AND ORDER OF FILING OF RELATED CASE" (Smith entry 18 and Erez entry 4) directs that Erez be consolidated with No. 2:26-cv-01305 under the Consolidation Order, and the Erez case was terminated on its own docket that day. May 21, 2026: Smith entry 20 is a "STIPULATION AND ORDER regarding stay of derivative action," and the 10-Q says "on May 21, 2026, the court approved a stay of further proceedings until final resolution of the Securities Action." The Sussman docket (Delaware) shows entries through May 20, 2026 (complaint, consent forms and assignment to a judge) in the copies checked.
Company position. The 10-Q states that CoreWeave "believes that the claims made in the Securities Action and the Derivative Actions are without merit and intends to defend itself vigorously," that any possible loss or range of loss "cannot be reasonably estimated at this time," and that it had not accrued any material potential loss as of June 30, 2026. Its Legal Proceedings item says it is "not presently a party to any litigation the outcome of which, we believe, if determined adversely to us, would individually or taken together have a material adverse effect."
Is CoreWeave Legitimate?
CoreWeave, Inc. is registered with the SEC (CIK 0001769628), files annual and quarterly reports, and its Class A stock trades on the Nasdaq Stock Market as CRWV; the contracting party named in its Spot Services and ARENA terms is "CoreWeave, Inc., a Delaware corporation." Its published customer terms, privacy policy, acceptable use policy, maintenance policy and status page are quoted above, and support, billing, privacy and security contacts are listed on its own documentation pages. The legal proceedings described in Note 9 of its June 30, 2026 Form 10-Q are the securities class action and shareholder derivative suits summarized above; no government enforcement action was identified in the sources checked on September 30, 2026 (its Form 10-K and 10-Q, the CourtListener search, and one web search), and that check did not cover every federal or state agency database. This page assigns CoreWeave no rating, score or verdict of its own; the terms, contacts and litigation status are reported so readers can weigh them for themselves.
Court & Public Records
| Case | Authority | Dates | Type | Outcome | Source |
|---|---|---|---|---|---|
| Masaitis v. CoreWeave, Inc., et al. Docket No. 2:26-cv-00355 | U.S. District Court, D. New Jersey | Filed | Filed — no final outcome recorded A putative securities class action (an allegation, not a finding) on behalf of purchasers of CoreWeave securities between March 28, 2025 and December 15, 2025, asserting Sections 10(b) and 20(a) claims against CoreWeave, Michael Intrator, Nitin Agrawal and Brannin McBee. A stipulated order entered February 13, 2026 suspended defendants' time to respond pending appointment of a lead plaintiff and lead counsel. Competing lead-plaintiff motions were filed beginning March 13, 2026. No lead-plaintiff appointment order was visible in the accessible CourtListener/RECAP entries through September 29, 2026; because RECAP may be incomplete and two September 29 notices were unavailable, PACER is the definitive record. CoreWeave says the claims are without merit and that it intends to defend itself vigorously. | Source | |
| Smith v. Intrator, et al. (lead derivative action; papers maintained under this number) Docket No. 2:26-cv-01305 | U.S. District Court, D. New Jersey | Filed | Filed — no final outcome recorded Stockholder derivative action brought on behalf of CoreWeave against certain current and former officers and directors, with CoreWeave as nominal defendant, based on substantially the same allegations as the securities class action (an allegation, not a finding). CoreWeave says the claims are without merit. Per the docket: a March 11, 2026 stipulation and order consolidating cases and appointing co-lead counsel (entry 4); an April 1, 2026 order of filing of related case as to Erez (entry 9); a May 15, 2026 notice and order directing that Erez be consolidated (entry 18); and a May 21, 2026 stipulation and order regarding stay of the derivative action (entry 20). The 10-Q states that the New Jersey derivative actions were consolidated on April 1, 2026 as In Re CoreWeave, Inc. S'holder Deriv. Litig. and that on May 21, 2026 the court approved a stay until final resolution of the Securities Action. | Source | |
| Roy v. Intrator, et al. (derivative) Docket No. 2:26-cv-01345 | U.S. District Court, D. New Jersey | Filed | Filed — no final outcome recorded Stockholder derivative action brought on behalf of CoreWeave against certain current and former officers and directors, with CoreWeave as nominal defendant, based on substantially the same allegations as the securities class action (an allegation, not a finding). CoreWeave says the claims are without merit. The Roy docket shows a stipulation and order on March 11, 2026 and the civil case terminated that day; the Smith docket's March 11, 2026 order consolidates cases and places papers under No. 2:26-cv-01305. | Source | |
| Erez v. Intrator, et al. (derivative) Docket No. 2:26-cv-02321 | U.S. District Court, D. New Jersey | Filed | Filed — no final outcome recorded Stockholder derivative action brought on behalf of CoreWeave against certain current and former officers and directors, with CoreWeave as nominal defendant, based on substantially the same allegations as the securities class action (an allegation, not a finding). CoreWeave says the claims are without merit. The Erez docket shows a May 15, 2026 notice and order of filing of related case directing that Erez be consolidated with No. 2:26-cv-01305, and the case terminated that day. The Smith docket also shows an April 1, 2026 related-case order naming Erez. | Source | |
| Sussman v. Intrator, et al. (derivative) Docket No. 1:26-cv-00553 | U.S. District Court, D. Delaware | Filed | Filed — no final outcome recorded Stockholder derivative action brought on behalf of CoreWeave against certain current and former officers and directors, with CoreWeave as nominal defendant, based on substantially the same allegations as the securities class action (an allegation, not a finding). CoreWeave says the claims are without merit. The Delaware docket copies checked (CourtListener last known filing May 20, 2026; Justia last retrieved May 20, 2026) show the complaint, consent forms, and assignment to Judge Colm F. Connolly; later activity, if any, was not visible. | Source |
Frequently Asked Questions
Is CoreWeave a real, publicly traded company?
CoreWeave, Inc. is a Delaware corporation registered with the SEC under CIK 0001769628, with principal executive offices in Livingston, New Jersey. Its Class A common stock trades on the Nasdaq Stock Market under the symbol CRWV, and its Form 10-K says it completed its initial public offering in March 2025. Its annual and quarterly reports are on SEC EDGAR.
How do I contact CoreWeave support?
CoreWeave's support page says the recommended route is the Help button in the Cloud Console (log in at console.coreweave.com), which offers a "Client Support Report" form for general requests and a "Quota Increase" form. If you cannot use the console, it says to email [email protected] with your contact information, an issue priority (Low, Medium, High or Urgent), the organization administrator's email, the organization name and the namespace. The status page's "Report Issue" link uses [email protected]. The (973) 270-9737 number in the SEC filings is listed there as the company's registrant telephone number, not as a customer-support line.
How do I get a credit for a CoreWeave outage?
The deadline depends on the product. Under the main Terms of Service (compute), you must notify CoreWeave technical support within ten (10) days of becoming eligible and provide server log files showing loss of external connectivity errors with dates and times, or the credit is forfeited; credits run from 10% to 50% of the affected monthly bill, are capped at 50% of the month's amount due, are applied to future use within sixty days of the request, and are described as the customer's "sole and exclusive remedy." AI Object Storage has its own SLA with a thirty (30) day window and request logs; Spot and ARENA services are excluded. The Terms name server logs, not the status page, as the evidence. A signed order form or master agreement may set different terms.
How does CoreWeave bill, and how do I dispute a charge?
The Terms say most services are billed monthly in arrears for the prior month's usage; invoices under $20,000 are charged automatically to the card on file and invoices of $20,000 or more are paid by ACH or wire on Net 15 terms. Past-due fees are subject to a finance charge of 1.5% of the unpaid balance per month (or the highest lawful rate, if lower), amounts due "shall not be withheld or offset," and CoreWeave may suspend an account for nonpayment or late payment and may suspend API access after written notice of late payment. For billing questions the docs point to [email protected]; no separate invoice-dispute procedure or deadline was identified in the Terms, Billing and Contact support pages opened on September 30, 2026.
Can CoreWeave suspend or terminate my account?
The Terms reserve CoreWeave's right to suspend, disable or delete an account or access "at any time for nonpayment, late payment (if applicable), or failure to maintain" valid payment methods; a narrower sentence says it may suspend API access after written notice of late payment. The Acceptable Use Policy allows it to suspend or terminate use if it determines in good faith that the policy was violated, even if unintentionally, and the ARENA evaluation terms let CoreWeave terminate "for cause or convenience at any time." No published appeal, reinstatement or data-export procedure for suspended accounts was identified in the pages opened on September 30, 2026; contact support in writing and check any signed order form, which may add notice or cure rights.
What happens to my data if I close my CoreWeave account?
For Customer Data, the Terms say customers can delete it during the term, and that after account closure or expiry of an Order Form, CoreWeave will, following a recovery period of up to thirty days, delete Customer Data on instruction within a maximum of 180 days; the customer is responsible for exporting any data it wants to keep before the term ends or the account is closed. Personal-data requests about information CoreWeave holds as a controller (for example website or account-contact data) are handled separately under the Privacy Policy.
Is there a lawsuit against CoreWeave?
The lawsuits identified in CoreWeave's June 30, 2026 Form 10-Q and the court dockets checked on September 30, 2026 are investor claims, not customer complaints: a putative securities class action, Masaitis v. CoreWeave, Inc., No. 2:26-cv-00355 (D.N.J.), and four shareholder derivative actions based on substantially the same allegations. CoreWeave says the claims are without merit and that it intends to defend itself vigorously. Dates, procedural status and the limits of the public dockets are set out in the litigation section of this page.
How do I make a privacy request to CoreWeave?
CoreWeave's Privacy Policy (last updated February 24, 2026) says to email [email protected] or call 1-888-349-5038 with your name, email address, phone number and address and the type of request, and that CoreWeave will verify identity before responding and may request additional information. It applies to personal data CoreWeave processes as a controller; where CoreWeave processes data on behalf of a customer, the policy says requests should go to that customer as the data controller. It also says it honors Global Privacy Control signals where required by law. Deletion of Customer Data under the service contract is a separate process (see the account-closure answer).
How do I report a security vulnerability to CoreWeave?
CoreWeave's Vulnerability Disclosure Policy asks reporters to email [email protected] with as much detail as possible and offers safe harbor for good-faith research under that policy. Its Acceptable Use Policy separately says customers may not probe or test CoreWeave systems for vulnerabilities without prior written consent.