All systems operational.
Updated   just now
Region   AU · Sydney
Next maintenance   None scheduled
Uptime · 90 days
99.98%
Across all services, rolling.
Snapshots · last 24 h
14,820
Completed successfully across the fleet.
Restore p50
38s
Median single-record restore latency.
Open incidents
0
No active customer-impacting incidents.
Operational
Partial / degraded
Outage
Each bar · one day · oldest left, today right
Incident log

Recent activity.

09 May 202610:42 — 11:08 AEST
Snapshot scheduler — delayed snapshots MinorResolved
A subset of customers on Option B (private cloud, AWS Sydney) experienced delayed snapshot starts of approximately 18 minutes following an upstream IAM-role propagation delay in our cloud provider. All snapshots completed successfully within the 24-hour SLA. No data loss, no missed snapshots.
10:42Monitoring alert — snapshot start latency above threshold.
10:51On-call engineer engaged; root cause traced to provider IAM propagation.
11:08Scheduler caught up; all affected snapshots running normally.
15:30Post-incident review complete. Mitigation: pre-warming IAM roles in next release.
21 Apr 202602:00 — 02:38 AEST
Scheduled maintenance — storage gateway upgrade MaintenanceCompleted
Routine upgrade of the storage gateway service to introduce per-customer key-wrap rotation. The console was placed in read-only mode for 38 minutes; snapshot scheduler was paused. All paused snapshots ran on the next cycle as designed.
02:00Maintenance window opens. Console read-only. Scheduler paused.
02:38Rollout complete. All services verified. Scheduler resumed.
03 Apr 202614:11 — 14:24 AEST
Restore service — slow exports MinorResolved
CSV export of full-organisation restores exceeded the 60-second p95 SLO for a 13-minute window. Single-record restores were unaffected. Caused by an inefficient query plan after a database index rebuild; resolved by re-warming the planner cache.
14:11p95 export latency alert fires.
14:24Planner cache warmed; latency back to baseline.
18 Mar 202608:55 — 09:02 AEST
Console — sign-in errors MinorResolved
A subset of customers received "session expired" errors when signing in to the console. Snapshots and the restore service were unaffected. Caused by a misconfigured rate limit after a routine deploy; rolled back within seven minutes.
08:55Sign-in error rate above threshold.
09:02Deploy rolled back; sign-in errors stop.

Get notified when something changes.

We email status updates for incidents and scheduled maintenance only. No marketing, no monthly digest. You can unsubscribe at the bottom of any email.