---
title: "MyAryaka redundancy"
canonical: "https://docs.aryaka.com/space/KNOW/1269399573/MyAryaka%20redundancy"
format: markdown
---
MyAryaka allows Aryaka customers and partners to monitor and manage their service.

You can access MyAryaka over the Aryaka IP App Delivery Service (IADS). The domain [my.aryaka.com](http://my.aryaka.com) CNAMES to [my.aryk.aads1.net](http://my.aryk.aads1.net), which resolves to an IP address on an edge POP based on a user’s location. This allows users to connect to the nearest POP when accessing MyAryaka. IADS is optimized to ensure that end users experience high-quality performance when accessing MyAryaka from anywhere in the world.

MyAryaka is hosted on the San Jose POP, but there is a redundant setup on the Amsterdam POP in case of an outage at the San Jose POP. IADS controls the redirection of traffic from the San Jose POP to the Amsterdam POP if required.

The following graphic depicts an on-premises and a remote user accessing MyAryaka from different edge POPs: 

![MyAryaka IADS.png](media://8d1843b4-21bc-47d4-97e2-4e10f86b3643)

MyAryaka comprises the following components:

- Configuration management
- Statistics and log collector
- Data processing
- Alert management

These components are hosted behind a pair of load balancers that are deployed in active-standby mode to provide machine-level redundancy.

The following graphic depicts the components of MyAryaka and the load balancer:

![MyAryaka Components.png](media://e8f937d7-f828-4cee-9f92-2cc40b91c87d)

Each component’s database is backed up to its redundant peer every 30 minutes. These components are also monitored by the Aryaka Network Operations team. If a failure occurs on any component, the team determines the type of recovery operation that needs to be performed.