Stay updated on the latest Radix News
Sign up for all the latest news, events and announcements!
By clicking “Sign up”, you agree to our Privacy policy. We’ll occasionally send you account related emails.
Due an influx of demand, Radix-provided archive nodes (nodes which provide data to the Wallet and https://explorer.radixdlt.com) are currently experiencing some difficulties keeping up with the current volume of requests. This is causing slow performance for some users, up to and including outright timeouts on requests. Network consensus is unaffected; this is strictly a user interface-level issue.
To address this problem as quickly as possible, Radix has "cross-wired" some archive nodes in lower demand regions to also serve requests from our areas of highest demand (Europe and the US), and we are in the process of spinning up additional archive nodes. We expect this will promptly get us back to snappy performance.
The long term resolution for this issue is migration to an updated API and gateway service, which will horizontally scale much more easily to meet much greater demand. This remains the Radix Network team's highest priority, and implementation has been underway for some time now. We do not yet have a high-confidence date for that release (which will coincide with a new Wallet release to take advantage of it).
Update: Issue seems resolved for now. We will continue to monitor.
Due an influx of demand, Radix-provided archive nodes (nodes which provide data to the Wallet and https://explorer.radixdlt.com) are currently experiencing some difficulties keeping up with the current volume of requests. This is causing slow performance for some users, up to and including outright timeouts on requests. Network consensus is unaffected; this is strictly a user interface-level issue.
To address this problem as quickly as possible, Radix has "cross-wired" some archive nodes in lower demand regions to also serve requests from our areas of highest demand (Europe and the US), and we are in the process of spinning up additional archive nodes. We expect this will promptly get us back to snappy performance.
The long term resolution for this issue is migration to an updated API and gateway service, which will horizontally scale much more easily to meet much greater demand. This remains the Radix Network team's highest priority, and implementation has been underway for some time now. We do not yet have a high-confidence date for that release (which will coincide with a new Wallet release to take advantage of it).
Update: Issue seems resolved for now. We will continue to monitor.
