bgpreport

Network · data from 2026-11-12

AS270380 AS270380 - PROVELINK TELECOM LTDA

Registry name: AS270380 - PROVELINK TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270380, 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.

190.89.57.0/24 No ROA Nonecovered by 190.89.56.0/22 671 100% 67
190.89.56.0/24 No ROA Nonecovered by 190.89.56.0/22 669 99% 67
190.89.58.0/24 No ROA Nonecovered by 190.89.56.0/22 669 99% 67
190.89.59.0/24 No ROA Nonecovered by 190.89.56.0/22 669 99% 67
2804:6b20::/34 No ROA Nonecovered by 2804:6b20::/32 636 100% 67
2804:6b20:4000::/34 No ROA Nonecovered by 2804:6b20::/32 636 100% 67
2804:6b20:8000::/34 No ROA Nonecovered by 2804:6b20::/32 636 100% 67
2804:6b20:c000::/34 No ROA Nonecovered by 2804:6b20::/32 636 100% 67
190.89.56.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
2804:6b20::/32 No ROA Other IRR onlyRADB, TC 636 100% 69

AS-SET

AS270380 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none8
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none190.89.57.0/24No ROA covers it. Add a ROA for AS270380, maxLength 24.671 of 673
Route object: none190.89.57.0/24No route object for it. A route object for 190.89.56.0/22 with origin AS270380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270380 in the RIR database for the space.671 of 673
ROA: none190.89.56.0/24No ROA covers it. Add a ROA for AS270380, maxLength 24.669 of 673
Route object: none190.89.56.0/24No route object for it. A route object for 190.89.56.0/22 with origin AS270380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270380 in the RIR database for the space.669 of 673
ROA: none190.89.58.0/24No ROA covers it. Add a ROA for AS270380, maxLength 24.669 of 673
Route object: none190.89.58.0/24No route object for it. A route object for 190.89.56.0/22 with origin AS270380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270380 in the RIR database for the space.669 of 673
ROA: none190.89.59.0/24No ROA covers it. Add a ROA for AS270380, maxLength 24.669 of 673
Route object: none190.89.59.0/24No route object for it. A route object for 190.89.56.0/22 with origin AS270380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270380 in the RIR database for the space.669 of 673
ROA: none2804:6b20::/34No ROA covers it. Add a ROA for AS270380, maxLength 34.636 of 636
Route object: none2804:6b20::/34No route object for it. A route object for 2804:6b20::/32 with origin AS270380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270380 in the RIR database for the space.636 of 636
ROA: none2804:6b20:4000::/34No ROA covers it. Add a ROA for AS270380, maxLength 34.636 of 636
Route object: none2804:6b20:4000::/34No route object for it. A route object for 2804:6b20::/32 with origin AS270380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270380 in the RIR database for the space.636 of 636
ROA: none2804:6b20:8000::/34No ROA covers it. Add a ROA for AS270380, maxLength 34.636 of 636
Route object: none2804:6b20:8000::/34No route object for it. A route object for 2804:6b20::/32 with origin AS270380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270380 in the RIR database for the space.636 of 636
ROA: none2804:6b20:c000::/34No ROA covers it. Add a ROA for AS270380, maxLength 34.636 of 636
Route object: none2804:6b20:c000::/34No route object for it. A route object for 2804:6b20::/32 with origin AS270380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270380 in the RIR database for the space.636 of 636
ROA: none190.89.56.0/22No ROA covers it. Add a ROA for AS270380, maxLength 22.671 of 673
Route object: RIR190.89.56.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:6b20::/32No ROA covers it. Add a ROA for AS270380, maxLength 32.636 of 636
Route object: RIR2804:6b20::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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