The Apica Testing network is based on more than 50 co-locations around the world. These contain a both physical and hybrid cloud-based testing data clusters.

When setting up a check, it is assigned one or more locations, which will act as points of origin. This provides an easy way of providing a comprehensive monitoring solution.

If you assign a check to one location during check creation, one copy of the check will be created. If you assign a check to multiple locations during check creation, multiple copies of the check will be created - one copy for each location selected during check creation. One check cannot run from multiple locations.

Tiers

Open

Agent Tiers

Apica locations are classified into various Tiers according to reliability and scalability.

Tier classification

A location that is classed as a Tier 3 is usually running in a country with less reliable infrastructure and performance, while Tier 1+ ensures the quality & scalability out of the location.

The tiers can be used to intentionally monitor the performance of your service from corresponding regions.

Failover

In some instances a primary location may nor be working. When that happens, a secondary location may be used as failover.

Failover Functionality

The failover location can be enabled for each individual check.

When the primary location is unavailable or unable to connect to the monitored service, a secondary location is automatically selected and used instead.

The secondary location will reside in the same geographical region and have the same priority, but the exact location is determined at run time.

Public IP Location List

Use the following lists for whitelisting purposes to ensure Apica public locations are accessible from within your network.

If you are granting an Apica resource access to your application, they will be accessing your network from the IP ranges 194.213.118.0/24 and 194.213.119.0/24. As such, please allow access to the application or server in question from those IP ranges.