Service Level Agreement
Last updated: 15 August 2026
Every page of our site says "99.99% SLA, in writing". This is the writing. It applies to every Managed Node from Argusnodes.
1. The commitment
Each Managed Node will achieve Monthly Uptime of at least 99.99%: the node responds to RPC requests at its endpoint. Measured per node, per calendar month.
2. How uptime is measured
- Monthly Uptime = (minutes in month − Downtime minutes) ÷ minutes in month.
- Downtime is any minute in which the node fails to respond to our external monitoring probes. The same p50/p99 monitoring you see in your dashboard is the record; you are watching the measurement system itself.
- Partial degradation that still serves requests (for example elevated latency during a resync we initiated) is not Downtime unless the endpoint fails probes.
3. What is excluded
- Scheduled maintenance, announced at least [72 hours] ahead and capped at [4 hours] per node per month.
- Failures of the blockchain network itself: chain halts, consensus failures, or a chain upgrade that breaks every node of that network. If the chain is down, no node on earth is up.
- Suspension for non-payment or Acceptable Use violations.
- Customer-caused outages, including configuration changes you requested against our advice.
- For BYOH Services: hardware failure, facility, power or network faults of machines and sites you own. We commit to our response, not to your hardware.
- Force majeure events beyond reasonable control.
4. Service credits
If a node's Monthly Uptime falls below the commitment, you receive a credit against that node's next monthly fee:
- Below 99.99% and at or above 99.9%: 10% credit.
- Below 99.9% and at or above 99.0%: 25% credit.
- Below 99.0%: 50% credit.
Credits are claimed by any support channel within 30 days of the month's end, are capped at 100% of that node's monthly fee, and are the exclusive remedy for missed uptime under this SLA.
5. Support response
Support is 24/7 on ticket, chat, Telegram and Slack, with no priority tiers. Incident response for a node that is down begins immediately on detection by monitoring, whether or not you have reported it.