bgpreport

Network · data from 2026-11-12

AS64160 64160

Registry name: AS64160 - NimblyNet Limited, BZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64160, 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.
2803:e510::/32 No ROA None 636 100% 67
149.18.3.0/24 No ROA Other IRR onlyRADB 573 85% 66
5.175.238.0/24 Valid RIR databaseRIPE 664 99% 67
13.141.68.0/24 Valid RIR databaseRADB, RIPE 664 99% 67
87.232.109.0/24 Valid RIR databaseRADB, RIPE 664 99% 67
88.151.198.0/24 Valid RIR databaseRIPE 664 99% 67
148.224.24.0/22 Valid RIR databaseLACNIC 664 99% 67
148.224.24.0/24 Valid RIR databaseLACNIC 664 99% 67
148.224.25.0/24 Valid RIR databaseLACNIC 664 99% 67
148.224.26.0/24 Valid RIR databaseLACNIC 664 99% 67
195.128.24.0/24 Valid RIR databaseRIPE 664 99% 67
149.57.29.0/24 Valid RIR databaseARIN 662 98% 67
149.57.93.0/24 Valid RIR databaseARIN 662 98% 67
181.233.124.0/24 Valid RIR databaseLACNIC 575 85% 66
181.233.125.0/24 Valid RIR databaseLACNIC 575 85% 66
181.233.126.0/24 Valid RIR databaseLACNIC 575 85% 66
181.233.127.0/24 Valid RIR databaseLACNIC 575 85% 66

AS-SET

PeeringDB's irr_as_set for AS64160: LACNIC::AS64160:AS-NILI. 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 (AS64160 isn't in the set, or no route object for AS64160 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 objectsAS64160 in itNot covered
LACNIC::AS64160:AS-NILI LACNIC 2149 Yes 1

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2803:e510::/32No ROA covers it. Add a ROA for AS64160, maxLength 32.636 of 636
Route object: none2803:e510::/32No route object for it. Add a route object with origin AS64160 in the RIR database for the space.636 of 636
ROA: none149.18.3.0/24No ROA covers it. Add a ROA for AS64160, maxLength 24.573 of 673
Route object: RIR149.18.3.0/24Route object only in RADB. Add it in the RIR database for the space.573 of 673

Route objects not announced

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

148.224.27.0/24LACNICValid

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.