bgpreport

Network · data from 2026-11-12

AS265103 AS265103 - Biplink Servicos de Comunicacao Multimidia Ltda ME

Registry name: AS265103 - Biplink Servicos de Comunicacao Multimidia Ltda ME, BR · not in 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
0Route objects not announced registered with origin AS265103, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265103, 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.
170.254.101.0/24 No ROA Nonecovered by 170.254.100.0/22 669 99% 67
170.254.100.0/24 No ROA Nonecovered by 170.254.100.0/22 202 30% 56
170.254.102.0/24 No ROA Nonecovered by 170.254.100.0/22 202 30% 56
170.254.103.0/24 No ROA Nonecovered by 170.254.100.0/22 202 30% 56
170.254.100.0/22 No ROA Other IRR onlyRADB 671 100% 67
2804:32e4::/32 No ROA Other IRR onlyRADB 633 100% 67

AS-SET

AS265103 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: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none170.254.101.0/24No ROA covers it. Add a ROA for AS265103, maxLength 24.669 of 673
Route object: none170.254.101.0/24No route object for it. A route object for 170.254.100.0/22 with origin AS265103 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265103 in the RIR database for the space.669 of 673
ROA: none170.254.100.0/24No ROA covers it. Add a ROA for AS265103, maxLength 24.202 of 673
Route object: none170.254.100.0/24No route object for it. A route object for 170.254.100.0/22 with origin AS265103 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265103 in the RIR database for the space.202 of 673
ROA: none170.254.102.0/24No ROA covers it. Add a ROA for AS265103, maxLength 24.202 of 673
Route object: none170.254.102.0/24No route object for it. A route object for 170.254.100.0/22 with origin AS265103 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265103 in the RIR database for the space.202 of 673
ROA: none170.254.103.0/24No ROA covers it. Add a ROA for AS265103, maxLength 24.202 of 673
Route object: none170.254.103.0/24No route object for it. A route object for 170.254.100.0/22 with origin AS265103 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265103 in the RIR database for the space.202 of 673
ROA: none170.254.100.0/22No ROA covers it. Add a ROA for AS265103, maxLength 22.671 of 673
Route object: RIR170.254.100.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:32e4::/32No ROA covers it. Add a ROA for AS265103, maxLength 32.633 of 636
Route object: RIR2804:32e4::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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