bgpreport

Network · data from 2026-11-12

AS265176 AS265176 - LINKTAP TELECOM LTDA

Registry name: AS265176 - LINKTAP TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265176, 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.
167.249.86.0/23 Valid Nonecovered by 167.249.84.0/22 669 99% 67
167.249.84.0/23 Valid Nonecovered by 167.249.84.0/22 668 99% 67
167.249.84.0/24 Valid Nonecovered by 167.249.84.0/22 1 0%low visibility 1
167.249.85.0/24 Valid Nonecovered by 167.249.84.0/22 1 0%low visibility 1
167.249.86.0/24 Valid Nonecovered by 167.249.84.0/22 1 0%low visibility 1
167.249.87.0/24 Valid Nonecovered by 167.249.84.0/22 1 0%low visibility 1
167.249.84.0/22 Valid Other IRR onlyRADB 669 99% 67
2804:2bcc::/32 Valid Other IRR onlyRADB 630 99% 67

AS-SET

AS265176 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 8 are in fix.csv.

  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none167.249.86.0/23No route object for it. A route object for 167.249.84.0/22 with origin AS265176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265176 in the RIR database for the space.669 of 673
Route object: none167.249.84.0/23No route object for it. A route object for 167.249.84.0/22 with origin AS265176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265176 in the RIR database for the space.668 of 673
Route object: none167.249.84.0/24No route object for it. A route object for 167.249.84.0/22 with origin AS265176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265176 in the RIR database for the space.1 of 673
Route object: none167.249.85.0/24No route object for it. A route object for 167.249.84.0/22 with origin AS265176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265176 in the RIR database for the space.1 of 673
Route object: none167.249.86.0/24No route object for it. A route object for 167.249.84.0/22 with origin AS265176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265176 in the RIR database for the space.1 of 673
Route object: none167.249.87.0/24No route object for it. A route object for 167.249.84.0/22 with origin AS265176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265176 in the RIR database for the space.1 of 673
Route object: RIR167.249.84.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:2bcc::/32Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

Every route object with origin AS265176 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.