AS16842 5DL-AS - 5Nines Data, LLC
🇺🇸ARINassigned
Announced Prefixes (BGP)
6total
5 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)10,240
Announced (BGP)10,240
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | ARIN | 2026-10-10 | |
| No ROA | ARIN | 2026-10-10 | |
| No ROA | ARIN | 2026-10-10 | |
| No ROA | ARIN | 2026-10-10 | |
| No ROA | ARINOther IRR | 2026-10-10 | |
| No ROA | ARINOther IRR | 2026-10-10 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 173.229.0.0/19 | 🇺🇸 US | ARIN | allocated |
| 208.66.128.0/21 | 🇺🇸 US | ARIN | allocated |
| 2607:f848::/32 | 🇺🇸 US | ARIN | allocated |
All 6 announced prefixes of AS16842 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS16842 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS16842 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS16842 in the transit part of AS paths: peers, providers or customers.
- AS4181TDS TELECOM1
ASPA
No ASPA
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS16842 should publish an ASPA object
- IPv4 transfers in the ARIN regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/16842Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/16842" | jq