Sakarin Network

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks5
IPv6 5 prefixes (largest 2a0e:4005:ff12::/48)
Cluster ID214577235
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
2602:f92a:1315:2::94/128 SAKARIN-NETWORK PEERINGDB ASSIGNED ● medium
2a0e:4005:ff12::/48 SAKARIN-NETWORK BGP ANNOUNCED ● medium
2a0e:4005:ff41::/48 SAKARIN-NETWORK BGP ANNOUNCED ● medium
2a14:7583:efff::/48 SAKARIN-NETWORK BGP ANNOUNCED ● medium
2a0e:8f01:1000:16::14b/128 Sakarin Network PEERINGDB ASSIGNED ● low

IPv6 ranges (5)

Network trust

what's this?
RPKI hygiene: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (4 of 5)
Possible discrepancies (3)

These blocks are registered to Sakarin Network but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a14:7583:efff::/48 /48 authorized for AS14618 — Amazon.com, Inc.
2a0e:4005:ff12::/48 /48 authorized for AS219378 — ZHANG XIYUAN
2a0e:4005:ff41::/48 /48 authorized for AS219378 — ZHANG XIYUAN

NIC Handles

AS219378 AS219378 MNT-DGTL SAKARIN-MNT