YESONGIT NETWORK

Data as of 2026-08-16
BGP inherited
Cluster stats
Netblocks7
IPv6 4 prefixes (largest 2406:d400:1:133:203:163:223:84/128)
Cluster ID229201089
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

8 weekly snapshots · JSON
7 -1 netblocks since 2026-07-05
2026-07-05 peak 8 2026-08-16

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
203.163.223.84/32 YESONGIT NETWORK PEERINGDB ASSIGNED ● high
203.163.223.85/32 YESONGIT NETWORKS PEERINGDB ASSIGNED ● high
203.163.223.86/32 YESONGIT NETWORKING PEERINGDB ASSIGNED ● high
2406:d400:1:133:203:163:223:84/128 YESONGIT NETWORK PEERINGDB ASSIGNED ● high
2406:d400:1:133:203:163:223:85/128 YESONGIT NETWORKS PEERINGDB ASSIGNED ● high
2406:d400:1:133:203:163:223:86/128 YESONGIT NETWORKING PEERINGDB ASSIGNED ● high
2a14:67c1:a080::8888/128 YESONGIT NETWORK PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS154155 AS210634 AS213404