bgpreport

Network · data from 2026-11-12

AS266569 AS266569 - TEC NET PROVEDOR LTDA

Registry name: AS266569 - TEC NET PROVEDOR LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266569, 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.
160.238.208.0/23 No ROA Nonecovered by 160.238.208.0/22 668 99% 67
160.238.210.0/23 No ROA Nonecovered by 160.238.208.0/22 668 99% 67
160.238.209.0/24 No ROA Other IRR onlyALTDB 669 99% 66
160.238.210.0/24 No ROA Other IRR onlyALTDB 669 99% 66
160.238.208.0/22 No ROA Other IRR onlyALTDB, RADB 668 99% 67
2804:3e08::/32 No ROA Other IRR onlyRADB 633 100% 67

AS-SET

AS266569 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 14 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none160.238.208.0/23No ROA covers it. Add a ROA for AS266569, maxLength 23.668 of 673
Route object: none160.238.208.0/23No route object for it. A route object for 160.238.208.0/22 with origin AS266569 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266569 in the RIR database for the space.668 of 673
ROA: none160.238.210.0/23No ROA covers it. Add a ROA for AS266569, maxLength 23.668 of 673
Route object: none160.238.210.0/23No route object for it. A route object for 160.238.208.0/22 with origin AS266569 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266569 in the RIR database for the space.668 of 673
ROA: none160.238.209.0/24No ROA covers it. Add a ROA for AS266569, maxLength 24.669 of 673
Route object: RIR160.238.209.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
ROA: none160.238.210.0/24No ROA covers it. Add a ROA for AS266569, maxLength 24.669 of 673
Route object: RIR160.238.210.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
ROA: none160.238.208.0/22No ROA covers it. Add a ROA for AS266569, maxLength 22.668 of 673
Route object: RIR160.238.208.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:3e08::/32No ROA covers it. Add a ROA for AS266569, maxLength 32.633 of 636
Route object: RIR2804:3e08::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

160.238.208.0/24ALTDBNo ROA
160.238.211.0/24ALTDBNo 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.