Cause: Rivet is winding down service through its customer portal. *As of today, the portal is no longer available to new customers.
Conditions: For a time, centralization was a practical bridge. It allowed us to ship, to learn, and to serve real users in a real environment. But bridges are not destinations. They are temporary structures designed to be crossed, not occupied. Stepping away from the portal is therefore not an abandonment of users. It is a refusal to freeze in a form that cannot scale without recreating the very dynamics we are trying to dissolve.Stepping aside from the portal is how that intention becomes real.
Cause: Application of system updates to Geth 1.10.8
Conditions: All systems remained available throughout the duration.
Note: Rivet uses a streaming replication architecture with master servers responsible for maintaining consensus, and replica servers handling client requests. Given the critical nature of the Geth v1.10.8 security update, we applied the update to our masters as quickly as possible, but are continuing to test our replicas for performance and stability. For the time being, calls to web3_clientVersion will still indicate that we are running v1.10.6-stable, but these requests are handled by our replicas. The masters which validate blocks and transactions have the critical security update, and the replicas will be updated once they have been through our quality assurance processes.
were
Maintenance
Rivet.cloud provides next generation Web3 infrastructure.
Back to top • Subscribe via RSS
2026 © Open Relay LLC
