● AS403001 · AS-MIRAGEPeering Policy
Mirage Global Technologies LLC · AS403001 · last updated 30 October 2026
Summary
| Network | Mirage Global Technologies LLC · AS403001 |
|---|---|
| IRR as-set | AS-MIRAGE (source: ARIN) |
| Prefixes originated | IPv4: 23.165.12.0/24 · 156.9.216.0/22 · regional /24s: 156.9.216.0/24 (Chicago), 156.9.217.0/24 (Frankfurt, Düsseldorf), 156.9.218.0/24 (London), 156.9.219.0/24 (Amsterdam) — IPv6: 2602:f2d3::/40 · more-specifics: 2602:f2d3::/48 (anycast), 2602:f2d3:10::/44 (US), 2602:f2d3:20::/44 (EU), regional /48s: 2602:f2d3:12::/48 (Toronto), 2602:f2d3:13::/48 (New York), 2602:f2d3:14::/48 (Kansas City), 2602:f2d3:15::/48 (Fremont), 2602:f2d3:22::/48 (Düsseldorf), 2602:f2d3:23::/48 (London), 2602:f2d3:24::/48 (Amsterdam), 2602:f2d3:25::/48 (Milan) |
| Routing security | RPKI ROAs for every announced prefix · ASPA published (providers AS6517, AS6939, AS20473, AS34872, AS34927, AS52025, AS215296) · route/route6 objects in the ARIN IRR · RPKI-invalid routes rejected |
| Upstreams (IP transit) | AS6939 Hurricane Electric (IPv6 at LocIX Frankfurt, LONAP London, nine-ix and Frys-IX Amsterdam and ONIX Toronto; IPv4 peering at LONAP, nine-ix, Frys-IX and ONIX) · AS34872 Servperso (Düsseldorf) · AS20473 Vultr (Chicago, Frankfurt) · AS34927 iFog (Toronto) · AS52025 GetVPS (London) · AS215296 LowPing (Amsterdam) · AS6517 LakeNetworks (Milan) |
| Internet exchanges | LocIX Frankfurt (AS202409) · 1G via Düsseldorf · IPv6 2001:7f8:f2:e1:a5:40:3001:1 · IPv4 185.1.166.96 · route servers: yes · Cloudflare (AS13335, direct IPv4 + IPv6) · Hetzner (AS24940, direct IPv4 + IPv6) · M-TELECOM (AS214172, direct IPv6) · LocIX Düsseldorf (AS202409) · 1G · IPv6 2a0c:b641:701:0:a5:40:3001:1 · IPv4 185.1.155.168 · route servers: yes · ONIX Toronto (AS57369) · 1G · IPv6 2001:504:125:e1::160 · IPv4 149.112.50.160 · route servers: yes · Hurricane Electric (IPv6 transit + IPv4 peering) · LONAP London (AS8550) · 1G · IPv6 2001:7f8:17::6:2639:1 · IPv4 5.57.82.159 · route servers: yes · Hurricane Electric (IPv4 peering + IPv6 transit) · Apple (AS714, direct IPv4 + IPv6) · Init7 (AS13030, direct IPv4 + IPv6) · nine-ix Amsterdam (AS31561) · IPv6 2001:7f8:12e::40:3001:1 · IPv4 185.1.14.208 · route servers: yes · Hurricane Electric (IPv6 transit + IPv4 peering) · Frys-IX Amsterdam (AS56393) · IPv6 2001:7f8:10f::6:2639:350 · IPv4 185.1.161.95 · route servers: yes · Hurricane Electric (IPv6 transit + IPv4 peering) · PeeringDB |
| General policy | Open |
| Multiple locations | Not required |
| Ratio | Not required |
| Contract | Not required |
| Suggested max-prefix for AS403001 | IPv4: 10 · IPv6: 20 (as in PeeringDB) |
| Locations | Chicago, IL (ORD) · New York, NY (JFK) · Kansas City, MO (MCI) · Fremont, CA (FMT) · Hillsboro, OR (PDX) · Frankfurt, DE (FRA) · Düsseldorf, DE (DUS) · Toronto, ON (YYZ) · London, GB (LCY) · Amsterdam, NL (AMS) · Milan, IT (LIN) · Strasbourg, FR (SXB) · Sydney, AU (SYD) |
| Peering / NOC contact | noc@mirageglobaltech.com |
| Abuse | abuse@mirageglobaltech.com |
Requirements
- A public ASN with an up-to-date PeeringDB record.
- Route objects registered in an IRR, reachable through the as-set you give us.
- Announcements must be RPKI-valid or not-found; RPKI-invalid routes are rejected.
- No bogons, no private ASNs in the AS path, no default route, no prefixes more specific than /24 (IPv4) or /48 (IPv6).
- A reachable NOC contact, and prompt action on security or abuse reports.
- MD5 or TCP-AO session authentication on request.
How to request peering
- Email noc@mirageglobaltech.com with your ASN, as-set, peering location and session addresses.
- Check our routing from the looking glass and our PeeringDB record.
MGT — Mirage Global Technologies LLC · noc@mirageglobaltech.comLooking Glass · mirageglobaltech.com