Service status
Know what is happening with your workspace.
SaveOn uses clear service communication so customers can distinguish platform availability, database-specific health, reservation state, and support notices.
Current service communication
This public page communicates broad application availability and planned maintenance. Database-specific health belongs in the authenticated workspace because it depends on the customer’s own project, endpoint, region, and current state.
How database health is shown
Inside the workspace, SaveOn can show the current service state, endpoint state, last synchronization time, region, and provider-returned metrics where available. A status such as Operational should reflect an actual returned signal. If a signal is not available, the interface should say Status unavailable rather than claim that every dimension is healthy.
Incident reporting
If you experience a problem, record the workspace name, approximate time, action taken, and error message. Avoid sending passwords, API keys, or connection strings. This information helps support distinguish an account issue, a database issue, a payment issue, and a broader service event.
Maintenance preparation
Before planned maintenance, review active workloads, confirm backups, check renewal status, and make sure your team knows how to reach support. Keep migration and export procedures tested so the business is not dependent on a single interface.
Frequently asked questions
Where do I see my database’s live state?
Open the authenticated database workspace or the Infrastructure section of Settings. Those areas can show database-specific signals without exposing internal infrastructure identity.
What if a metric says unavailable?
Unavailable means the current service response or plan does not expose that measurement. It is not the same as a failure.
Continue exploring SaveOn
Choose the next resource for your project, from practical documentation to pricing, security, and support.