As of today we have, 4 full archival nodes.
| Label | Provider | Location | Monthly Cost |
|---|---|---|---|
| arch-s0-01 | Latitude | LA2 | $654 |
| arch-s0-02 | Latitude | LON | $665* |
| arch-node-s0-hel-01 | Hetzner | HEL1-DC1 | $590 |
| arch-node-s0-hel-02 | Hetzner | HEL1-DC6 | $584 |
| Total Number | 4 | Total Monthly Cost | $2493 |
Main reason for redundancy of archival nodes is to prevent network failure (single point of failure). When one node is down, it takes another node at least 2 weeks to sync the other one. Thus, if we have only 3 nodes and 1 goes down, only 1 will be serving traffic.
Note: The $2500 cost for 4 archival nodes is included as part of the $15k projection for July 2023.
In order fully terminate the ERPC nodes, we need to fulfill two criterias:
In January 2023, we migrated 2 of our archival nodes from AWS to Latitude in order to save cost. We initially synced the arch-s0-01 (LA archival) and was planning to sync arch-s0-02 (London archival) late January. However, Latitude had server problems and we were in a situation where we had to re-sync both nodes (where sync for each node takes at least 2 weeks). Since 2 archivals were down, we had to use 1 from Hetzner to face the customers and 1 to fully sync an archival from Latitude.
Currently, our archival node status looks as follows: