bgpreport

Network · data from 2026-11-12

AS211439 LOCOTORPI EU

Registry name: locotorpi Jurgita Jurgaitiene trading as LOCOTORPI, IE · PeeringDB

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

Announced routes

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

45.8.94.0/24 Invalid: origin None 112 17% 40
212.87.205.0/24 Invalid: origin None 2 0%low visibility 2
91.132.12.0/24 No ROA RIR databaseRIPE 673 100% 67
141.98.58.0/24 No ROA RIR databaseRIPE 673 100% 67
194.31.181.0/24 No ROA RIR databaseRIPE 673 100% 67
194.31.182.0/24 No ROA RIR databaseRIPE 673 100% 67
85.208.124.0/22 No ROA RIR databaseRIPE 672 100% 67
193.238.85.0/24 No ROA RIR databaseRIPE 672 100% 67
194.121.51.0/24 No ROA RIR databaseRIPE 672 100% 67
194.124.200.0/24 No ROA RIR databaseRIPE 672 100% 67
193.108.102.0/24 Valid Other IRR onlyRADB 673 100% 67
206.206.81.0/24 Valid Other IRR onlyRADB 673 100% 67
45.81.59.0/24 Valid Other IRR onlyRADB 672 100% 67
45.114.191.0/24 Valid Other IRR onlyRADB 672 100% 67
31.57.123.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
31.58.64.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
46.34.56.0/23 Valid RIR databaseRADB, RIPE 673 100% 67
64.69.96.0/24 Valid RIR databaseARIN, RADB 673 100% 67
67.210.100.0/24 Valid RIR databaseARIN, RADB 673 100% 67
67.210.107.0/24 Valid RIR databaseARIN, RADB 673 100% 67
79.99.149.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.153.1.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.206.19.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
88.209.253.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
91.188.252.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
92.113.62.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
108.165.34.0/24 Valid RIR databaseARIN 673 100% 67
108.165.200.0/24 Valid RIR databaseARIN, RADB 673 100% 67
109.110.165.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
109.110.166.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
109.176.212.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
139.28.173.0/24 Valid RIR databaseRIPE 673 100% 67
139.28.175.0/24 Valid RIR databaseRIPE 673 100% 67
140.150.153.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
140.233.185.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
143.20.212.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
150.241.231.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
151.242.138.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
151.244.77.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
151.244.84.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
151.245.79.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
151.245.84.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
163.5.113.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.20.255.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.226.107.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.242.111.0/24 Valid RIR databaseRIPE 673 100% 67
188.244.113.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
191.101.248.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.242.117.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.113.222.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
199.182.170.0/24 Valid RIR databaseARIN, RADB 673 100% 67
205.233.201.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.247.107.0/24 Valid RIR databaseARIN, RADB 673 100% 67
37.252.28.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.80.49.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.85.92.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.86.52.0/22 Valid RIR databaseRIPE 672 100% 67
45.94.237.0/24 Valid RIR databaseRIPE 672 100% 67
45.133.56.0/22 Valid RIR databaseRIPE 672 100% 67
89.116.92.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
104.206.18.0/24 Valid RIR databaseARIN, RADB 672 100% 67
171.22.222.0/24 Valid RIR databaseRIPE 672 100% 67
171.22.223.0/24 Valid RIR databaseRIPE 672 100% 67
185.169.228.0/22 Valid RIR databaseRIPE 672 100% 67
185.180.147.0/24 Valid RIR databaseRIPE 672 100% 67
185.205.223.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.242.110.0/24 Valid RIR databaseRIPE 672 100% 67
193.37.220.0/22 Valid RIR databaseRIPE 672 100% 67
209.137.184.0/24 Valid RIR databaseARIN, RADB 672 100% 67
64.204.136.0/24 Valid RIR databaseARIN, RADB 671 100% 67
23.26.52.0/24 Valid RIR databaseALTDB, ARIN, RADB 669 99% 67
23.26.234.0/24 Valid RIR databaseALTDB, ARIN, RADB 669 99% 67
31.56.198.0/24 Valid RIR databaseALTDB, RADB, RIPE 669 99% 67
31.57.94.0/24 Valid RIR databaseALTDB, RADB, RIPE 669 99% 67
64.40.148.0/24 Valid RIR databaseALTDB, ARIN, RADB 669 99% 67
91.202.209.0/24 Valid RIR databaseALTDB, RIPE 669 99% 67
95.135.196.0/24 Valid RIR databaseALTDB, RADB, RIPE 669 99% 67
166.0.149.0/24 Valid RIR databaseALTDB, ARIN, RADB 669 99% 67
181.41.209.0/24 Valid RIR databaseALTDB, RADB, RIPE 669 99% 67
181.214.172.0/24 Valid RIR databaseALTDB, RADB, RIPE 669 99% 67
181.215.24.0/24 Valid RIR databaseALTDB, RADB, RIPE 669 99% 67
181.215.54.0/24 Valid RIR databaseALTDB, RADB, RIPE 669 99% 67
191.96.2.0/24 Valid RIR databaseALTDB, RADB, RIPE 669 99% 67
191.101.143.0/24 Valid RIR databaseALTDB, RADB, RIPE 669 99% 67
37.44.212.0/24 Valid RIR databaseALTDB, RIPE 668 99% 67
88.80.143.0/24 Valid RIR databaseRIPE 667 99% 67
171.22.220.0/22 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: origin2
  • ROA: none8
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin45.8.94.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS211439 should announce it, add a ROA for AS211439.112 of 673
Route object: none45.8.94.0/24No route object for it. Add a route object with origin AS211439 in the RIR database for the space.112 of 673
ROA: origin212.87.205.0/24ROAs covering it name AS834, not AS211439. If AS211439 should announce it, add a ROA for AS211439.2 of 673
Route object: none212.87.205.0/24No route object for it. Add a route object with origin AS211439 in the RIR database for the space.2 of 673
ROA: none91.132.12.0/24No ROA covers it. Add a ROA for AS211439, maxLength 24.673 of 673
ROA: none141.98.58.0/24No ROA covers it. Add a ROA for AS211439, maxLength 24.673 of 673
ROA: none194.31.181.0/24No ROA covers it. Add a ROA for AS211439, maxLength 24.673 of 673
ROA: none194.31.182.0/24No ROA covers it. Add a ROA for AS211439, maxLength 24.673 of 673
ROA: none85.208.124.0/22No ROA covers it. Add a ROA for AS211439, maxLength 22.672 of 673
ROA: none193.238.85.0/24No ROA covers it. Add a ROA for AS211439, maxLength 24.672 of 673
ROA: none194.121.51.0/24No ROA covers it. Add a ROA for AS211439, maxLength 24.672 of 673
ROA: none194.124.200.0/24No ROA covers it. Add a ROA for AS211439, maxLength 24.672 of 673
Route object: RIR193.108.102.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.206.81.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR45.81.59.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.114.191.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

37.230.49.0/24RADB, RIPEValid
65.110.46.0/24ARIN, RADBValid
66.92.3.0/24ARIN, RADBValid
86.38.24.0/24RADB, RIPEValid

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.