Skip to content

Commit 563653a

Browse files
authored
Merge pull request #2621 from adrianparker/main
Update Uptime stats for January 2025
2 parents af66b6b + c0a0fc5 commit 563653a

1 file changed

Lines changed: 21 additions & 20 deletions

File tree

Lines changed: 21 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: src/layouts/Default.astro
33
pubDate: 2023-01-01
4-
modDate: 2025-01-08
4+
modDate: 2025-02-04
55
title: Octopus Cloud Uptime SLO
66
navOrder: 50
77
description: The uptime SLO for Octopus Cloud instances
@@ -13,41 +13,42 @@ Octopus Cloud's monthly uptime SLO is 99.99%.
1313

1414
We calculate uptime as 100% of the month, less all unplanned downtime.
1515

16-
Planned maintenance is a key benefit of Octopus Cloud and is scheduled in advance, so we exclude it from our uptime SLO calculation. Other than in exceptional circumstances, planned maintenance occurs during the customer’s [maintenance window](/docs/octopus-cloud/maintenance-window). In the 4 months ending October 2024, planned maintenance averaged fewer than 8 minutes of downtime per week.
16+
Planned maintenance is a key benefit of Octopus Cloud and is scheduled in advance, so we exclude it from our uptime SLO calculation. Other than in exceptional circumstances, planned maintenance occurs during the customer’s [maintenance window](/docs/octopus-cloud/maintenance-window). In the 7 months ending January 2025, planned maintenance averaged fewer than 6 minutes of downtime per week.
1717

1818
## Uptime Track Record
1919

2020
This table lists Octopus Cloud's monthly uptime statistics for the last 12 months.
2121

22-
We list our achieved uptime percentage and the average amount of unplanned downtime for each month. We also show these data points including planned maintenance.
22+
We list our achieved uptime percentage and weekly unplanned downtime duration. We also show these data points including planned maintenance. Data points measured at 95th percentile of all paid subscriptions.
2323

24-
| Month | Uptime % | Average weekly unplanned downtime | Uptime % incl. planned maintenance | Average weekly downtime incl. planned maintenance |
24+
| Month | Uptime % | Weekly unplanned downtime | Uptime % incl. planned maintenance | Weekly downtime incl. planned maintenance |
2525
| :----- | ------: | ------: |------: | ------: |
26-
| December 2024 | 100% | 2s | 99.9666% | 114s |
27-
| November 2024 | 100% | 2s | 99.8895% | 446s |
28-
| October 2024 | 99.9973% | 5s | 99.917% | 309s |
29-
| September 2024 | 99.9977% | 4s | 99.9165% | 313s |
30-
| August 2024 | 99.9955% | 8s | 99.8978% | 447s |
31-
| July 2024 | 99.9978% | 6s | 99.8602% | 616s |
32-
| June 2024 | 99.9931% | 9s | 99.9196% | * 279s |
33-
| May 2024 | 99.9976% | 11s |- | - |
34-
| April 2024 | 99.9687% | 17s |- | - |
35-
| March 2024 | 99.9914% | 10s |- | - |
36-
| February 2024 | 100% | 2s |- | - |
37-
| January 2024 | 99.9976% | 3s |- | - |
26+
| January 2025 | 99.9924% | 49s | 99.9397% | 371s |
27+
| December 2024 | 100% | 0s | 99.9666% | 203s |
28+
| November 2024 | 100% | 0s | 99.8895% | 672s |
29+
| October 2024 | 99.9973% | 21s | 99.917% | 504s |
30+
| September 2024 | 99.9977% | 14s | 99.9165% | 511s |
31+
| August 2024 | 99.9955% | 28s | 99.8978% | 623s |
32+
| July 2024 | 99.9978% | 14s | 99.8602% | 847s |
33+
| June 2024 | 99.9931% | 49s | 99.9196% | * 490s |
34+
| May 2024 | 99.9976% | 21s |- | - |
35+
| April 2024 | 99.9687% | 189s |- | - |
36+
| March 2024 | 99.9914% | 56s |- | - |
37+
| February 2024 | 100% | 0s |- | - |
3838

3939
\* We began capturing planned downtime metrics on June 10, 2024.
4040

4141
### How we calculate uptime
4242

43-
We calculate uptime as 100% minus the percentage of unplanned downtime seconds out of the total seconds in a calendar month. We measure uptime performance at the 95th percentile of all paid subscriptions (95% of customers experienced at minimum the listed uptime %).
43+
We calculate uptime as 100% minus the percentage of unplanned downtime seconds out of the total seconds in a calendar month. We measure all data points at the 95th percentile of all paid subscriptions (95% of customers experienced the listed measurement *or better*).
44+
45+
We exclude downtime that arises from planned or customer-requested maintenance from our uptime SLO calculation, but we measure and report it for transparency.
4446

45-
We exclude downtime that arises from planned or customer-requested maintenance from our uptime SLO calculation, but we measure and report it for transparency.
4647
Some Octopus Cloud customers use [dynamic workers](/docs/infrastructure/workers/dynamic-worker-pools). As the name implies, these workers are dynamically assigned to a cloud instance and are spun up and down as required by the Deployment or Runbook executed. We exclude Dynamic Workers from our calculation of uptime.
4748

4849
**“Downtime”** means a period where the customer instance is unavailable, according to Octopus Deploy's internal and external monitoring systems.
4950

50-
**"Average weekly unplanned downtime"** is measured in seconds per week, as an arithmetic mean across all paid customers. It excludes planned maintenance and customer-requested maintenance.
51+
**"Weekly unplanned downtime"** is shown as seconds per week. We use the month's total unplanned downtime duration measured at the 95th percentile of all paid subscriptions to calculate a weekly average duration. It excludes planned and customer-requested maintenance.
5152

52-
**"Average weekly downtime incl. planned maintenance"** is measured in seconds per week, as an arithmetic mean across all paid customers. It includes planned maintenance and customer-requested maintenance.
53+
**"Weekly downtime incl. planned maintenance"** is shown as seconds per week. We use the month's total downtime duration measured at the 95th percentile of all paid subscriptions to calculate a weekly average duration. It includes unplanned downtime, as well as downtime arising from planned and customer-requested maintenance.
5354

0 commit comments

Comments
 (0)