bgpreport

Network · data from 2026-11-12

AS273723 L.LOTIC SERVICOS DE TECNOLOGIA

Registry name: AS273723 - L.LOTIC SERVICOS DE TECNOLOGIA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273723, 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.
38.21.118.0/23 No ROA Other IRR onlyALTDB 672 100% 66
38.250.246.0/23 No ROA Other IRR onlyALTDB, RADB 672 100% 66
38.21.118.0/24 No ROA Other IRR onlyALTDB 671 100% 66
38.21.119.0/24 No ROA Other IRR onlyALTDB 671 100% 66
38.250.246.0/24 No ROA Other IRR onlyALTDB 671 100% 66
38.250.247.0/24 No ROA Other IRR onlyALTDB 671 100% 66
2804:8b48::/32 No ROA Other IRR onlyALTDB, RADB, TC 635 100% 67
2804:8b48::/33 No ROA Other IRR onlyALTDB, TC 635 100% 67
2804:8b48:8000::/33 No ROA Other IRR onlyALTDB, TC 635 100% 67

AS-SET

AS273723'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 18 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none38.21.118.0/23No ROA covers it. Add a ROA for AS273723, maxLength 23.672 of 673
Route object: RIR38.21.118.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none38.250.246.0/23No ROA covers it. Add a ROA for AS273723, maxLength 23.672 of 673
Route object: RIR38.250.246.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.21.118.0/24No ROA covers it. Add a ROA for AS273723, maxLength 24.671 of 673
Route object: RIR38.21.118.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none38.21.119.0/24No ROA covers it. Add a ROA for AS273723, maxLength 24.671 of 673
Route object: RIR38.21.119.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none38.250.246.0/24No ROA covers it. Add a ROA for AS273723, maxLength 24.671 of 673
Route object: RIR38.250.246.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none38.250.247.0/24No ROA covers it. Add a ROA for AS273723, maxLength 24.671 of 673
Route object: RIR38.250.247.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none2804:8b48::/32No ROA covers it. Add a ROA for AS273723, maxLength 32.635 of 636
Route object: RIR2804:8b48::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:8b48::/33No ROA covers it. Add a ROA for AS273723, maxLength 33.635 of 636
Route object: RIR2804:8b48::/33Route object only in ALTDB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:8b48:8000::/33No ROA covers it. Add a ROA for AS273723, maxLength 33.635 of 636
Route object: RIR2804:8b48:8000::/33Route object only in ALTDB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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