AS31133 ASPA — MF MGSM PJSC MegaFon Upstream Provider Authorization
MF-MGSM-AS PJSC MegaFon🇷🇺
AS31133 has not published its own ASPA object, but 6 ASNs list it as an authorized upstream provider.
Peering Topology
Downstream Customers(6)
These ASNs list AS31133 as an authorized upstream provider.
| ASN | Name |
|---|---|
| AS31257 | 🇷🇺ORIONNET-KRK Orion Telecom LLC |
| AS35168 | 🇰🇿TNS-Plus-Core TNS-Plus LLP |
| AS50045 | 🇷🇺MONNET-AS PJSC Montazh |
| AS50427 | 🇷🇺ORIONNET-ABK Orion Telecom LLC |
| AS59600 | 🇷🇺ATLAS-TELECOM-AS United Communication Systems Tambov LLC |
| AS197068 | 🇷🇺CURATOR HLL LLC |
About ASPA - what it is and why AS31133 should publish one
ASPA (Autonomous System Provider Authorization) is a cryptographically signed RPKI object specified in the IETF draft-ietf-sidrops-aspa-profile that lets an AS declare which upstream networks are authorized to carry its traffic. Together with route origin validation (ROV), ASPA enables BGP route leak detection: routers can reject paths that traverse an unauthorized provider, which is one of the most common causes of large-scale internet outages.
AS31133 (MF-MGSM-AS PJSC MegaFon) has not yet published an ASPA object. Publishing one is free, takes a few minutes in your RIR portal, and strengthens the routing security posture of every network that depends on you. If you only buy transit from well-known upstreams, the record is usually a short list of their ASNs.
Create an ASPA object: RIPE Portal · ARIN RPKI · APNIC MyAPNIC · ipctl.io RPKI & ROA tools
Related Tools
- RPKI & ROA Lookup — validate prefixes and check ASPA records for any ASN
- Global ASPA Adoption Statistics — transit-free ASNs, top upstream providers, adoption trends
- AS31133 Overview — prefixes, BGP routes, peers, and RPKI status