ResearchRouting table, RPKI, IRR & looking glass

AS41733 JSC "ER-Telecom Holding"

AS41733 (ZTELECOM-AS) is registered to JSC "ER-Telecom Holding" in RU. It originates 135 prefixes in the global routing table.

135
IPv4 prefixes
0
IPv6 prefixes
304,640
IPv4 addresses
3%
RPKI valid

Who holds AS41733

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS41733
Handle
ZTELECOM-AS
Organization
JSC "ER-Telecom Holding"
Country
RU
ASPA
None published

What AS41733 announces

Prefixes originated by AS41733 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
135
IPv6 prefixes
0
IPv4 addresses
304,640 (1,190 /24s)
RPKI valid
5 3%
RPKI invalid
0
RPKI not found
130
ROAs naming AS41733
5
With an IRR route object
51 37%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

IPv4 (135)
5.16.144.0/205.16.192.0/185.17.0.0/165.17.0.0/175.17.0.0/225.17.80.0/225.17.84.0/225.17.88.0/225.17.92.0/225.17.128.0/185.17.240.0/215.18.0.0/165.18.4.0/245.18.6.0/245.18.36.0/225.18.40.0/245.18.41.0/245.18.42.0/245.18.80.0/225.18.84.0/235.18.86.0/235.18.88.0/225.18.94.0/235.18.96.0/215.18.100.0/235.18.102.0/245.18.103.0/245.18.128.0/245.18.129.0/245.18.130.0/245.18.131.0/245.18.132.0/245.18.133.0/245.18.134.0/245.18.135.0/245.18.144.0/245.18.145.0/245.18.146.0/245.18.147.0/245.18.148.0/245.18.149.0/245.18.150.0/245.18.151.0/245.18.152.0/245.18.153.0/245.18.154.0/245.18.155.0/245.18.156.0/225.18.160.0/215.18.168.0/225.18.174.0/245.18.175.0/245.18.176.0/245.18.177.0/245.18.178.0/245.18.179.0/245.18.180.0/245.18.181.0/245.18.182.0/245.18.183.0/245.18.184.0/245.18.185.0/245.18.186.0/245.18.187.0/245.18.188.0/245.18.189.0/245.18.190.0/245.18.191.0/245.18.196.0/225.18.200.0/245.18.201.0/245.18.202.0/245.18.203.0/245.18.204.0/245.18.205.0/245.18.206.0/245.18.207.0/245.18.208.0/205.18.208.0/215.18.216.0/215.18.224.0/245.18.225.0/245.18.228.0/245.18.229.0/245.18.230.0/245.18.231.0/245.18.232.0/225.18.236.0/225.18.240.0/245.18.241.0/245.18.242.0/245.18.243.0/245.18.244.0/245.18.245.0/245.18.246.0/245.18.247.0/245.18.248.0/245.18.249.0/245.18.250.0/245.18.251.0/245.18.252.0/245.18.253.0/245.18.254.0/245.18.255.0/245.19.0.0/205.19.0.0/245.19.1.0/245.19.3.0/245.19.7.0/245.19.9.0/245.19.64.0/195.19.128.0/1737.112.248.0/2162.182.88.0/2177.244.16.0/2080.246.240.0/2083.136.240.0/2184.52.64.0/1888.204.96.0/2391.202.220.0/22
Show 15 more

RPKI valid   RPKI invalid   no ROA covers it

Who AS41733 is reached through

The AS just before AS41733 in the paths our looking glass collectors hold, for 60 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
RIPEZTELECOM-ASRIPE-NCC-END-MNT, RAID-MNT

Route objects with origin AS41733: RIPE 115

as-sets that list AS41733 (9)