 Altostrat’s regional servers form a globally distributed infrastructure that optimizes routing and reduces latency for routers connecting to the Management VPN. By geographically locating servers in different continents, we ensure minimal single points of failure.
Altostrat’s regional servers form a globally distributed infrastructure that optimizes routing and reduces latency for routers connecting to the Management VPN. By geographically locating servers in different continents, we ensure minimal single points of failure.
Purpose of Regional Servers
- Optimal Routing: DNS resolves each router to the closest regional server, cutting down on round-trip times.
- Reduced Latency: Traffic from your MikroTik device travels a shorter distance before entering Altostrat’s management plane.
- High Availability: If one region encounters downtime, DNS reroutes connections to another operational cluster.
Example DNS Flow
Available Regional Servers
| Location | FQDN | IP Address | 
|---|---|---|
| 🇩🇪 Frankfurt, Germany | europe.altostrat.io | 45.63.116.182 | 
| 🇿🇦 Johannesburg, South Africa | africa.altostrat.io | 139.84.235.246 | 
| 🇦🇺 Melbourne, Australia | australia.altostrat.io | 67.219.108.29 | 
| 🇺🇸 Seattle, USA | usa.altostrat.io | 45.77.214.231 | 
Geographical DNS Routing
1
DNS Query
When a MikroTik router asks for 
mgnt.sdx.altostrat.io, Altostrat’s DNS determines the nearest regional
cluster based on the router’s IP geolocation.2
Server Assignment
The query returns a server address (e.g., 
europe.altostrat.io) located in Germany for routers in
nearby regions.3
Performance Boost
Shorter travel distance = better latency and faster management-plane interactions. During a regional outage, DNS
automatically resolves to the next available server cluster.
Best Practices
- Default Routing
Let your MikroTik resolve mgnt.sdx.altostrat.iodynamically. Don’t hardcode IPs unless necessary.
- Failover Awareness If your region is offline, the router automatically reconnects to another operational cluster once DNS updates.
- Monitor Keep an eye on the Orchestration Log for any server-switching events.