Service Level Notice
Beta targets, measured publicly. No service credits until general availability.
Overview
These are engineering targets we take seriously and measure publicly, not guaranteed service levels. The platform is a beta run by a single operator; there are no service credits yet. You can watch our actual numbers live, including the money invariant, without logging in.
Status: beta
The Platform is in beta (Terms § 2.2). The figures below are availability and response targets. They become enforceable service levels with service credits only at general availability, which will be announced separately.
Availability targets (monthly)
Measured per calendar month across the Provider's frames. Planned maintenance (announced in advance where feasible), integrity halts under Terms § 4.5 and § 5.5 (d), read-only safety modes, force majeure, and outages caused by the user's own systems are excluded from measurement.
- Registry API: 99.5%
- Web console: 99.0%
- Event ledger and supply audit: 99.9%
Transparency
Live status is public: operational dashboards are published via the public status pages, and the supply invariant of every frame is continuously verifiable at auditor.theprotocol.cloud without authentication. We publish honest numbers, including bad ones.
Support response targets
Business days: [provider details unavailable].
- Security reports ([provider details unavailable]): acknowledgment within 24 hours
- Support tickets, account and payment issues: first response within 2 business days
- General inquiries: first response within 5 business days
Maintenance and safety interventions
The Provider may perform maintenance and may halt or degrade features where the supply invariant, security, or legal compliance requires it (Terms § 2.2, § 4.5). Material planned maintenance is announced in the console or by email where feasible.
No service credits during beta
During beta, no service credits, penalties, or availability-based refunds are offered. Statutory rights, including Terms § 6, remain unaffected.