bgpreport

Network · data from 2026-11-12

AS271050 AS271050 - LINK INTERNET FIBRA OTICA

Registry name: AS271050 - LINK INTERNET FIBRA OTICA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271050, 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.
187.84.118.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
187.84.116.0/24 No ROA Other IRR onlyRADB 670 100% 66
187.84.119.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
187.84.117.0/24 No ROA Other IRR onlyRADB, TC 666 99% 67
2804:757c:8000::/34 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:757c:4000::/34 No ROA Other IRR onlyRADB, TC 631 99% 67
2804:757c:c000::/34 No ROA Other IRR onlyRADB, TC 631 99% 67

AS-SET

AS271050 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 45 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: none187.84.118.0/24No ROA covers it. Add a ROA for AS271050, maxLength 24.672 of 673
Route object: RIR187.84.118.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none187.84.116.0/24No ROA covers it. Add a ROA for AS271050, maxLength 24.670 of 673
Route object: RIR187.84.116.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none187.84.119.0/24No ROA covers it. Add a ROA for AS271050, maxLength 24.668 of 673
Route object: RIR187.84.119.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none187.84.117.0/24No ROA covers it. Add a ROA for AS271050, maxLength 24.666 of 673
Route object: RIR187.84.117.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:757c:8000::/34No ROA covers it. Add a ROA for AS271050, maxLength 34.635 of 636
Route object: RIR2804:757c:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:757c:4000::/34No ROA covers it. Add a ROA for AS271050, maxLength 34.631 of 636
Route object: RIR2804:757c:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:757c:c000::/34No ROA covers it. Add a ROA for AS271050, maxLength 34.631 of 636
Route object: RIR2804:757c:c000::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

187.84.116.0/22NTTCOM, RADB, TCNo ROA
187.84.116.0/23RADBNo ROA
187.84.118.0/23RADBNo ROA
2804:757c::/32NTTCOM, RADB, TCNo ROA
2804:757c::/33RADBNo ROA
2804:757c::/34RADBNo ROA
2804:757c::/35RADBNo ROA
2804:757c::/36RADBNo ROA
2804:757c:1000::/36RADBNo ROA
2804:757c:2000::/35RADBNo ROA
2804:757c:2000::/36RADBNo ROA
2804:757c:3000::/36RADBNo ROA
2804:757c:4000::/35RADBNo ROA
2804:757c:4000::/36RADBNo ROA
2804:757c:5000::/36RADBNo ROA
2804:757c:6000::/35RADBNo ROA
2804:757c:6000::/36RADBNo ROA
2804:757c:7000::/36RADBNo ROA
2804:757c:8000::/33RADBNo ROA
2804:757c:8000::/35RADBNo ROA
2804:757c:8000::/36RADBNo ROA
2804:757c:9000::/36RADBNo ROA
2804:757c:a000::/35RADBNo ROA
2804:757c:a000::/36RADBNo ROA
2804:757c:b000::/36RADBNo ROA
2804:757c:c000::/35RADBNo ROA
2804:757c:c000::/36RADBNo ROA
2804:757c:d000::/36RADBNo ROA
2804:757c:e000::/35RADBNo ROA
2804:757c:e000::/36RADBNo ROA
2804:757c:f000::/36RADBNo 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.