ResearchRouting table, RPKI, IRR & looking glass

AS41371 BiKaDa TOO

AS41371 (BIKADA) is registered to BiKaDa TOO in KZ. It originates 17 prefixes in the global routing table.

17
IPv4 prefixes
0
IPv6 prefixes
4,096
IPv4 addresses
100%
RPKI valid

Who holds AS41371

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

AS number
AS41371
Handle
BIKADA
Organization
BiKaDa TOO
Country
KZ
ASPA
1 provider

What AS41371 announces

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

IPv4 prefixes
17
IPv6 prefixes
0
IPv4 addresses
4,096 (16 /24s)
RPKI valid
17 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS41371
17
With an IRR route object
17 100%

Announced prefixes

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

Who AS41371 is reached through

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

Provider authorization

AS41371 publishes an ASPA naming this provider. Check a path.

Routing registry objects

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