bgpreport

Network · data from 2026-11-12

AS266271 INTERAGE TELECOMUNICACOES E INFORMATICA

Registry name: AS266271 - INTERAGE TELECOMUNICACOES E INFORMATICA LTDA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266271, 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.78.48.0/24 Valid Nonecovered by 170.78.48.0/23 672 100% 66
170.78.49.0/24 Valid Nonecovered by 170.78.48.0/23 672 100% 66
170.78.50.0/24 Valid Nonecovered by 170.78.48.0/22 672 100% 66
170.78.51.0/24 Valid Nonecovered by 170.78.48.0/22 672 100% 66
170.78.50.0/23 Valid Nonecovered by 170.78.48.0/22 671 100% 67
170.78.48.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
170.78.48.0/23 Valid Other IRR onlyRADB 671 100% 67
2804:3524::/32 Valid Other IRR onlyRADB, TC 633 100% 67

AS-SET

AS266271'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 10 are in fix.csv.

  • Route object: none5
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none170.78.48.0/24No route object for it. A route object for 170.78.48.0/23 with origin AS266271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266271 in the RIR database for the space.672 of 673
Route object: none170.78.49.0/24No route object for it. A route object for 170.78.48.0/23 with origin AS266271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266271 in the RIR database for the space.672 of 673
Route object: none170.78.50.0/24No route object for it. A route object for 170.78.48.0/22 with origin AS266271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266271 in the RIR database for the space.672 of 673
Route object: none170.78.51.0/24No route object for it. A route object for 170.78.48.0/22 with origin AS266271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266271 in the RIR database for the space.672 of 673
Route object: none170.78.50.0/23No route object for it. A route object for 170.78.48.0/22 with origin AS266271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266271 in the RIR database for the space.671 of 673
Route object: RIR170.78.48.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.78.48.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:3524::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

2804:694::/32RADBNo ROA
2804:3524::/33RADBValid

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.