asn.dev

Routing security

AS267270 AS267270 - MV COMUNICACOES LTDA - ME

Unclassified LACNIC Cable/DSL/ISP

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

Announcements

What this network originates

6 observed

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

PrefixRPKIIRRVantage points
45.232.156.0/22RPKI validNo IRR53
45.232.156.0/23RPKI validNo IRR53
45.232.158.0/23RPKI validNo IRR53
2804:4ae4::/32RPKI validNo IRR29
2804:4ae4::/33RPKI validNo IRR29
2804:4ae4:8000::/33RPKI validNo IRR29

RPKI · ROAs

Route origin authorisations

2 ROAs

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

PrefixMax lengthTrust anchor
45.232.156.0/22/32LACNIC
2804:4ae4::/32/128LACNIC

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

RPKI · ASPA

Declared transit providers

3 declared

This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.

ASNetworkASPARouting paths
AS10429TELEFONICA BRASIL S.ADeclaredObserved
AS262365IBI TELECOM EIRELIDeclaredObserved
AS262737Gateway Telecom Ltda - MEDeclaredObserved

An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.

IRR

Registered route objects

0 objects · 0 not announced

Route objects naming AS267270 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.

No route objects name this AS as origin.

IRR

AS-sets

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

AS-setWhereRelationship
AS267270:AS-MVTELECOMPeeringDBDeclared by the operator as its own set
AS-268696RADBLists AS267270 as a direct member
AS-53078-CUSTALTDBLists AS267270 as a direct member
AS-53181RADBLists AS267270 as a direct member
AS-7738-BGP-CUSTOMERSRADBLists AS267270 as a direct member
AS-7738_CUSTOMERSRADBLists AS267270 as a direct member
AS-CTBC-CUSTOMERS50RADBLists AS267270 as a direct member
AS-CTBC-TOOLS-3RADBLists AS267270 as a direct member
AS-DURAND1-CUSTOMERRADBLists AS267270 as a direct member
AS-EMBRATELNETRADBLists AS267270 as a direct member
AS-HURRICANERADBLists AS267270 as a direct member
AS-SB-AUTOMATION-CUSTOMERRADBLists AS267270 as a direct member
AS-SEMPRE-CUSTOMER-262365RADBLists AS267270 as a direct member
AS-SEMPRE-CUSTOMER-268696RADBLists AS267270 as a direct member
AS-TRANSROUTE-SPECRIPELists AS267270 as a direct member
AS-TUDDO-CLIRADBLists AS267270 as a direct member
AS-UFINET-LATAM-BRASILRADBLists AS267270 as a direct member
AS-UFLA-TRANSCUSTRADBLists AS267270 as a direct member
AS262365:AS-IBITELECOMNTTCOMLists AS267270 as a direct member
AS263903:AS-TRANSITRADBLists AS267270 as a direct member
AS264409:AS-CONERADBLists AS267270 as a direct member
AS267933:AS-ZETTANTTCOMLists AS267270 as a direct member
AS52927:AS-TECNOSERVENTTCOMLists AS267270 as a direct member
AS53013:AS-CONERADBLists AS267270 as a direct member
AS61568:AS-ALOO-TELECOM-DDOSRADBLists AS267270 as a direct member

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