ResearchRouting table, RPKI, IRR & looking glass

AS16256 MTS PJSC

AS16256 (ReCom-AS) is registered to MTS PJSC in RU. It originates 8 prefixes in the global routing table.

8
IPv4 prefixes
0
IPv6 prefixes
12,800
IPv4 addresses
0%
RPKI valid

Who holds AS16256

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

AS number
AS16256
Handle
ReCom-AS
Organization
MTS PJSC
Country
RU
ASPA
None published

What AS16256 announces

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

IPv4 prefixes
8
IPv6 prefixes
0
IPv4 addresses
12,800 (50 /24s)
RPKI valid
0 0%
RPKI invalid
0
RPKI not found
8
ROAs naming AS16256
0
With an IRR route object
4 50%

Announced prefixes

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

Who AS16256 is reached through

The AS just before AS16256 in the paths our looking glass collectors hold, for 8 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
RIPEReCom-ASMTU-NOC, RIPE-NCC-END-MNT, MR-CENTER-MTS-MNT

Route objects with origin AS16256: RIPE 6

as-sets that list AS16256 (6)