Route FEED
RouteFEED
Cluster stats
Netblocks16
Cluster ID193383704
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
210.173.176.211/32 RouteFEED PEERINGDB ASSIGNED ● high
210.173.176.212/32 RouteFEED PEERINGDB ASSIGNED ● high
210.173.184.101/32 RouteFEED PEERINGDB ASSIGNED ● high
210.173.184.102/32 RouteFEED PEERINGDB ASSIGNED ● high
210.173.188.101/32 RouteFEED PEERINGDB ASSIGNED ● high
210.173.188.102/32 RouteFEED PEERINGDB ASSIGNED ● high
210.173.189.101/32 RouteFEED PEERINGDB ASSIGNED ● high
210.173.189.102/32 RouteFEED PEERINGDB ASSIGNED ● high
2001:7fa:7:1:0:4:5686:1/128 RouteFEED PEERINGDB ASSIGNED ● high
2001:7fa:7:1:0:4:5686:2/128 RouteFEED PEERINGDB ASSIGNED ● high
2001:7fa:7:2:0:4:5686:1/128 RouteFEED PEERINGDB ASSIGNED ● high
2001:7fa:7:2:0:4:5686:2/128 RouteFEED PEERINGDB ASSIGNED ● high
2001:7fa:7:4:0:4:5686:1/128 RouteFEED PEERINGDB ASSIGNED ● high
2001:7fa:7:4:0:4:5686:2/128 RouteFEED PEERINGDB ASSIGNED ● high
2001:7fa:7:5:0:4:5686:1/128 RouteFEED PEERINGDB ASSIGNED ● high
2001:7fa:7:5:0:4:5686:2/128 RouteFEED PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS45686