bgpreport

Network · data from 2026-11-12

AS266627 AS266627 - INTERATIVA TELECOM E TI LTDA ME

Registry name: AS266627 - INTERATIVA TELECOM E TI LTDA ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266627, 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.
128.201.24.0/23 No ROA Other IRR onlyRADB 668 99% 67
128.201.26.0/23 No ROA Other IRR onlyRADB 668 99% 67

AS-SET

AS266627 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 12 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none128.201.24.0/23No ROA covers it. Add a ROA for AS266627, maxLength 23.668 of 673
Route object: RIR128.201.24.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none128.201.26.0/23No ROA covers it. Add a ROA for AS266627, maxLength 23.668 of 673
Route object: RIR128.201.26.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

128.201.24.0/22TCNo ROA
128.201.24.0/24RADBNo ROA
128.201.25.0/24RADBNo ROA
128.201.26.0/24RADBNo ROA
128.201.27.0/24RADBNo ROA
2804:3ee4::/32RADB, TCNo ROA
2804:3ee4::/33RADBNo ROA
2804:3ee4:8000::/33RADBNo 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.