bgpreport

Network · data from 2026-11-12

AS268135 INTERPLUS TECNLOGIA

Registry name: AS268135 - INTERPLUS TECNLOGIA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
2Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS268135, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268135, 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.

45.170.4.0/24 Valid Other IRR onlyRADB 672 100% 67
45.170.5.0/24 Valid Other IRR onlyRADB 672 100% 67
45.170.6.0/24 Valid Other IRR onlyRADB 670 100% 67
45.170.7.0/24 Valid Other IRR onlyRADB 670 100% 67
45.170.4.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
2804:588c::/32 Valid Other IRR onlyRADB, TC 636 100% 67
2804:588c::/33 Valid Other IRR onlyRADB 636 100% 67
2804:588c:8000::/33 Valid Other IRR onlyRADB 636 100% 67
45.170.4.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
45.170.6.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS268135'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 17 are in fix.csv.

  • Route object: RIR10
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: RIR45.170.4.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.170.5.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.170.6.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.170.7.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.170.4.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:588c::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:588c::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:588c:8000::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR45.170.4.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR45.170.6.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2804:588c::/34RADBValid
2804:588c::/35RADBValid
2804:588c::/36RADBValid
2804:588c::/37RADBValid
2804:588c::/38RADBValid
2804:588c::/39RADBValid
2804:588c::/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.