bgpreport

Network · data from 2026-11-12

AS61819 AS61819 - K L M SERVICOS DE TELECOMUNICACOES LTDA

Registry name: AS61819 - K L M SERVICOS DE TELECOMUNICACOES LTDA, BR · not in PeeringDB

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

Announced routes

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

201.131.168.0/23 No ROA Nonecovered by 201.131.168.0/22 671 100% 67
201.131.168.0/24 No ROA Nonecovered by 201.131.168.0/22 671 100% 67
201.131.169.0/24 No ROA Nonecovered by 201.131.168.0/22 671 100% 67
201.131.170.0/23 No ROA Nonecovered by 201.131.168.0/22 671 100% 67
201.131.171.0/24 No ROA Nonecovered by 201.131.168.0/22 671 100% 67
201.131.170.0/24 No ROA Nonecovered by 201.131.168.0/22 670 100% 67
2804:19cc:c0ca::/48 No ROA Nonecovered by 2804:19cc::/32 636 100% 67
2804:19cc:f0ca::/48 No ROA Nonecovered by 2804:19cc::/32 636 100% 67
2804:19cc:fada::/48 No ROA Nonecovered by 2804:19cc::/32 636 100% 67
201.131.168.0/22 No ROA Other IRR onlyRADB, TC 672 100% 67
2804:19cc::/32 No ROA Other IRR onlyRADB, TC 634 100% 69

AS-SET

AS61819 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 22 are in fix.csv.

  • ROA: none11
  • Route object: none9
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none201.131.168.0/23No ROA covers it. Add a ROA for AS61819, maxLength 23.671 of 673
Route object: none201.131.168.0/23No route object for it. A route object for 201.131.168.0/22 with origin AS61819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61819 in the RIR database for the space.671 of 673
ROA: none201.131.168.0/24No ROA covers it. Add a ROA for AS61819, maxLength 24.671 of 673
Route object: none201.131.168.0/24No route object for it. A route object for 201.131.168.0/22 with origin AS61819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61819 in the RIR database for the space.671 of 673
ROA: none201.131.169.0/24No ROA covers it. Add a ROA for AS61819, maxLength 24.671 of 673
Route object: none201.131.169.0/24No route object for it. A route object for 201.131.168.0/22 with origin AS61819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61819 in the RIR database for the space.671 of 673
ROA: none201.131.170.0/23No ROA covers it. Add a ROA for AS61819, maxLength 23.671 of 673
Route object: none201.131.170.0/23No route object for it. A route object for 201.131.168.0/22 with origin AS61819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61819 in the RIR database for the space.671 of 673
ROA: none201.131.171.0/24No ROA covers it. Add a ROA for AS61819, maxLength 24.671 of 673
Route object: none201.131.171.0/24No route object for it. A route object for 201.131.168.0/22 with origin AS61819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61819 in the RIR database for the space.671 of 673
ROA: none201.131.170.0/24No ROA covers it. Add a ROA for AS61819, maxLength 24.670 of 673
Route object: none201.131.170.0/24No route object for it. A route object for 201.131.168.0/22 with origin AS61819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61819 in the RIR database for the space.670 of 673
ROA: none2804:19cc:c0ca::/48No ROA covers it. Add a ROA for AS61819, maxLength 48.636 of 636
Route object: none2804:19cc:c0ca::/48No route object for it. A route object for 2804:19cc::/32 with origin AS61819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61819 in the RIR database for the space.636 of 636
ROA: none2804:19cc:f0ca::/48No ROA covers it. Add a ROA for AS61819, maxLength 48.636 of 636
Route object: none2804:19cc:f0ca::/48No route object for it. A route object for 2804:19cc::/32 with origin AS61819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61819 in the RIR database for the space.636 of 636
ROA: none2804:19cc:fada::/48No ROA covers it. Add a ROA for AS61819, maxLength 48.636 of 636
Route object: none2804:19cc:fada::/48No route object for it. A route object for 2804:19cc::/32 with origin AS61819 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61819 in the RIR database for the space.636 of 636
ROA: none201.131.168.0/22No ROA covers it. Add a ROA for AS61819, maxLength 22.672 of 673
Route object: RIR201.131.168.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:19cc::/32No ROA covers it. Add a ROA for AS61819, maxLength 32.634 of 636
Route object: RIR2804:19cc::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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