Detection
Billing jobs, API error rates and provider callbacks are monitored. A failing renewal or webhook backlog is treated as an incident, not a support ticket.
Status
Sobtra does not yet publish a live status feed with historical uptime percentages. Publishing a number we do not measure would be worse than saying so. Here is what we do commit to, and how incidents reach you.
How incidents are handled
During the beta, incident communication runs through the merchant support channel rather than a public timeline.
Billing jobs, API error rates and provider callbacks are monitored. A failing renewal or webhook backlog is treated as an incident, not a support ticket.
Affected merchants are emailed with what broke, which records were affected and whether any action is required on their side.
After resolution, a short summary states the cause, the fix and any change made to prevent recurrence.
State definitions
Requests are succeeding within expected latency and no billing job is behind schedule.
The platform is responding, but a subsystem is slow or partially failing. Billing operations may be delayed.
A core subsystem is unavailable. Subscription processing, invoicing or payment coordination is affected.
A scheduled change is in progress. Billing jobs are queued and processed after the window closes.
Known beta limitations
Reporting an issue
If billing state looks wrong, tell us before working around it in your own database.