AS49544
i3D.net B.V
CAIDA
Primary org cluster
i3D.net B.V
392
Announced prefixes
50
RPKI-authorized prefixes

Prefixes

showing 1–100 of 392
CIDR Org name Source Confidence
5.57.81.25/32 i3D.net B.V PEERINGDB 1.00
5.180.216.0/23 i3D.net B.V BGP 1.00
5.180.218.0/23 i3D.net B.V BGP 1.00
5.200.0.0/19 i3D.net B.V BGP 1.00
5.200.5.0/24 i3D.net B.V BGP 1.00
5.200.31.0/24 i3D.net B.V BGP 1.00
27.111.229.225/32 i3D.net B.V PEERINGDB 1.00
31.204.128.0/19 i3D.net B.V BGP 1.00
31.204.132.0/22 i3D.net B.V BGP 1.00
31.204.136.0/23 i3D.net B.V BGP 1.00
31.204.140.0/22 i3D.net B.V BGP 1.00
31.204.144.0/24 i3D.net B.V BGP 1.00
31.204.145.0/24 i3D.net B.V BGP 1.00
31.204.156.0/23 i3D.net B.V BGP 1.00
36.255.56.159/32 i3D.net B.V PEERINGDB 1.00
37.49.237.230/32 i3D.net B.V PEERINGDB 1.00
43.239.136.0/22 i3D.net B.V BGP 1.00
45.68.16.144/32 i3D.net B.V PEERINGDB 1.00
45.68.92.58/32 i3D.net B.V PEERINGDB 1.00
45.127.172.94/32 i3D.net B.V PEERINGDB 1.00
45.147.87.0/24 i3D.net B.V BGP 1.00
45.149.251.0/24 i3D.net B.V BGP 1.00
45.153.18.0/23 i3D.net B.V BGP 1.00
62.69.146.31/32 i3D.net B.V PEERINGDB 1.00
64.191.233.99/32 i3D.net B.V PEERINGDB 1.00
66.22.196.0/22 i3D.net B.V BGP 1.00
66.22.200.0/22 i3D.net B.V BGP 1.00
66.22.204.0/22 i3D.net B.V BGP 1.00
66.22.208.0/22 i3D.net B.V BGP 1.00
66.22.212.0/22 i3D.net B.V BGP 1.00
66.22.218.0/23 i3D.net B.V BGP 1.00
66.22.220.0/23 i3D.net B.V BGP 1.00
66.22.222.0/23 i3D.net B.V BGP 1.00
66.22.224.0/23 i3D.net B.V BGP 1.00
66.22.226.0/23 i3D.net B.V BGP 1.00
66.22.230.0/24 i3D.net B.V BGP 1.00
66.22.231.0/24 i3D.net B.V BGP 1.00
66.22.232.0/24 i3D.net B.V BGP 1.00
66.22.233.0/24 i3D.net B.V BGP 1.00
66.22.234.0/24 i3D.net B.V BGP 1.00
66.22.235.0/24 i3D.net B.V BGP 1.00
66.22.236.0/24 i3D.net B.V BGP 1.00
66.22.237.0/24 i3D.net B.V BGP 1.00
66.22.238.0/24 i3D.net B.V BGP 1.00
66.22.240.0/24 i3D.net B.V BGP 1.00
66.22.241.0/24 i3D.net B.V BGP 1.00
66.22.242.0/24 i3D.net B.V BGP 1.00
66.22.243.0/24 i3D.net B.V BGP 1.00
66.22.244.0/24 i3D.net B.V BGP 1.00
66.22.245.0/24 i3D.net B.V BGP 1.00
66.22.246.0/24 i3D.net B.V BGP 1.00
66.22.248.0/24 i3D.net B.V BGP 1.00
80.81.194.107/32 i3D.net B.V PEERINGDB 1.00
80.97.248.66/32 i3D.net B.V PEERINGDB 1.00
80.249.208.162/32 i3D.net B.V PEERINGDB 1.00
86.104.125.154/32 i3D.net B.V PEERINGDB 1.00
89.46.144.171/32 i3D.net B.V PEERINGDB 1.00
89.104.160.0/21 i3D.net B.V BGP 1.00
89.104.168.0/23 i3D.net B.V BGP 1.00
89.104.170.0/23 i3D.net B.V BGP 1.00
89.104.172.0/22 i3D.net B.V BGP 1.00
89.104.176.0/23 i3D.net B.V BGP 1.00
89.104.178.0/23 i3D.net B.V BGP 1.00
89.104.180.0/24 i3D.net B.V BGP 1.00
89.104.181.0/24 i3D.net B.V BGP 1.00
91.194.218.15/32 i3D.net B.V PEERINGDB 1.00
91.195.234.0/23 i3D.net B.V BGP 1.00
91.206.53.28/32 i3D.net B.V PEERINGDB 1.00
91.210.16.59/32 i3D.net B.V PEERINGDB 1.00
91.212.235.16/32 i3D.net B.V PEERINGDB 1.00
91.216.207.0/24 i3D.net B.V BGP 1.00
91.221.208.0/24 i3D.net B.V BGP 1.00
91.233.67.0/24 i3D.net B.V BGP 1.00
101.203.74.61/32 i3D.net B.V PEERINGDB 1.00
101.203.78.48/32 i3D.net B.V PEERINGDB 1.00
101.203.88.121/32 i3D.net B.V PEERINGDB 1.00
103.16.102.158/32 i3D.net B.V PEERINGDB 1.00
103.26.69.93/32 i3D.net B.V PEERINGDB 1.00
103.41.12.45/32 i3D.net B.V PEERINGDB 1.00
103.159.122.0/23 i3D.net B.V BGP 1.00
103.194.164.0/22 i3D.net B.V BGP 1.00
103.203.158.142/32 i3D.net B.V PEERINGDB 1.00
103.231.152.143/32 i3D.net B.V PEERINGDB 1.00
103.247.139.38/32 i3D.net B.V PEERINGDB 1.00
104.153.84.0/22 i3D.net B.V BGP 1.00
109.200.192.0/19 i3D.net B.V BGP 1.00
109.200.194.0/23 i3D.net B.V BGP 1.00
109.200.198.0/23 i3D.net B.V BGP 1.00
109.200.208.0/22 i3D.net B.V BGP 1.00
109.200.212.0/22 i3D.net B.V BGP 1.00
109.200.220.0/22 i3D.net B.V BGP 1.00
123.255.92.15/32 i3D.net B.V PEERINGDB 1.00
130.254.64.0/19 i3D.net B.V BGP 1.00
130.254.80.0/23 i3D.net B.V BGP 1.00
130.254.84.0/23 i3D.net B.V BGP 1.00
130.254.88.0/23 i3D.net B.V BGP 1.00
130.254.90.0/23 i3D.net B.V BGP 1.00
138.128.136.0/22 i3D.net B.V BGP 1.00
138.128.140.0/22 i3D.net B.V BGP 1.00
146.247.72.0/22 i3D.net B.V BGP 1.00
← Previous Next →

RPKI-authorized prefixes (ROAs)

what's this?

Uses the REST API.