An open-source database of companies who have been affected (or not) by the collapse of SVB.
hey folks. I've created an open-source database of companies affected (or not) by the #SVBCollapse https://t.co/6M3yefx7cc— geoff (open to jobs)🦩 (@GeoffreyHuntley) March 12, 2023
Contributions are welcome and encouraged. See citations/* for a listing of citations. Please attach a citation (either link or screenshot) when PRing
Contribute to the project via https://github.com/ghuntley/affectedbysvbornot.com.
Below you will find companies who have publically (or privately with citations) revealed that they have been affected by the collapse of SVB. There are tens of thousands to hundreds(?) of thousands of companies affected as revealed by this Google Dork.
The query pulls back documents containing an #SVB routing or swift number + an @SVB_Financial account number.
The name of the business tied to the SVB account number is usually within 100 characters of the account number and typically labeled “beneficiary” or “for credit of” (or some close variation on those themes).
In edge cases where a company name is not found near the account number, the account holder is often the source/author of the document, e.g.,
Google only returns 1000 results for any given query - so retrieving the entire results set would require narrowing each query’s scope and then iterating through the targets at a finer granularity.
For example, the current query looks for account numbers matching 33**. Replacing that with 33NN**, where NN is 01-99 would let you iterate through ranges of account numbers (3301**, 3302**, and so on…).
Other approaches include geographically scoping the queries by adding “AND NJ” to queries (and iterating through each two-byte state code) or tacking on partial zip codes, etc…
|Company Name||Amount of Employees||Website URL||Official Statement||SEC Filing||Citations||Exposure Level|
|Camp||unknown||https://camp.com||If you are in need of Toys, Gifts, etc. I would really appreciate you shopping from http://Camp.com today. We will give ya a nice discount if you need/want it. or pay full price - Ben Kaufman||n/a||BANKRUN promotion code.||unknown|
|Chargebee||1000||https://www.chargebee.com/||n/a||n/a||“Chargebee requests that you do not send payments to our SVB account” email sent to customers||unknown|
|Circle||unknown||https://circle.com||Silicon Valley Bank is one of six banking partners Circle uses for managing the ~25% portion of USDC reserves held in cash. - Twitter Link||n/a||Official Twitter statement||unknown|
|CostPlusDrugs||unknown||https://CostsPlusDrugs.com||n/a||CostsPlus Drugs.com deals with SVB. So we had, I think we had 3.1 million in there||unknown|
|Etsy||2790||https://etsy.com||n/a||Etsy sellers reporting payouts have not been processed with screenshot of an email from Esty.||unknown|
|Fastly||1112||https://fastly.com||n/a||n/a||An email from account managers sent to Fastlys customers. Our payment instructions have changed. Effective immediately, please cease sending payments to our Silicon Valley Bank (SVB) Account and direct all payments to the following account at JP Morgan Chase.||unknown|
|Juniper Networks||10901||https://www.juniper.net/||Juniper loss as of result of SVB receivership is immaterial - Reuters||n/a||JUNIPER NETWORKS INC - MAINTAINS OPERATING ACCOUNTS AT SVB WITH MINIMAL CASH BALANCE OF LESS THAN 1% OF TOTAL CASH, CASH EQUIVALENTS AND INVESTMENTS||unknown|
|KeyboardIO||15||https://shop.keyboard.io/||We’re fine, but, uh, our bank failed this morning.||n/a||A tweet from the company account||unknown|
|Rippling||1700||https://www.rippling.com/||n/a||SF payroll firm Rippling has to delay payouts after Silicon Valley Bank collapse||unknown|
|Roblox||2100||https://www.roblox.com/||approximately 5% of its $3 billion cash and securities balance was held at SVB as of Feb. 28, 2023||https://d18rn0p25nwr6d.cloudfront.net/CIK-0001315098/05c0fe85-052c-4786-980c-7bdf467f8258.pdf||unknown|
|Rocket Lab USA||1300||https://www.rocketlabusa.com/||Rocket Lab USA said it had $38 million in cash, or 7.9% of its total cash as of Dec. 31, 2022, with SVB||https://d18rn0p25nwr6d.cloudfront.net/CIK-0001819994/b644cf38-1413-43b7-bdb7-a0292b3ac1b3.pdf||unknown|
|Roku||3000||https://www.roku.com/||At this time, the Company does not know to what extent the Company will be able to recover its cash on deposit at SVB||https://www.sec.gov/ix?doc=/Archives/edgar/data/1428439/000142843923000010/wk-20230310.htm||unknown|
|Strongsuit||unknown||https://www.strongsuit.co/||The financial future of my company, team and family are at risk w/ the collapse of SVB||n/a||A tweet from the company founder||unknown|
|SoFi||unknown||https://www.sofi.com/||We have no assets with SVB. Our only exposure is a very small lending facility that is provided to us for less than $40m which is unaffected by the FDIC’s receivership of Silicon Valley Bank. Your money is safe with SoFi.||https://twitter.com/SoFi/status/1634269534604472321||unknown|
|Perplexity AI||unknown||https://www.perplexity.ai/||We use SVB for @perplexity_ai and were impacted by the recent events. Thanks to @natfriedman for stepping forward to help us with emergency funding on real short notice. Fortunate to be working with him!||Tweet by the founder.||unknown|
|Vimeo||1300||https://www.vimeo.com/||The company believes it does not have exposure to any liquidity concern at SVB. The Company has a well structured and diverse set of banking partners with no bank holding over 25% of its total cash||https://investors.vimeo.com/static-files/e2ef741c-1688-48a3-8b4e-1c12e87d2a91||unknown|
|Company Name||Official Statement|
|fuboTV||We do not hold any deposit or have any investments at SVB|
|Gusto||We do not use SVB|
|Groundfloor||Groundfloor’s primary banking relationship is with Truist|
|Qovery||It’s a sad day for the startup ecosystem! While there is no direct impact on Qovery|
|Company Name||Official Statement||url|
|Qovery||Offering to delay payments for March and April to any Qovery customers whom the SVB crash may impact.||https://www.qovery.com/blog/qovery-pledges-to-help-businesses-impacted-by-svb-crash|
This website was created and is maintained by Geoffrey Huntley. Contributions are welcome!