Control plane uptime
99.5% monthly availability on the public console and API. Maintenance windows are announced at least 72 hours in advance and excluded from the calculation.
Platform status and availability.
Availability commitments for the six subsystems that make up Penaxtra, and how incidents are notified.
Last refreshed:
This page publishes the availability commitments that apply to a Penaxtra subscription. It does not yet publish measured uptime: incident notices go to the subscribed contact on every active workspace, and a customer can request the availability record for their own term at any time.
What we commit to. What you do when we miss it.
Database availability
Nightly encrypted backups held off-server with write-once retention. Restores are exercised from those backups; there is no hot standby and no continuous archiving, so recovery is to the most recent backup rather than to an arbitrary point in time.
Incident notification
Critical incidents are notified within fifteen minutes of detection. Customers on Business and Enterprise tiers receive email notifications; Enterprise tier additionally receives Slack or webhook notifications.
Service credit
Falling below the SLA in a billing month triggers a service credit of ten percent for the first hour past target, then one percent per additional hour, capped at fifty percent of the monthly fee. Enterprise contracts may negotiate alternative remedies.
Want incident notifications?
Incident notices go to the subscribed contact on every active workspace. Not a customer yet? Ask us to add you to the status list.
Ask to be notified →Goes to a person, not a sequence. One short message per incident.