bgpreport

Network · data from 2026-11-12

AS269309 FIBRA LIVE SERVICOS DE TELECOMUNICACOES LTDA

Registry name: AS269309 - FIBRA LIVE SERVICOS DE TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

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

2804:2b1c:40::/42 Invalid: origin None 25 4%low visibility 11
45.183.22.0/24 No ROA Nonecovered by 45.183.20.0/22 667 99% 67
45.183.20.0/23 No ROA Nonecovered by 45.183.20.0/22 665 99% 67
45.183.20.0/24 No ROA Nonecovered by 45.183.20.0/22 29 4%low visibility 11
45.183.21.0/24 No ROA Nonecovered by 45.183.20.0/22 29 4%low visibility 11
45.183.23.0/24 No ROA Other IRR onlyRADB 670 100% 67
2804:62a4::/32 No ROA Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS269309's PeeringDB record names no 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 15 are in fix.csv.

  • ROA: origin1
  • ROA: none6
  • Route object: none5
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2804:2b1c:40::/42ROAs covering it name AS265135, not AS269309. If AS269309 should announce it, add a ROA for AS269309.25 of 636
Route object: none2804:2b1c:40::/42No route object for it. Add a route object with origin AS269309 in the RIR database for the space.25 of 636
ROA: none45.183.22.0/24No ROA covers it. Add a ROA for AS269309, maxLength 24.667 of 673
Route object: none45.183.22.0/24No route object for it. A route object for 45.183.20.0/22 with origin AS269309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269309 in the RIR database for the space.667 of 673
ROA: none45.183.20.0/23No ROA covers it. Add a ROA for AS269309, maxLength 23.665 of 673
Route object: none45.183.20.0/23No route object for it. A route object for 45.183.20.0/22 with origin AS269309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269309 in the RIR database for the space.665 of 673
ROA: none45.183.20.0/24No ROA covers it. Add a ROA for AS269309, maxLength 24.29 of 673
Route object: none45.183.20.0/24No route object for it. A route object for 45.183.20.0/22 with origin AS269309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269309 in the RIR database for the space.29 of 673
ROA: none45.183.21.0/24No ROA covers it. Add a ROA for AS269309, maxLength 24.29 of 673
Route object: none45.183.21.0/24No route object for it. A route object for 45.183.20.0/22 with origin AS269309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269309 in the RIR database for the space.29 of 673
ROA: none45.183.23.0/24No ROA covers it. Add a ROA for AS269309, maxLength 24.670 of 673
Route object: RIR45.183.23.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:62a4::/32No ROA covers it. Add a ROA for AS269309, maxLength 32.635 of 636
Route object: RIR2804:62a4::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.183.20.0/22RADB, TCNo 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.