ResearchRouting table, RPKI, IRR & looking glass

AS8263 PJSC MegaFon

AS8263 (Cloud-Megafon) is registered to PJSC MegaFon in RU. It originates 3 prefixes in the global routing table.

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

Who holds AS8263

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

AS number
AS8263
Handle
Cloud-Megafon
Organization
PJSC MegaFon
Country
RU
ASPA
None published

What AS8263 announces

Prefixes originated by AS8263 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
3 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS8263
3
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 AS8263 is reached through

The AS just before AS8263 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
RIPECloud-MegafonMEGAFON-RIPE-MNT, MF-MOSCOW-MNT, RIPE-NCC-END-MNT

Route objects with origin AS8263: RIPE 4

as-sets that list AS8263 (3)