Our customer base grows on a daily basis. This means we have to deploy more service zones closer to the geographical regions where our customers are located. All this Service Zones or Satellites help us to deliver always the lowest latency possible to our users, no matter if they are in a Free or Paid plan, or if they are using the API anonymously. That’s why we have just launched a New service zone in Australia for our users from Oceania.

When api.apility.net receives a request our DNS resolves to the closest geographically distributed Satellite. For example, if you ping to api.apility.net from Melbourne (Australia) you will see how it resolves to the closest servers:

PING satellite-ovh-syd1.apility.net (139.99.198.228) 56(84) bytes of data.
64 bytes from satellite-ovh-syd1.apility.net (139.99.198.228): icmp_seq=1 ttl=53 time=12.9 ms
64 bytes from satellite-ovh-syd1.apility.net (139.99.198.228): icmp_seq=2 ttl=53 time=12.8 ms
64 bytes from satellite-ovh-syd1.apility.net (139.99.198.228): icmp_seq=3 ttl=53 time=12.7 ms
--- satellite-ovh-syd1.apility.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 7000ms
rtt min/avg/max/mdev = 12.773/12.851/12.916/0.109 ms

But if you ping from New York (USA) you will see a different server responding:

PING satellite-aws-us-east1-b.apility.net (34.239.23.185) 56(84) bytes of data.
64 bytes from satellite-aws-us-east1-b.apility.net (34.239.23.185): icmp_seq=1 ttl=45 time=7.25 ms
64 bytes from satellite-aws-us-east1-b.apility.net (34.239.23.185): icmp_seq=2 ttl=45 time=7.24 ms
64 bytes from satellite-aws-us-east1-b.apility.net (34.239.23.185): icmp_seq=3 ttl=45 time=7.19 ms
64 bytes from satellite-aws-us-east1-b.apility.net (34.239.23.185): icmp_seq=4 ttl=45 time=7.61 ms
64 bytes from satellite-aws-us-east1-b.apility.net (34.239.23.185): icmp_seq=5 ttl=45 time=7.21 ms
--- satellite-aws-us-east1-b.apility.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4011ms
rtt min/avg/max/mdev = 7.197/7.303/7.618/0.184 ms

 

The following map shows the locations of our different Service Zones. We have opened a new Service Zone every month since the launch of the service in January 2018. We will open new locations soon in Japan in South America depending on the users’ growth in this areas.

Apility.io Service Zones

 

The map shows all our Public Service zones, but we can also deploy our Service Zones in Private Clouds and Enterprise Datacenters to deliver the best possible latency to our customers and at the same time keeping fresh all the information of the hundreds of blacklists we track and the millions of IP addresses, domains and emails we store. If you think you need a Private deployment in your Private Cloud or Enterprise Datacenter please don’t hesitate to contact us and request for information.