bgpreport

Network · data from 2026-11-12

AS28110 Rack Lodge

Registry name: AS28110 - NAVEGALO S.A., CR · PeeringDB

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

Announced routes

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

149.18.35.0/24 No ROA None 673 100% 68
149.18.26.0/24 No ROA Other IRR onlyRADB 673 100% 67
69.25.4.0/24 No ROA Other IRR onlyRADB 671 100% 68
154.6.3.0/24 No ROA Other IRR onlyRADB 665 99% 68
149.18.5.0/24 No ROA Other IRR onlyRADB 663 99% 68
154.6.62.0/24 No ROA Other IRR onlyRADB 657 98% 67
131.196.32.0/24 Valid Other IRR onlyRADB 673 100% 70
131.196.33.0/24 Valid Other IRR onlyRADB 673 100% 70
131.196.34.0/24 Valid Other IRR onlyRADB 673 100% 70
138.59.132.0/24 Valid Other IRR onlyRADB 673 100% 70
138.59.135.0/24 Valid Other IRR onlyRADB 673 100% 70
181.174.169.0/24 Valid Other IRR onlyRADB 673 100% 70
181.174.170.0/24 Valid Other IRR onlyRADB 673 100% 70
181.174.171.0/24 Valid Other IRR onlyRADB 673 100% 70
190.124.248.0/24 Valid Other IRR onlyRADB 673 100% 70
190.124.249.0/24 Valid Other IRR onlyRADB 673 100% 70
190.124.250.0/24 Valid Other IRR onlyRADB 673 100% 70
190.124.251.0/24 Valid Other IRR onlyRADB 673 100% 70
190.184.196.0/24 Valid Other IRR onlyRADB 673 100% 70
190.184.197.0/24 Valid Other IRR onlyRADB 673 100% 70
190.184.198.0/24 Valid Other IRR onlyRADB 673 100% 70
190.184.199.0/24 Valid Other IRR onlyRADB 673 100% 70
181.174.168.0/24 Valid Other IRR onlyRADB 671 100% 70
131.196.35.0/24 Valid Other IRR onlyRADB 663 99% 68
138.59.133.0/24 Valid Other IRR onlyRADB 663 99% 68
138.59.134.0/24 Valid Other IRR onlyRADB 663 99% 68
82.21.238.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.22.213.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.22.218.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.22.238.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.23.227.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.24.229.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.24.235.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.25.222.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.25.232.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.26.223.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.27.217.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.27.232.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
138.122.245.0/24 Valid RIR databaseLACNIC, RADB 666 99% 68
149.57.62.0/24 Valid RIR databaseARIN 665 99% 68
138.122.246.0/24 Valid RIR databaseLACNIC, RADB 664 99% 68
45.224.202.0/24 Valid RIR databaseLACNIC 660 98% 69
2606:f180:2::/48 Valid RIR databaseARIN 634 100% 67
2606:f180:9::/48 Valid RIR databaseARIN 631 99% 68
2800:c20::/32 Valid RIR databaseLACNIC, RADB 630 99% 68

AS-SET

PeeringDB's irr_as_set for AS28110: AS28110. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS28110 isn't in the set, or no route object for AS28110 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS28110 in itNot covered
AS28110 A single AS number, not a set: AS28110 (this network), 54 route objects.

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

  • ROA: none6
  • Route object: none1
  • Route object: RIR25
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none149.18.35.0/24No ROA covers it. Add a ROA for AS28110, maxLength 24.673 of 673
Route object: none149.18.35.0/24No route object for it. Add a route object with origin AS28110 in the RIR database for the space.673 of 673
ROA: none149.18.26.0/24No ROA covers it. Add a ROA for AS28110, maxLength 24.673 of 673
Route object: RIR149.18.26.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none69.25.4.0/24No ROA covers it. Add a ROA for AS28110, maxLength 24.671 of 673
Route object: RIR69.25.4.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.6.3.0/24No ROA covers it. Add a ROA for AS28110, maxLength 24.665 of 673
Route object: RIR154.6.3.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none149.18.5.0/24No ROA covers it. Add a ROA for AS28110, maxLength 24.663 of 673
Route object: RIR149.18.5.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none154.6.62.0/24No ROA covers it. Add a ROA for AS28110, maxLength 24.657 of 673
Route object: RIR154.6.62.0/24Route object only in RADB. Add it in the RIR database for the space.657 of 673
Route object: RIR131.196.32.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR131.196.33.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR131.196.34.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR138.59.132.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR138.59.135.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR181.174.169.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR181.174.170.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR181.174.171.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR190.124.248.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR190.124.249.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR190.124.250.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR190.124.251.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR190.184.196.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR190.184.197.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR190.184.198.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR190.184.199.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR181.174.168.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR131.196.35.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
Route object: RIR138.59.133.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
Route object: RIR138.59.134.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673

Route objects not announced

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

131.196.32.0/22LACNICValid
138.59.132.0/22LACNIC, RADBValid
138.121.140.0/22LACNICValid
149.57.0.0/24RADBNo ROA
170.81.32.0/22LACNICValid
181.174.168.0/22LACNIC, RADBValid
190.124.248.0/22LACNIC, RADBValid
190.184.196.0/22LACNIC, RADBValid
191.102.56.0/22LACNICValid
2606:f180:b::/48ARINValid

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.