AS48300 PIPELLC-NET Pipe Networks LLC
🇺🇸Org handle: ORG-PNL52-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
6 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)7,168
IPv6 Addresses
Allocated (RIR)1.9×10²⁵
Announced (BGP)0
Routing hygiene
Score 86/100 · High riskRPKI ROA coverage
0%
2 prefixes RPKI invalid
IRR route objects
0%
2 prefixes registered for another origin
Hijack signals
1
1 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 44/100
- 100% of announced prefixes (6 of 6) have no valid ROA, 2 of them RPKI invalid
- Announces 1 prefix that RPKI assigns to another network (possible hijack or misconfiguration)
- 100% of announced prefixes (6 of 6) have no IRR route object for this ASN
Based on 6 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-26 | |
51.241.100.0/22MOAS | Invalid | - | 2026-10-26 |
| No ROA | - | 2026-10-26 | |
| No ROA | - | 2026-10-26 | |
| Invalid | - | 2026-10-26 | |
| No ROA | - | 2026-10-26 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 89.18.52.0/22 | 🇭🇷 HR | RIPENCC | allocated |
| 2a12:bec0:400::/44 | 🇳🇱 NL | RIPE | assigned |
ASPA
No ASPA
Abuse Contact
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 AS48300 should publish an ASPA object
- IPv4 transfers in the RIPE NCC 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/48300Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48300" | jq