bgpreport

Network · data from 2026-11-12

AS270164 AS270164 - MATZANET SERVICIOS Y SISTEMAS DE COMUNICACION S.A DE C.V

Registry name: AS270164 - MATZANET SERVICIOS Y SISTEMAS DE COMUNICACION S.A DE C.V, MX · not in PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS270164, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270164, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
2806:20d:5602::/48 Invalid: origin None 39 6%low visibility 26
2806:3ea::/32 No ROA Other IRR onlyRADB 635 100% 69
168.205.7.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
185.236.181.0/24 Valid RIR databaseRADB, RIPE 666 99% 67

AS-SET

AS270164 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 20 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: origin2806:20d:5602::/48ROAs covering it name AS32098, not AS270164. If AS270164 should announce it, add a ROA for AS270164.39 of 636
Route object: none2806:20d:5602::/48No route object for it. Add a route object with origin AS270164 in the RIR database for the space.39 of 636
ROA: none2806:3ea::/32No ROA covers it. Add a ROA for AS270164, maxLength 32.635 of 636
Route object: RIR2806:3ea::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS270164 whose prefix no peer sees AS270164 announce. Many are kept on purpose (backup routes, space announced only in some places).

2806:3ea::/33RADBNo ROA
2806:3ea::/34RADBNo ROA
2806:3ea::/35RADBNo ROA
2806:3ea::/36RADBNo ROA
2806:3ea::/37RADBNo ROA
2806:3ea::/38RADBNo ROA
2806:3ea::/39RADBNo ROA
2806:3ea::/40RADBNo ROA
2806:3ea::/41RADBNo ROA
2806:3ea::/42RADBNo ROA
2806:3ea::/43RADBNo ROA
2806:3ea::/44RADBNo ROA
2806:3ea::/45RADBNo ROA
2806:3ea::/46RADBNo ROA
2806:3ea::/47RADBNo ROA
2806:3ea::/48RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.