ResearchRouting table, RPKI, IRR & looking glass

AS206027 Freight Link OJSC

AS206027 (FREIGHT-LINK-AS) is registered to Freight Link OJSC in RU. It originates 1 prefix in the global routing table.

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

Who holds AS206027

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

AS number
AS206027
Handle
FREIGHT-LINK-AS
Organization
Freight Link OJSC
Country
RU
ASPA
None published

What AS206027 announces

Prefixes originated by AS206027 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
0
IPv4 addresses
256 (1 /24s)
RPKI valid
0 0%
RPKI invalid
0
RPKI not found
1
ROAs naming AS206027
0
With an IRR route object
1 100%

Announced prefixes

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

IPv4 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS206027 is reached through

The AS just before AS206027 in the paths our looking glass collectors hold, for 1 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
RIPEFREIGHT-LINK-ASRIPE-NCC-END-MNT, MNT-FREIGHT-LINK

Route objects with origin AS206027: RIPE 1

as-sets that list AS206027 (9)