bgpreport

Network · data from 2026-11-12

AS266319 Smart Telecom Networks Serv.de Telecom. LTDA M.E

Registry name: AS266319 - Smart Telecom Networks Serv.de Telecom. LTDA M.E, BR · PeeringDB

4IPv4 routes 0.0% RPKI valid · 100.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No 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 AS266319, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266319, 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.238.128.0/23 No ROA Other IRR onlyTC 671 100% 67
170.238.129.0/24 No ROA Other IRR onlyTC 671 100% 67
170.238.128.0/24 No ROA Other IRR onlyTC 670 100% 67
170.238.130.0/23 No ROA Other IRR onlyRADB, TC 670 100% 67
2804:35fc::/33 No ROA Other IRR onlyTC 636 100% 67
2804:35fc:8000::/33 No ROA Other IRR onlyTC 636 100% 67

AS-SET

AS266319'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 20 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none170.238.128.0/23No ROA covers it. Add a ROA for AS266319, maxLength 23.671 of 673
Route object: RIR170.238.128.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none170.238.129.0/24No ROA covers it. Add a ROA for AS266319, maxLength 24.671 of 673
Route object: RIR170.238.129.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none170.238.128.0/24No ROA covers it. Add a ROA for AS266319, maxLength 24.670 of 673
Route object: RIR170.238.128.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none170.238.130.0/23No ROA covers it. Add a ROA for AS266319, maxLength 23.670 of 673
Route object: RIR170.238.130.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:35fc::/33No ROA covers it. Add a ROA for AS266319, maxLength 33.636 of 636
Route object: RIR2804:35fc::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:35fc:8000::/33No ROA covers it. Add a ROA for AS266319, maxLength 33.636 of 636
Route object: RIR2804:35fc:8000::/33Route object only in TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

170.82.44.0/24RADBNo ROA
170.82.46.0/24RADBNo ROA
170.82.47.0/24RADBNo ROA
170.238.128.0/22RADB, TCNo ROA
170.238.130.0/24RADB, TCNo ROA
170.238.131.0/24RADB, TCNo ROA
201.159.16.0/22RADBNo ROA
2804:35fc::/32RADB, TCNo 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.