bgpreport

Network · data from 2026-11-12

AS266487 Speed Max Telecomunicação

Registry name: AS266487 - ISM Telecom Eireli ME, BR · PeeringDB

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

Announced routes

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

2804:3894:ca00::/40 No ROA Nonecovered by 2804:3894:8000::/33 635 100% 67
2804:3894:2000::/35 No ROA Nonecovered by 2804:3894::/33 8 1%low visibility 6
2804:3894:4000::/35 No ROA Nonecovered by 2804:3894::/33 8 1%low visibility 6
2804:3894:6000::/35 No ROA Nonecovered by 2804:3894::/33 8 1%low visibility 6
170.83.186.0/23 No ROA Other IRR onlyRADB 670 100% 66
170.83.184.0/23 No ROA Other IRR onlyRADB 669 99% 66
2804:3894::/33 No ROA Other IRR onlyRADB 634 100% 67
2804:3894:9d00::/40 No ROA Other IRR onlyRADB 634 100% 67
170.83.184.0/24 No ROA Other IRR onlyRADB 20 3%low visibility 8
170.83.185.0/24 No ROA Other IRR onlyRADB 20 3%low visibility 8

AS-SET

AS266487'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 26 are in fix.csv.

  • ROA: none10
  • Route object: none4
  • Route object: RIR6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2804:3894:ca00::/40No ROA covers it. Add a ROA for AS266487, maxLength 40.635 of 636
Route object: none2804:3894:ca00::/40No route object for it. A route object for 2804:3894:8000::/33 with origin AS266487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266487 in the RIR database for the space.635 of 636
ROA: none2804:3894:2000::/35No ROA covers it. Add a ROA for AS266487, maxLength 35.8 of 636
Route object: none2804:3894:2000::/35No route object for it. A route object for 2804:3894::/33 with origin AS266487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266487 in the RIR database for the space.8 of 636
ROA: none2804:3894:4000::/35No ROA covers it. Add a ROA for AS266487, maxLength 35.8 of 636
Route object: none2804:3894:4000::/35No route object for it. A route object for 2804:3894::/33 with origin AS266487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266487 in the RIR database for the space.8 of 636
ROA: none2804:3894:6000::/35No ROA covers it. Add a ROA for AS266487, maxLength 35.8 of 636
Route object: none2804:3894:6000::/35No route object for it. A route object for 2804:3894::/33 with origin AS266487 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266487 in the RIR database for the space.8 of 636
ROA: none170.83.186.0/23No ROA covers it. Add a ROA for AS266487, maxLength 23.670 of 673
Route object: RIR170.83.186.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none170.83.184.0/23No ROA covers it. Add a ROA for AS266487, maxLength 23.669 of 673
Route object: RIR170.83.184.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:3894::/33No ROA covers it. Add a ROA for AS266487, maxLength 33.634 of 636
Route object: RIR2804:3894::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:3894:9d00::/40No ROA covers it. Add a ROA for AS266487, maxLength 40.634 of 636
Route object: RIR2804:3894:9d00::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none170.83.184.0/24No ROA covers it. Add a ROA for AS266487, maxLength 24.20 of 673
Route object: RIR170.83.184.0/24Route object only in RADB. Add it in the RIR database for the space.20 of 673
ROA: none170.83.185.0/24No ROA covers it. Add a ROA for AS266487, maxLength 24.20 of 673
Route object: RIR170.83.185.0/24Route object only in RADB. Add it in the RIR database for the space.20 of 673

Route objects not announced

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

170.83.184.0/22BBOI, NTTCOM, RADB, TCNo ROA
170.83.186.0/24RADBNo ROA
170.83.187.0/24RADBNo ROA
2804:3894::/32BBOI, NTTCOM, RADB, TCNo ROA
2804:3894:8000::/33RADBNo ROA
2804:3894:a000::/35RADBNo 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.