● AS403001 · AS-MIRAGEPeering Policy
Mirage Global Technologies LLC · AS403001 · last updated 25 September 2026
Summary
| Network | Mirage Global Technologies LLC · AS403001 |
|---|---|
| IRR as-set | AS-MIRAGE (source: ARIN) |
| General policy | Open |
| Multiple locations | Not required |
| Ratio | Not required |
| Contract | Not required |
| Suggested max-prefix for AS403001 | IPv4: 5 · IPv6: 10 |
| Locations | Chicago, IL (ORD) · Hillsboro, OR (PDX) · Strasbourg, FR (SXB) |
| 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.
Mirage Global Technologies LLCLooking Glass · mirageglobaltech.com