asn.dev

Routing security

AS42632 MNOGOBYTE-AS Moscow, Russia

Hosting RIPE Content

RPKI valid 100% 39 of 39 announcements
RPKI invalid 0 none
No ROA 0 not covered by any ROA
IRR registered 100% 0 missing · 0 other origin
ROAs 39 authorising this AS

Announcements

What this network originates

39 observed

Every prefix observed with AS42632 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
2a02:878:1::/48RPKI validIRR covering30
2a02:878:2::/48RPKI validIRR covering30
2a02:878:a::/48RPKI validIRR covering30
2a02:878:a80e::/48RPKI validIRR covering30
2a02:878:a801::/48RPKI validIRR30
77.220.160.0/23RPKI validIRR covering51
77.220.164.0/22RPKI validIRR16
77.220.164.0/23RPKI validIRR15
77.220.166.0/23RPKI validIRR13
77.220.168.0/22RPKI validIRR16
77.220.168.0/23RPKI validIRR13
77.220.170.0/23RPKI validIRR51
77.220.172.0/23RPKI validIRR51
77.220.174.0/23RPKI validIRR51
77.220.176.0/21RPKI validIRR51
77.220.184.0/21RPKI validIRR51
83.222.96.0/22RPKI validIRR51
83.222.100.0/22RPKI validIRR51
83.222.104.0/22RPKI validIRR51
83.222.108.0/22RPKI validIRR51
83.222.112.0/22RPKI validIRR51
83.222.116.0/22RPKI validIRR51
146.255.192.0/22RPKI validIRR51
146.255.192.0/23RPKI validIRR51
146.255.194.0/23RPKI validIRR51
146.255.196.0/24RPKI validIRR51
146.255.197.0/24RPKI validIRR52
146.255.198.0/23RPKI validIRR52
146.255.198.0/24RPKI validIRR52
146.255.199.0/24RPKI validIRR covering52
146.255.200.0/24RPKI validIRR51
146.255.201.0/24RPKI validIRR17
176.58.32.0/22RPKI validIRR51
176.58.36.0/23RPKI validIRR15
212.76.128.0/21RPKI validIRR51
212.76.136.0/21RPKI validIRR51
212.76.144.0/22RPKI validIRR51
212.76.152.0/22RPKI validIRR51
212.76.156.0/22RPKI validIRR51

RPKI · ROAs

Route origin authorisations

39 ROAs

Signed statements by address holders that AS42632 may originate these prefixes, up to the maximum length shown.

PrefixMax lengthTrust anchor
77.220.160.0/23/23RIPENCC
77.220.164.0/22/23RIPENCC
77.220.166.0/23/23RIPENCC
77.220.168.0/22/23RIPENCC
77.220.168.0/23/23RIPENCC
77.220.172.0/23/23RIPENCC
77.220.174.0/23/23RIPENCC
77.220.176.0/21/24RIPENCC
77.220.180.0/24/24RIPENCC
77.220.184.0/21/21RIPENCC
83.222.96.0/22/22RIPENCC
83.222.100.0/22/22RIPENCC
83.222.104.0/22/22RIPENCC
83.222.108.0/22/22RIPENCC
83.222.112.0/22/22RIPENCC
83.222.116.0/22/22RIPENCC
146.255.192.0/22/23RIPENCC
146.255.192.0/23/23RIPENCC
146.255.196.0/24/24RIPENCC
146.255.197.0/24/24RIPENCC
146.255.198.0/23/24RIPENCC
146.255.200.0/23/23RIPENCC
146.255.200.0/24/24RIPENCC
146.255.201.0/24/24RIPENCC
176.58.32.0/22/23RIPENCC
176.58.36.0/23/23RIPENCC
176.58.40.0/24/24RIPENCC
176.58.62.0/23/23RIPENCC
212.76.128.0/21/23RIPENCC
212.76.136.0/21/23RIPENCC
212.76.144.0/22/22RIPENCC
212.76.152.0/22/24RIPENCC
212.76.156.0/22/22RIPENCC
2a02:878:1::/48/48RIPENCC
2a02:878:2::/48/48RIPENCC
2a02:878:a::/48/48RIPENCC
2a02:878:10::/48/48RIPENCC
2a02:878:a801::/48/48RIPENCC
2a02:878:a80e::/48/48RIPENCC

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

52 objects · 19 not announced

Route objects naming AS42632 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.

PrefixSourceDescriptionMaintainerChangedRouting
77.220.160.0/22RIPEMnogoByte customers' areaMNT-MBNET2010-05-31Not announced
77.220.168.0/21RIPEMnogoByte ColocationMNT-MBNET2007-06-05Not announced
77.220.172.0/22RIPEMB ColoMNT-MBNET2007-03-27Not announced
77.220.176.0/20RIPEMnogoByte backup routeMNT-MBNET2012-07-04Not announced
77.220.176.0/22RIPEMnogoByte ColocationMNT-MBNET2007-08-17Not announced
77.220.184.0/22RIPEMnogoByte ColocationMNT-MBNET2007-09-26Not announced
77.220.188.0/22RIPEMnogoByte data-centre servicesMNT-MBNET2010-04-21Not announced
83.222.96.0/21RIPEMnogoByte backup routeMNT-MBNET2012-08-22Not announced
83.222.104.0/21RIPEMnogoByte data-centre servicesMNT-MBNET2009-09-16Not announced
83.222.112.0/21RIPEMnogoByte data-centre servicesMNT-MBNET2009-12-22Not announced
146.255.196.0/23RIPEMnogoByte data-centre servicesMNT-MBNET2011-10-27Not announced
146.255.200.0/23RIPEMnogoByte customers' areaMNT-MBNET2012-06-25Not announced
176.58.32.0/24RIPEMnogoByte data-centre servicesMNT-MBNET2012-03-19Not announced
176.58.33.0/24RIPEMnogoByte data-centre servicesMNT-MBNET2012-03-19Not announced
176.58.59.0/24RIPEMnogoByteMNT-MBNET2026-10-08Not announced
176.58.62.0/23RIPE—MNT-MBNET2020-11-02Not announced
212.76.153.0/24RIPEMnogoByteMNT-MBNET2015-01-16Not announced
2a02:878::/32RIPEMnogoByte LLCMNT-MBNET2012-05-29Not announced
2a02:878:a806::/48RIPEMnogoByte data-centre servicesMNT-MBNET2013-09-18Not announced
77.220.164.0/22RIPEMnogoByte data-centre servicesMNT-MBNET2011-01-13Announced
77.220.164.0/23RIPEMnogobyte customers areaMNT-MBNET2007-03-27Announced
77.220.166.0/23RIPEMnogoByteMNT-MBNET2014-02-03Announced
77.220.168.0/22RIPEMnoboByte LLCMNT-MBNET2007-05-02Announced
77.220.168.0/23RIPEMnogoByteMNT-MBNET2014-02-14Announced
77.220.170.0/23RIPEMnogoByteMNT-MBNET2014-02-10Announced
77.220.172.0/23RIPE—MNT-MBNET2018-02-19Announced
77.220.174.0/23RIPEMnogoByteMNT-MBNET2014-02-14Announced
77.220.176.0/21RIPEMnogoByte backup routeMNT-MBNET2012-07-04Announced
77.220.184.0/21RIPEMnogoByteMNT-MBNET2014-02-03Announced
83.222.96.0/22RIPEMnogoByte ColocationMNT-MBNET2009-02-13Announced
83.222.100.0/22RIPEMnogoByte data-centre servicesMNT-MBNET2010-04-13Announced
83.222.104.0/22RIPEMnogoByte backup routeMNT-MBNET2012-08-22Announced
83.222.108.0/22RIPEMnogoByte backup routeMNT-MBNET2012-08-22Announced
83.222.112.0/22RIPEMnogoByte backup routeMNT-MBNET2012-08-22Announced
83.222.116.0/22RIPEMnogoByte backup routeMNT-MBNET2012-08-22Announced
146.255.192.0/22RIPEMnogoByte data-centre servicesMNT-MBNET2011-10-10Announced
146.255.192.0/23RIPEMnogoByteMNT-MBNET2014-04-16Announced
146.255.194.0/23RIPEMnogoByteMNT-MBNET2014-04-16Announced
146.255.196.0/24RIPEMnogoByte data-centre servicesMNT-MBNET2012-07-02Announced
146.255.197.0/24RIPEMnogoByte customers' areaMNT-MBNET2012-07-02Announced
146.255.198.0/23RIPEMnogoByte data-centre servicesMNT-MBNET2011-12-23Announced
146.255.198.0/24RIPEMnogoByteMNT-MBNET2026-10-08Announced
146.255.200.0/24RIPEMnogoByte customers' areaMNT-MBNET2012-06-25Announced
146.255.201.0/24RIPEMnogoByte data-centre servicesMNT-MBNET2021-04-27Announced
176.58.32.0/22RIPEMnogoByte data-centre servicesMNT-MBNET2013-07-26Announced
176.58.36.0/23RIPEMnogoByte data-centre servicesMNT-MBNET2015-11-13Announced
212.76.128.0/21RIPEMnogoByte data-centre servicesMNT-MBNET2010-01-18Announced
212.76.136.0/21RIPEMnogoByte data-centre servicesMNT-MBNET2010-04-21Announced
212.76.144.0/22RIPEMnogoByte servicesMNT-MBNET2011-05-04Announced
212.76.152.0/22RIPEMnogoByte data-centre servicesMNT-MBNET2011-01-13Announced
212.76.156.0/22RIPEMnogoByte data-centre servicesMNT-MBNET2011-01-13Announced
2a02:878:a801::/48RIPEMnogoByte data-centre servicesMNT-MBNET2013-09-18Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS42632 directly show who expects to carry it.

AS-setWhereRelationship
AS-MNOGOBYTEPeeringDBDeclared by the operator as its own set
AS-BLOCK-SETRIPELists AS42632 as a direct member
AS-BLOCKED-RURIPELists AS42632 as a direct member
AS-COMCORRIPELists AS42632 as a direct member
AS-COMCOR-EURIPELists AS42632 as a direct member
AS-COMCOR-STKRIPELists AS42632 as a direct member
AS-MNOGOBYTERIPELists AS42632 as a direct member
AS-TRANSROUTE-MNOGOBYTERIPELists AS42632 as a direct member
AS203391:AS-UPSTREAMSRADBLists AS42632 as a direct member
AS203391:AS-UPSTREAMSRIPELists AS42632 as a direct member
AS3491:AS-CUSTOMERS-EURADBLists AS42632 as a direct member

RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.