Skip to main content

Uptime and availability

Historical uptime is an indicator of the reliability of a service, in our case the Radix Kubernetes cluster. The Radix uptime is measured by sending requests from an external service every 1 minute to an endpoint running in Radix, and recording whether the request completed successfully or not. The uptime number is then calculated as the ratio (percentage) of aggregated time between consecutive successful requests over the length of the measurement period.

Radix will only report the measured uptime for the Radix platform, and not the other services provided, i.e. build- deploy pipeline, montitoring, vulnerability scanning. We will use an external service that monitors an application running on the Radix Platform, from outside the Azure tenant, it will calculate availability of the applicable monitored service.

Service monitored:
Timeperiod:Rolling last 90 days
Monitoring tool:Dynatrace
Availability calculation %:Uptime / (Uptime + Downtime) x 100

The Uptime/Availability report, will be an indication of future reliability of Radix Platform.


The monitoring has not been active for 90 days yet, so the current report will show the availability % for the number of days it has been running.

  • Planned maintenance: We will announce, in our main Slack channel - #omnia_radix, planned maintenance at least 2 business days in advance. Downtime during planned maintenance does not affect uptime goals
  • Disaster Recovery: A Disaster Recovery Procedure is in place and the procedure is executed on a weekly basis. Estimated time to recover a cluster is 15 minutes, estimated time to rebuild and recover a complete cluster is 1 hour. (A backup of all resources in the Kubernetes cluster is done every 1 hour, and is the main ingredient of the recovery recipe)

Platform cluster availability and services

The Radix Platform should be used when your team has chosen Radix as PaaS (Platform-as-a-Service) for a product under development or in production.

PlatformProducts under development or in productionEvery ~6 monthsYes
PlaygroundTesting and experimenting with RadixBest-effort


Schedule for Radix DevOps/Support team - 08:00 - 16:00 CET/CEST on Norwegian working days

  • Support channels: File issue on radix repo or ask on #omnia_radix_support on Slack
  • Response time: As soon as possible within business hours, at least next business day
  • On-call duty: No, please contact us to discuss options
  • Resolution time: Cannot be guaranteed, but for critical issues work on fixing the problem will start immediately and continue within business hours until resolved

Associated operational risks

  • No incident management beyond schedule "Norway - default" - i.e. no support after 16:00 CET/CEST on Norwegian working days
  • Infrastructure downtime despite robust, high-availability infrastructure

Uptime risk management

A risk assessment for cluster uptime has been done, and the most critical risk scenarios are identified, and risk mitigation actions have been agreed upon and are implemented as required.

Disaster recovery

Application configuration is backed up every hour using Velero and that backup is stored in the Azure Storage account. We have created a script that can create a new AKS instance and migrate all applications from the affected cluster to the new one.

RTO (Recovery Time Objective) has been estimated at 20 minutes from the moment the Radix team starts working on it. Keep in mind that the RTO is only an estimate since external factors can also influence the recovery time. For example, this time will increase if there is a high load on Azure REST API or Azure managed Kubernetes API server.

Some of the failure events that can take down the service or introduce delays and timeouts:

  • Bad commit can introduce a bad code/bug in Radix components
  • Executing a command in the wrong cluster
  • Resource exhaustion, CPU, Memory, Disk issues
  • Upgrading 3rd party components
  • Azure resources/services are deleted
  • MS Azure services unavailable
  • Kubernetes bugs
  • Kubernetes API changes
  • Expired certificates
  • Network issues, DDOS
  • Expired secrets

We are working hard to mitigate as much of these as possible.

Radix Playground services

Use Playground for testing Radix, see if it’s a good fit for your projects, and provide feedback. When you are ready to commit, register your application in the Radix Platform, even if your application still is development stage. The Radix Platform has improved services.

  • Support channels: Same as for Radix Platform (see above). Help will be provided when team has capacity

  • Uptime: "Best-effort", but no guarantee of uptime. Planned maintenance is announced as early as possible

Automatic cleanup in Playground cluster

A stricter lifecycle policy for using Radix Playground is in place, to make sure everybody share the resources and avoid unattended applications using unnecessary resources.

Any application which has not been deployed or restarted in the last 7 days will be stopped.

After further 21 days of inactivity, all stopped applications will be deleted.