ResearchRouting table, RPKI, IRR & looking glass

AS35108 EMERGN AS

AS35108 (EMERGN-LV) is registered to EMERGN AS in LV. It originates 3 prefixes in the global routing table.

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

Who holds AS35108

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

AS number
AS35108
Handle
EMERGN-LV
Organization
EMERGN AS
Country
LV
ASPA
None published

What AS35108 announces

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

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

Announced prefixes

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

IPv4 (3)

RPKI valid   RPKI invalid   no ROA covers it

Who AS35108 is reached through

The AS just before AS35108 in the paths our looking glass collectors hold, for 3 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
RIPEEMERGN-LVRIPE-NCC-END-MNT, TELIALV-MNT, DATI-MNT

Route objects with origin AS35108: RIPE 3

as-sets that list AS35108 (9)