bgpreport

Network · data from 2026-11-12

AS270672 EVO TECNOLOGIA

Registry name: AS270672 - MP INFORMATICA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270672, 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.
179.60.128.0/22 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 667 99% 67
179.60.128.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
179.60.128.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
179.60.130.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
179.60.130.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
179.60.129.0/24 Valid Other IRR onlyRADB, TC 666 99% 67
179.60.131.0/24 Valid Other IRR onlyRADB, TC 666 99% 67
2804:6f9c::/32 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 635 100% 68

AS-SET

AS270672's PeeringDB record names no 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 14 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR179.60.128.0/22Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR179.60.128.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR179.60.128.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR179.60.130.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR179.60.130.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR179.60.129.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR179.60.131.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:6f9c::/32Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

2804:6f9c::/33RADB, TCValid
2804:6f9c::/34RADB, TCValid
2804:6f9c:4000::/34RADB, TCValid
2804:6f9c:8000::/33RADB, TCValid
2804:6f9c:8000::/34RADB, TCValid
2804:6f9c:c000::/34RADB, TCValid

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.