bgpreport

Network · data from 2026-11-12

AS267446 Newertech Sol. Tec. e Prod. de Informática

Registry name: AS267446 - PRO LINK TELECOMUNICACOES LTDA, BR · PeeringDB

5IPv4 routes 0.0% RPKI valid · 20.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 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS267446, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267446, 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.
181.191.236.0/24 No ROA Nonecovered by 181.191.236.0/22 668 99% 67
181.191.237.0/24 No ROA Nonecovered by 181.191.236.0/22 668 99% 67
181.191.238.0/24 No ROA Nonecovered by 181.191.236.0/22 668 99% 67
181.191.239.0/24 No ROA Nonecovered by 181.191.236.0/22 668 99% 67
181.191.236.0/22 No ROA Other IRR onlyTC 672 100% 67
2804:41a0::/32 No ROA Other IRR onlyTC 633 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none181.191.236.0/24No ROA covers it. Add a ROA for AS267446, maxLength 24.668 of 673
Route object: none181.191.236.0/24No route object for it. A route object for 181.191.236.0/22 with origin AS267446 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267446 in the RIR database for the space.668 of 673
ROA: none181.191.237.0/24No ROA covers it. Add a ROA for AS267446, maxLength 24.668 of 673
Route object: none181.191.237.0/24No route object for it. A route object for 181.191.236.0/22 with origin AS267446 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267446 in the RIR database for the space.668 of 673
ROA: none181.191.238.0/24No ROA covers it. Add a ROA for AS267446, maxLength 24.668 of 673
Route object: none181.191.238.0/24No route object for it. A route object for 181.191.236.0/22 with origin AS267446 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267446 in the RIR database for the space.668 of 673
ROA: none181.191.239.0/24No ROA covers it. Add a ROA for AS267446, maxLength 24.668 of 673
Route object: none181.191.239.0/24No route object for it. A route object for 181.191.236.0/22 with origin AS267446 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267446 in the RIR database for the space.668 of 673
ROA: none181.191.236.0/22No ROA covers it. Add a ROA for AS267446, maxLength 22.672 of 673
Route object: RIR181.191.236.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:41a0::/32No ROA covers it. Add a ROA for AS267446, maxLength 32.633 of 636
Route object: RIR2804:41a0::/32Route object only in TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

170.83.28.0/22RADBNo ROA
2804:78c8::/32RADBNo 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.