ResearchRouting table, RPKI, IRR & looking glass

AS203733 BINERO TROMSO AS

AS203733 (itpartner-no) is registered to BINERO TROMSO AS in NO. It originates 3 prefixes in the global routing table.

3
IPv4 prefixes
0
IPv6 prefixes
768
IPv4 addresses
0%
RPKI valid

Who holds AS203733

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

AS number
AS203733
Handle
itpartner-no
Organization
BINERO TROMSO AS
Country
NO
ASPA
None published

What AS203733 announces

Prefixes originated by AS203733 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
768 (3 /24s)
RPKI valid
0 0%
RPKI invalid
0
RPKI not found
3
ROAs naming AS203733
0
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 AS203733 is reached through

The AS just before AS203733 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
RIPEitpartner-noRIPE-NCC-END-MNT, NO-ITPARTNER-1-MNT

Route objects with origin AS203733: RIPE 4

as-sets that list AS203733 (3)