System status
Platform availability, incidents and planned maintenance.
Live status is at status.terravek.com
The authoritative, live status page is hosted separately at status.terravek.com so that it stays available when the main site is not. Subscribe there for incident notifications by e-mail, RSS or webhook. This page is a summary and an archive.
Current status
| Service | Region | Status |
|---|---|---|
| ORBIS Cloud | eu-nl-1 (Amsterdam) | Operational |
| ORBIS Cloud | eu-de-1 (Frankfurt) | Operational |
| ATLAS API | Global | Operational |
| ORBIS Viewer | Global | Operational |
| Tasking & scheduling | Global | Operational |
| Svalgrund ground segment | SVG-GS | Operational |
| Customer portal | Global | Operational |
| Identity (SSO / OIDC) | Global | Operational |
Planned maintenance windows
Standard windows are Wednesdays 02:00–04:00 UTC for eu-nl-1 and Thursdays 02:00–04:00 UTC for eu-de-1. Not every window is used. Any change with a plausible path to customer impact is announced at least five working days ahead, whether or not we expect downtime — why we over-announce.
Recent incidents
| Date | Status | Incident | Summary |
|---|---|---|---|
| 11 Jul 2026 | Resolved | Elevated delivery latency, eu-nl-1 | A storage tier rebalance caused delivery latency to exceed the SLO for 3h 41m. No data loss. Post-incident review published 2026-07-16. |
| 2 May 2026 | Resolved | ATLAS API intermittent 503, all regions | A misconfigured rate-limit rule rejected a proportion of authenticated requests for 46 minutes. Corrected by rollback. Post-incident review published 2026-05-07. |
| 28 Mar 2026 | Resolved | Svalgrund pass scheduling degraded | Scheduler conflict resolution failed for overlapping windows on two satellites; 4 passes were missed and re-tasked. No customer-visible delivery miss. |
| 15 Jan 2026 | Resolved | ORBIS Viewer tile rendering errors | A cache invalidation defect served stale tiles to a subset of users for 2h 12m. |
| 30 Nov 2025 | Resolved | Planned failover test overran, eu-de-1 | A scheduled failover exercise overran its window by 38 minutes. Announced in advance; counted as customer impact and reviewed accordingly. |
Post-incident reviews
Terravek publishes a review for every incident with customer impact, normally within five working days. They state what customers experienced, the timeline in UTC, the technical cause, the contributing factors, what went well and what did not, and the actions with owners and dates.
No individual is named as a cause. Why, and what the format is.
Incident notifications also cross-post to @terravek. Support: support@terravek.com · NOC: noc@terravek.com