AS200536 SNL-127-200536 - Sunoaki
🇺🇸186526 Network
ARINassigned
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)0
Routing hygiene
Score 60/100 · High riskRPKI ROA coverage
0%
1 prefix RPKI invalid
IRR route objects
0%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (1 of 1) have no valid ROA, 1 of them RPKI invalid
- 100% of announced prefixes (1 of 1) have no IRR route object for this ASN
- Only one upstream seen in the AS paths of its routes
Based on 1 announced prefix, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Invalid | - | 2026-10-26 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 151.245.162.0/24 | 🇸🇬 SG | RIPE | assigned |
| 2a0a:6040:a900::/48 | 🇦🇶 AQ | RIPE | assigned |
All 1 announced prefix of AS200536 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS200536 hands its own prefixes to: transit providers, or peers at an exchange.
- AS21859Zenlayer1
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 AS200536 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/200536Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200536" | jq