AS34087

NTE TELEKOM AS
CAIDA
Primary org cluster
NTE TELEKOM AS
42
Announced prefixes
25
RPKI-authorized prefixes

Prefixes

showing 1–42 of 42
CIDR Org name Source Confidence
80.249.213.73/32 NTE TELEKOM AS PEERINGDB 1.00
84.16.192.0/19 NTE TELEKOM AS BGP 1.00
84.16.197.128/26 NTE TELEKOM AS BGP 1.00
84.52.192.0/18 NTE TELEKOM AS BGP 1.00
84.52.224.0/19 NTE TELEKOM AS BGP 1.00
85.89.0.0/19 NTE TELEKOM AS BGP 1.00
89.151.192.0/19 NTE TELEKOM AS BGP 1.00
89.151.224.0/19 NTE TELEKOM AS BGP 1.00
91.198.176.56/32 NTE TELEKOM AS PEERINGDB 1.00
94.246.0.0/18 NTE TELEKOM AS BGP 1.00
148.252.64.0/18 NTE TELEKOM AS BGP 1.00
148.252.64.0/19 NTE TELEKOM AS BGP 1.00
148.252.96.0/19 NTE TELEKOM AS BGP 1.00
152.65.0.0/19 NTE TELEKOM AS BGP 1.00
152.65.32.0/19 NTE TELEKOM AS BGP 1.00
152.65.64.0/19 NTE TELEKOM AS BGP 1.00
152.65.96.0/19 NTE TELEKOM AS BGP 1.00
178.164.0.0/19 NTE TELEKOM AS BGP 1.00
178.164.0.0/17 NTE TELEKOM AS BGP 1.00
178.164.32.0/19 NTE TELEKOM AS BGP 1.00
178.164.64.0/19 NTE TELEKOM AS BGP 1.00
178.164.96.0/19 NTE TELEKOM AS BGP 1.00
185.1.55.11/32 NTE TELEKOM AS PEERINGDB 1.00
185.1.65.171/32 NTE TELEKOM AS PEERINGDB 1.00
185.161.56.0/22 NTE TELEKOM AS BGP 1.00
185.161.56.0/24 NTE TELEKOM AS BGP 1.00
185.161.57.0/24 NTE TELEKOM AS BGP 1.00
185.161.57.128/28 NTE TELEKOM AS BGP 1.00
185.161.57.208/28 NTE TELEKOM AS BGP 1.00
185.161.57.224/28 NTE TELEKOM AS BGP 1.00
192.121.80.75/32 NTE TELEKOM AS PEERINGDB 1.00
195.66.226.201/32 NTE TELEKOM AS PEERINGDB 1.00
217.168.80.0/20 NTE TELEKOM AS BGP 1.00
2001:678:464::/48 NTE TELEKOM AS BGP 1.00
2001:7f8:1::a503:4087:1/128 NTE TELEKOM AS PEERINGDB 1.00
2001:7f8:4::8527:1/128 NTE TELEKOM AS PEERINGDB 1.00
2001:7f8:12:1::3:4087/128 NTE TELEKOM AS PEERINGDB 1.00
2001:7f8:12:3::3:4087/128 NTE TELEKOM AS PEERINGDB 1.00
2001:7f8:3e:0:a500:3:4087:1/128 NTE TELEKOM AS PEERINGDB 1.00
2001:7f8:41:0:1:34:87:1/128 NTE TELEKOM AS PEERINGDB 1.00
2a01:560::/32 NTE TELEKOM AS BGP 1.00
2a01:560::/29 NTE TELEKOM AS BGP 1.00
← Previous Next →

RPKI-authorized prefixes (ROAs)

what's this?

Uses the REST API.