ResearchRouting table, RPKI, IRR & looking glass

AS202891 AddSecure AB

AS202891 (MULTICOM-IOT) is registered to AddSecure AB in SE. It originates 6 prefixes in the global routing table.

5
IPv4 prefixes
1
IPv6 prefixes
2,816
IPv4 addresses
100%
RPKI valid

Who holds AS202891

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

AS number
AS202891
Handle
MULTICOM-IOT
Organization
AddSecure AB
Country
SE
ASPA
None published

What AS202891 announces

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

IPv4 prefixes
5
IPv6 prefixes
1
IPv4 addresses
2,816 (11 /24s)
RPKI valid
6 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS202891
4
With an IRR route object
6 100%

Announced prefixes

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

IPv4 (5)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS202891 is reached through

The AS just before AS202891 in the paths our looking glass collectors hold, for 6 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
RIPEMULTICOM-IOTRIPE-NCC-END-MNT, MULTICOMSECURITY-MNT

Route objects with origin AS202891: RIPE 6

as-sets that list AS202891 (2)