bgpreport

Network · data from 2026-11-12

AS52829 AS52829 - NEWLINE TELECOM

Registry name: AS52829 - NEWLINE TELECOM, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52829, 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.
177.72.187.0/24 No ROA Nonecovered by 177.72.184.0/21 672 100% 67
168.0.189.0/24 No ROA Nonecovered by 168.0.188.0/22 670 100% 66
177.72.191.0/24 No ROA Nonecovered by 177.72.184.0/21 670 100% 66
168.0.188.0/22 No ROA Other IRR onlyRADB 672 100% 66
177.72.184.0/21 No ROA Other IRR onlyRADB 670 100% 66
2804:bc8::/32 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

AS52829 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: none6
  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none177.72.187.0/24No ROA covers it. Add a ROA for AS52829, maxLength 24.672 of 673
Route object: none177.72.187.0/24No route object for it. A route object for 177.72.184.0/21 with origin AS52829 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52829 in the RIR database for the space.672 of 673
ROA: none168.0.189.0/24No ROA covers it. Add a ROA for AS52829, maxLength 24.670 of 673
Route object: none168.0.189.0/24No route object for it. A route object for 168.0.188.0/22 with origin AS52829 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52829 in the RIR database for the space.670 of 673
ROA: none177.72.191.0/24No ROA covers it. Add a ROA for AS52829, maxLength 24.670 of 673
Route object: none177.72.191.0/24No route object for it. A route object for 177.72.184.0/21 with origin AS52829 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52829 in the RIR database for the space.670 of 673
ROA: none168.0.188.0/22No ROA covers it. Add a ROA for AS52829, maxLength 22.672 of 673
Route object: RIR168.0.188.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.72.184.0/21No ROA covers it. Add a ROA for AS52829, maxLength 21.670 of 673
Route object: RIR177.72.184.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:bc8::/32No ROA covers it. Add a ROA for AS52829, maxLength 32.635 of 636
Route object: RIR2804:bc8::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS52829 is announced.

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.