About
Crestline Networks operates Autonomous System AS396015 (Crestline Networks) in ARIN. Find records on PeeringDB.
Announcements
- IPv6:
2602:81c:4000::/44 - IPv6:
2602:81c:4000::/48 - IPv6:
2602:81c:4001::/48
Routing Architecture
Crestline Networks uses a geographically distributed failover topology. The announcement structure is:
- Supernet:
2602:81c:4000::/44— announced from both edge locations for failover resilience. If a site's specific prefix is withdrawn, traffic routes to this supernet at the alternative location. - Site-specific /48s:
- EWR (New Jersey):
2602:81c:4000::/48 - LAX (Los Angeles):
2602:81c:4001::/48
- EWR (New Jersey):
More-specific routes (the /48s) are preferred by default routing. When a site performs maintenance or fails, its /48 can be selectively withdrawn while the supernet remains active, routing traffic through the alternative site.
Locations
| Name | City | Region | Country |
|---|---|---|---|
| Vultr EWR | New Jersey | NJ | US |
| Vultr LAX | Los Angeles | CA | US |
Measurement & Diagnostics
A looking glass (bird-lg-go) is available for live BGP and traceroute queries from our edge routers.
It is IPv6-only by design — there is deliberately no A record for this service.
We run RIPE Atlas software probes, hosted at our EWR and LAX PoPs, for independent third-party measurement of latency and reachability. Each probe reports from Vultr's (AS20473) address space at that PoP, not from an AS396015-announced prefix.
- Vultr EWR: Probe #1016787
- Vultr LAX: Probe #1016788
Contacts
- NOC: noc@as396015.com
- Peering: peering@as396015.com
- Abuse: abuse@as396015.com