Aplas DocsService availability and maintenance
Where to check Aplas status, when routine maintenance happens in your region, and how we tell you about anything bigger
Live status for every region is at status.aplas.com. Subscribe there to get incident and maintenance notices by email.
Routine maintenance window
Your organization's data lives in one of three regions: Australia, the EU or the US. Routine maintenance, including database operating-system patches, runs in that region's own window in the small hours of a weekend night, local time:
| Region | Window (UTC) | Local, standard time | Local, daylight saving |
|---|---|---|---|
| Australia (Sydney) | Sunday 15:00–17:00 | Monday 01:00–03:00 AEST | Monday 02:00–04:00 AEDT |
| EU (Frankfurt) | Sunday 01:00–03:00 | Sunday 02:00–04:00 CET | Sunday 03:00–05:00 CEST |
| US (N. Virginia) | Sunday 07:00–09:00 | Sunday 02:00–04:00 EST | Sunday 03:00–05:00 EDT |
The UTC window is fixed; the local time moves with daylight saving.
Most weeks nothing happens. When a patch is due, Aplas may be unavailable for under five minutes inside the window while the database restarts. Open pages recover on their own. API clients can retry a failed request when it is safe to do so; if a write's outcome is uncertain, check whether it took effect before retrying, so it is not applied twice. The dates are posted on status.aplas.com as soon as our cloud provider announces them, normally several days ahead.
Anything bigger
Maintenance expected to last longer than 15 minutes, or to fall outside the window, is announced by email to organization owners and admins at least five business days ahead, as well as on status.aplas.com.
Service levels
Customers on an Enterprise agreement have a 99.9% monthly availability commitment in their order form, measured excluding scheduled maintenance; the exact terms are in that order form. Other plans run on the same infrastructure and get the same maintenance notices, but carry no contractual availability commitment.