what are the statuspage.io RPO and RTO requirements?
Asked by Bulusu Venkatesh:

Please answer the below question:

1)What all are required to meet the Statuspage.io RPO and RTO requirements?


Answers:
author: Chris DeGidio
body: Hi Bulusu,

[About your data](https://www.atlassian.com/trust/security/data-management) - Atlassian's FAQ page about their data storage and disaster recovery plan for their OnDemand services.

You may also find this answer of value: <https://answers.atlassian.com/questions/178735>

Please let us know if you have any further questions or concerns.

Regards,

Chris

comments: author: Bulusu Venkatesh
body: Hi Chris,

The link you have provided is eight years old. Is it still applicable?

Can statuspage.io meet the following RTO and RPO requirements. If not what are the values for each of these four resilience aspects?

Operational RTO 5 mins

Operational RPO 5 mins

Disaster recovery RTO 4 hours

Disaster recovery RPO 4 hours


author: Chris DeGidio
body: Hi Bulusu,

The RPO and RTO timelines are mentioned here <https://www.atlassian.com/trust/security/data-management> There is a table toward the middle of the page with these defined and with examples.

Please let us know if you have any further questions or concerns.


author: Bulusu Venkatesh
body: Hi Chris,

Thanks for your answer. The link you have provided only gives me Operational RTO and RPO values. But i also want to know-

1. Disaster RPO and RTO values?


author: Chris DeGidio
body: Hi Bulusu,

The definitions of the link I sent you do indicate those are for disaster:

*\*RPO -- Recovery Point Objective -- data loss in event of disaster*

*\*\*RTO -- Recovery Time Objective -- services restoration in the event of a disaster*

Additionally, if we do fall outside of the SLA uptime agreement you are eligible to request compensation as detailed here <https://support.atlassian.com/subscriptions-and-billing/docs/service-level-agreement-for-atlassian-cloud-products/>

Please let us know if you have any further questions or concerns.


author: Bulusu Venkatesh
body: Hi Chris,

Thanks for your answer.

1. Can you please provide me the Operational RPO and RTO Timelines also?


author: Chris DeGidio
body: Hi Bulusu,

We should not have Data loss in our day-to-day operations or measurements on time to recovery unless we are in a situation to measure those data points. <https://www.atlassian.com/trust/security/data-management> Will be the page to reference for this information.

Please let us know if you have any further questions or concerns.


author: Bulusu Venkatesh
body: Hi Chris,

Thanks for answering my question.

The site mentions 60-120 seconds for failover etc.. does that mean that Operational RPO and RTO will be met as 1 hour and 6 hours accordingly?

Pasted from link provided--<https://www.atlassian.com/trust/security/data-management>

Jira and Confluence utilises the multi-AZ deployment mode for Amazon RDS. In a multi-AZ deployment, Amazon RDS provisions and maintains a synchronous standby replica in a different AZ of the same region to provide redundancy and failover capability. The AZ failover is automated and typically takes **60-120 seconds**, so database operations can resume as quickly as possible without administrative intervention. These region, AZ and replication concepts are highlighted in the diagrams below. Opsgenie, Statuspage, Trello and Jira Align use similar deployment strategies, with small variances in replica timing and failover timing.


Tags: cloud