bgpreport

Network · data from 2026-11-12

AS263435 AS263435 - MAIS NET TECNOLOGIA INTEGRADA

Registry name: AS263435 - MAIS NET TECNOLOGIA INTEGRADA, BR · not in PeeringDB

13IPv4 routes 100.0% RPKI valid · 100.0% with a route object
9IPv6 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 AS263435, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263435, 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.
170.80.130.0/23 Valid Other IRR onlyRADB 671 100% 67
170.80.130.0/24 Valid Other IRR onlyRADB 668 99% 67
170.80.131.0/24 Valid Other IRR onlyRADB 668 99% 67
170.80.128.0/23 Valid Other IRR onlyRADB 667 99% 67
170.80.129.0/24 Valid Other IRR onlyRADB 667 99% 67
177.67.92.0/23 Valid Other IRR onlyRADB 667 99% 67
177.67.94.0/23 Valid Other IRR onlyRADB 667 99% 67
177.67.94.0/24 Valid Other IRR onlyRADB 667 99% 67
177.67.95.0/24 Valid Other IRR onlyRADB 667 99% 67
170.80.128.0/24 Valid Other IRR onlyRADB 665 99% 67
177.67.92.0/22 Valid Other IRR onlyRADB 665 99% 67
177.67.92.0/24 Valid Other IRR onlyRADB 665 99% 67
177.67.93.0/24 Valid Other IRR onlyRADB 665 99% 67
2804:11bc:c000::/38 Valid Other IRR onlyRADB 634 100% 69
2804:11bc:c000::/39 Valid Other IRR onlyRADB 634 100% 69
2804:11bc:c200::/39 Valid Other IRR onlyRADB 634 100% 69
2804:11bc:4000::/39 Valid Other IRR onlyRADB 631 99% 69
2804:11bc:4200::/39 Valid Other IRR onlyRADB 631 99% 69
2804:11bc:8000::/38 Valid Other IRR onlyRADB 631 99% 69
2804:11bc:8000::/39 Valid Other IRR onlyRADB 631 99% 67
2804:11bc:8200::/39 Valid Other IRR onlyRADB 631 99% 67
2804:11bc:4000::/38 Valid Other IRR onlyRADB 630 99% 69

AS-SET

AS263435 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 28 are in fix.csv.

  • Route object: RIR22
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR170.80.130.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.80.130.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR170.80.131.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR170.80.128.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR170.80.129.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.67.92.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.67.94.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.67.94.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.67.95.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR170.80.128.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR177.67.92.0/22Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR177.67.92.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR177.67.93.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:11bc:c000::/38Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:11bc:c000::/39Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:11bc:c200::/39Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:11bc:4000::/39Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:11bc:4200::/39Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:11bc:8000::/38Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:11bc:8000::/39Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:11bc:8200::/39Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:11bc:4000::/38Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

170.80.128.0/22RADBValid
2804:11bc::/32RADBValid
2804:11bc:8000::/40RADBValid
2804:11bc:8100::/40RADBValid
2804:11bc:8200::/40RADBValid
2804:11bc:8300::/40RADBValid

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.