What happened
Start with the official announcement. On July 1, 2026, Venice published that it raised a $65M Series A led by Dragonfly at a $1B valuation (its first outside capital) with backers including Coinbase Ventures, F-Prime, and North Island Ventures. The company disclosed scale on the order of ~3.5M users and ~1.3T tokens processed per month. That blog post is the source of truth for the raise; social posts afterward are progress checks, not the announcement itself.
On July 7, six days later, Venice registered ARIN organization record VENIC-4. That is network-infrastructure prep after the funding announcement, not before it. The angle is how fast ops moved once capital was public.
On July 24, co-founder and CTO Jesse Proudman posted a checklist (“Series A: secured. GPUs: on the way. Data centers: deploying…”) alongside hiring for senior network infrastructure. Treat that as a progress update, not a second Series A announcement.
The Senior Network Infrastructure Engineer posting confirms the scope: routing, peering, firewalls, VLANs, VPNs, and load balancing across cloud and on-premises environments. Peering is BGP work between autonomous networks, which is exactly what AS402818 is for. The same posting says Venice is “moving into scaling mode” and wants candidates willing to travel as needed, consistent with physical data-center build-outs.
On July 27, Autonomous System AS402818 (VENICE-NET-1) was registered with ARIN. Jesse posted “It’s happening…” with the public whois link.
An ASN is how a network identifies itself and peers on the public internet. Publishing AS402818 under Venice is Venice saying this path is first-party infrastructure.
Venice's own chatbot account on X (@venice_mind, powered by @AskVenice) framed it the same way: Venice's “own slice of the internet's backbone,” with fewer intermediaries handling user data, better control over latency, and insulation from cloud provider censorship or rate limits.
