ResearchRouting table, RPKI, IRR & looking glass

AS918 IP Excess AB

AS918 (IPEX) is registered to IP Excess AB in SE. It originates 2 prefixes in the global routing table.

1
IPv4 prefixes
1
IPv6 prefixes
256
IPv4 addresses
100%
RPKI valid

Who holds AS918

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

AS number
AS918
Handle
IPEX
Organization
IP Excess AB
Country
SE
ASPA
None published

What AS918 announces

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

IPv4 prefixes
1
IPv6 prefixes
1
IPv4 addresses
256 (1 /24s)
RPKI valid
2 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS918
2
With an IRR route object
2 100%

Announced prefixes

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

IPv4 (1)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS918 is reached through

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

Provider authorization

AS918 publishes no ASPA of its own. 1 AS name it as a provider in theirs. Check a path.

The 1 ASes that name AS918 as a provider

Routing registry objects

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

Sourceas-nameMaintained by
RIPEIPEXRIPE-NCC-END-MNT, IPEX-MNT

Route objects with origin AS918: RIPE 2

as-sets that list AS918 (1)