System Status
All Systems Operational
Vaultro at a glance
Vaultro status covers the services that keep the wallet usable across seven mainnet networks and multiple client platforms. This includes chain connectivity, relayer execution, pricing, history, merchant settlement, jackpot events, and notification delivery.
A green status does not mean every external dependency is perfect every second, but it does mean the surfaces monitored by Vaultro are behaving inside normal expectations.
- 7 mainnet networks are monitored for connectivity and execution health.
- 6 client surfaces depend on these services: web, browser, Windows, macOS, Android, and iOS.
- Merchant settlement, jackpot automation, and push notifications are part of the monitored stack.
Blockchain Nodes
Supported mainnet connectivity is healthy and monitored for quotes, balances, transfers, swaps, bridges, merchant settlement, jackpot settlement, and recovery actions.
API Services
Relayer, pricing, history, merchant payments, and notification services are operating normally so gasless execution, store checkout, push alerts, and recovery flows can complete as expected.
Router Invariants
Routing and execution invariants are monitored to reduce unsafe outcomes across transfers, payments, merchant settlement, bridges, and jackpot-related flows.
Relayer Limits
Relayer controls and policy checks are monitored so supported gasless and recovery actions stay within operational safety limits.
Operational Notes
What this page monitors
Vaultro monitors chain reads, relayer execution, pricing, history indexing, merchant payment events, jackpot settlement, recovery flows, and push notifications. These surfaces directly affect the speed and reliability users feel inside the wallet.
Which Vaultro features depend on healthy status?
Wallet transfers, gasless execution, QR and NFC merchant checkout, stablecoin settlement, jackpot prizes, history refresh, push notifications, and recovery flows all depend on healthy operational surfaces or healthy external chain connectivity.
What to do during an incident
If status is degraded, avoid forcing repeated transactions. Check the transaction hash, wait for chain finality when needed, and use the official status page as the primary source for incidents, degraded dependencies, and recovery guidance.
- Do not spam repeated retries while a dependency is degraded.
- Keep the transaction hash and the affected network when reporting an issue.
- Use the official status page before trusting social posts or third-party rumors.