bgpreport

Network · data from 2026-11-12

AS271597 NEW LINK CONNECT

Registry name: AS271597 - NEW LINK CONNECT, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271597, 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.74.111.0/24 No ROA Other origin only 24 4%low visibility 18
179.63.12.0/23 No ROA Other IRR onlyRADB, TC 671 100% 66
179.63.15.0/24 No ROA Other IRR onlyTC 671 100% 66
179.63.12.0/24 No ROA Other IRR onlyRADB 6 1%low visibility 5
179.63.13.0/24 No ROA Other IRR onlyRADB 6 1%low visibility 5
2804:7e04:c000::/34 Valid Nonecovered by 2804:7e04::/32 635 100% 67
2804:7e04::/33 Valid Nonecovered by 2804:7e04::/32 634 100% 67

AS-SET

AS271597'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: none5
  • Route object: none3
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none177.74.111.0/24No ROA covers it. Add a ROA for AS271597, maxLength 24.24 of 673
Route object: none177.74.111.0/24Route objects for it name AS270970. Add a route object with origin AS271597 in the RIR database for the space.24 of 673
ROA: none179.63.12.0/23No ROA covers it. Add a ROA for AS271597, maxLength 23.671 of 673
Route object: RIR179.63.12.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none179.63.15.0/24No ROA covers it. Add a ROA for AS271597, maxLength 24.671 of 673
Route object: RIR179.63.15.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none179.63.12.0/24No ROA covers it. Add a ROA for AS271597, maxLength 24.6 of 673
Route object: RIR179.63.12.0/24Route object only in RADB. Add it in the RIR database for the space.6 of 673
ROA: none179.63.13.0/24No ROA covers it. Add a ROA for AS271597, maxLength 24.6 of 673
Route object: RIR179.63.13.0/24Route object only in RADB. Add it in the RIR database for the space.6 of 673
Route object: none2804:7e04:c000::/34No route object for it. A route object for 2804:7e04::/32 with origin AS271597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271597 in the RIR database for the space.635 of 636
Route object: none2804:7e04::/33No route object for it. A route object for 2804:7e04::/32 with origin AS271597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271597 in the RIR database for the space.634 of 636

Route objects not announced

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

179.63.12.0/22RADBNo ROA
2804:7e04::/32RADB, TCValid

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.