Network · data from 2026-11-12
AS61164 LIR-AS LIR Limited
Registry name: LIR-AS LIR Limited, AE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61164, 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.
| 2a01:5f20::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a04:ee80::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a07:1f00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a07:5c00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a07:98c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:600::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:1080::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:1e00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:2480::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:3380::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:4700::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:4780::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:4b80::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:4d80::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:6400::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:6580::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:6780::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:7a00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:8000::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:8440::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:8bc0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:9a80::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:a100::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:a980::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:c000::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:db00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:e3c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:eb00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:f300::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0a:c1c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0d:29c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0d:8bc0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0d:e140::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0d:f940::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:2180::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:8c40::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:9240::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:9440::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:b0c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:c040::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:d740::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:e440::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:e840::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0e:f040::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:1c00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:2780::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:2c00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:5d80::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:6340::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:71c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:7440::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:9500::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:d400::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a0f:dc00::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a12:4c40::/29 | Valid | RIR databaseRIPE | 631 99% |
| 2a12:53c0::/29 | Valid | RIR databaseRIPE | 631 99% |
| 2a12:8c80::/29 | Valid | RIR databaseRIPE | 631 99% |
AS-SET
AS61164 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS61164 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.