AS197443 NET-6545 6545 HOLDINGS LLC
🇺🇸Org handle: ORG-HL413-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 68/100 · High riskRPKI ROA coverage
50%
1 prefix RPKI invalid
IRR route objects
50%
1 prefix registered for another origin
Hijack signals
1
1 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Announces 1 prefix that RPKI assigns to another network (possible hijack or misconfiguration)
- 50% of announced prefixes (1 of 2) have no valid ROA, 1 of them RPKI invalid
- Only one upstream seen in the AS paths of its routes
- 50% of announced prefixes (1 of 2) have no IRR route object for this ASN
Based on 2 announced prefixes, updated daily (2026-10-26). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
153.76.6.0/24MOAS | Invalid | - | 2026-10-26 |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a06:9801:743::/48 | 🇺🇸 US | RIPE | assigned |
All 2 announced prefixes of AS197443 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS197443 hands its own prefixes to: transit providers, or peers at an exchange.
- AS835GoCodeIT2
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 AS197443 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/197443Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/197443" | jq