Frankfurt
Core router
- Carries
- Our voice address to the MirageTEL core
- Routes
- Route reflector for the whole network
- Serves
- Central Europe
The MirageTEL network
MirageTEL voice runs on our own autonomous system, AS403001: our own IPv4 and IPv6 addresses, our own routers in 7 locations across North America and Europe, and direct connections at the internet exchanges where the largest networks meet.
aut-num: AS403001 as-name: MIRAGE-GLOBAL-TECH org: Mirage Global Technologies LLC registry: ARIN inet6num: 2602:f2d3::/40 inetnum: 23.165.12.0/24 inetnum: 156.9.216.0/22 anycast: 2602:f2d3::/48 · every edge router rpki: ROA signed · origin valid aspa: published irr: route, route6 at ARIN voice: voice.miragetel.com → 23.165.12.162
Each location is one of our own routers or servers, joined to the others by an encrypted backbone. Calls enter our network at a router and travel inside it to the MirageTEL core in the European Union.
Both regions are joined by our encrypted backbone across the Atlantic
Core router
Exchange router
Network PoP
Core router
Edge router
Network PoP
Edge router
Exchange router
Exchange router
These figures are measured by RIPE NCC, the internet registry for Europe, and read by your browser while this page opens. We do not type them in.
Needs JavaScript to measure — the sources below show the same figures.
Calls to your MirageTEL number come in the same way: they arrive at our address, not at someone else’s.
Not everything runs on our network, and we would rather you heard it from us.
We exchange traffic directly with other networks at internet exchanges and carry the rest through 5 upstream networks, so there is always more than one way to reach you. Our peering policy is open.
| Exchange | With | Status |
|---|---|---|
| LocIX Frankfurt | Route servers AS202409 · Cloudflare AS13335 · Hurricane Electric AS6939 · Hetzner AS24940 | Live |
| LocIX Düsseldorf | Route servers AS202409 | Live |
| LONAP London | Route servers · Telehouse Docklands | Connecting |
| AMS-IX Amsterdam | Route servers | Coming soon |
| ONIX Toronto | Route servers | Connecting |
| MINAP Milan | Route servers | Coming soon |
Our routes are signed in RPKI, our upstreams are published in ASPA and our route objects are registered at ARIN — other networks can reject anyone who tries to announce our addresses.
RPKI · ASPA · IRRThe reverse DNS of both our IPv4 and IPv6 ranges is delegated and signed with DNSSEC.
DNSSECOur addresses are announced from several cities through 5 upstream networks and 2 internet exchanges; if one link fails, the internet routes around it.
Transit + peeringOur locations talk to each other only through encrypted tunnels; the MirageTEL core has no other way in.
Encrypted backboneEvery router, server and service is checked automatically, and our engineers are alerted the moment one stops answering.
Monitoring + alertsThe voice core keeps a second, independent address on a separate network, ready if the primary path fails.
Two addressesSell numbers, calling and SIP trunks under your own brand — your customers’ calls land on our addresses and cross our backbone, the same as ours.