Incidents, maintenance, and status updates
Thalassa Cloud communicates platform incidents and scheduled maintenance through status.thalassa.cloud and, for certain managed services, through email notifications within your configured maintenance windows.
Subscribe to the status page to receive updates when incidents or platform-wide maintenance are announced.
Status page
status.thalassa.cloud is the authoritative source for the current health of Thalassa Cloud services. It publishes:
| Update type | When it is posted |
|---|---|
| Active incidents | Unplanned outages, degraded performance, or partial failures affecting platform services |
| Scheduled maintenance | Planned work that impacts an entire service, the platform as a whole, a region, or an availability zone |
| Resolved incidents | Post-incident summaries when an issue is closed |
| Historical record | Past incidents and maintenance for transparency and post-mortem reference |
When maintenance or an incident affects shared infrastructure — for example, a control plane component, regional networking, or an entire availability zone — you will find the details, impact scope, and progress updates on the status page.
Check the status page before opening a support ticket for widespread issues. If an incident is already listed, updates will appear there as our operations team progresses through investigation and remediation.
What appears on the status page vs email
Not every maintenance event is posted on the status page. We use the status page for changes with broad or shared impact. Service-specific maintenance that affects only your resources is communicated directly to you.
| Scope | Channel |
|---|---|
| Entire platform or region | status.thalassa.cloud |
| Single availability zone | status.thalassa.cloud |
| Shared service outage (API, console, DNS, etc.) | status.thalassa.cloud |
| Your Kubernetes cluster | Email + console — within your maintenance window |
| Your DBaaS instance | Email — within your maintenance window |
| Your compute instance (host reboot, hypervisor maintenance) | Email — within your maintenance window |
Service-specific maintenance notifications
Managed services such as Kubernetes and DBaaS run on shared infrastructure that is periodically maintained — for example, hypervisor patches, required node reboots, or version upgrades. These events are scoped to your resources and scheduled within the maintenance window you configure.
You receive email notifications for service-specific maintenance, including:
- Advance notice — Scheduled maintenance with the expected date, time, and nature of the work
- Start notification — When maintenance on your resource begins
- Completion notification — When maintenance finishes, including the outcome
Kubernetes
Kubernetes clusters receive maintenance notifications for control plane upgrades, node pool rolling updates, and underlying infrastructure work. Configure your maintenance window and upgrade strategy so maintenance occurs during periods your workloads can tolerate brief disruption.
The console also shows upcoming and in-progress cluster maintenance alongside email notifications.
DBaaS
Database instances receive email notifications for engine upgrades, infrastructure maintenance, and required reboots. Schedule maintenance windows through your database configuration so patching and upgrades align with your application’s tolerance for brief connectivity interruptions.
Compute
Individual virtual machines may receive email notification before host-level maintenance that requires a reboot. Where possible, workloads are live-migrated to avoid downtime; when a reboot is unavoidable, you are notified in advance within your maintenance window.
During an incident
If you experience issues that are not yet reflected on the status page:
- Check status.thalassa.cloud for active incidents or maintenance
- Verify whether the issue is limited to your organisation (configuration, quota, or workload) or affects the broader platform
- Contact Thalassa Cloud support if you believe you are experiencing an unreported platform issue
For security incidents affecting your own workloads — compromise, misconfiguration, or abuse — see Abuse reporting and Security assessments. Platform security incidents are communicated through the status page.