Network · data from 2026-11-12
AS18464 ALVIDI
Registry name: ALVIDI - ALVIDI TECHNOLOGY Inc, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18464, 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.
| 163.61.62.0/24 | Valid | None | 673 100% |
| 178.173.224.0/24 | Valid | None | 671 100% |
| 178.173.228.0/22 | Valid | None | 671 100% |
| 178.173.229.0/24 | Valid | None | 669 99% |
| 178.173.241.0/24 | Valid | Other origin only | 669 99% |
| 178.173.228.0/24 | Valid | None | 667 99% |
| 178.173.227.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 178.173.230.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 58.84.52.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 58.84.53.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 58.84.54.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.136.125.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.136.126.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.136.127.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 116.206.100.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.206.101.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.206.102.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 58.84.55.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.90.136.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.90.136.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.90.136.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.90.137.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 103.90.138.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 50.117.86.0/24 | Valid | RIR databaseARIN | 669 99% |
| 45.38.54.0/24 | Valid | RIR databaseARIN | 668 99% |
| 45.38.166.0/24 | Valid | RIR databaseARIN | 668 99% |
| 45.39.231.0/24 | Valid | RIR databaseARIN | 668 99% |
| 2001:16c0:16c0::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2602:2a4:9f::/48 | Valid | RIR databaseARIN | 634 100% |
AS-SET
AS18464'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 37 are in fix.csv.
- Route object: none6
- Route object: RIR2
- Route object: not announced29
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 163.61.62.0/24 | No route object for it. Add a route object with origin AS18464 in the RIR database for the space. |
| Route object: none | 178.173.224.0/24 | No route object for it. Add a route object with origin AS18464 in the RIR database for the space. |
| Route object: none | 178.173.228.0/22 | No route object for it. Add a route object with origin AS18464 in the RIR database for the space. |
| Route object: none | 178.173.229.0/24 | No route object for it. Add a route object with origin AS18464 in the RIR database for the space. |
| Route object: none | 178.173.241.0/24 | Route objects for it name AS48024. Add a route object with origin AS18464 in the RIR database for the space. |
| Route object: none | 178.173.228.0/24 | No route object for it. Add a route object with origin AS18464 in the RIR database for the space. |
| Route object: RIR | 178.173.227.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 178.173.230.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18464 whose prefix no peer sees AS18464 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.84.52.0/22 | APNIC | Valid |
| 58.84.52.0/23 | APNIC | Valid |
| 58.84.54.0/23 | APNIC | Valid |
| 103.90.138.0/23 | APNIC | Valid |
| 103.90.139.0/24 | APNIC | Valid |
| 103.136.124.0/22 | APNIC | Valid |
| 103.136.124.0/23 | APNIC | Valid |
| 103.136.124.0/24 | APNIC | Valid |
| 103.136.126.0/23 | APNIC | Valid |
| 103.197.68.0/22 | APNIC | Valid |
| 103.197.68.0/23 | APNIC | Valid |
| 103.197.68.0/24 | APNIC | Valid |
| 103.197.69.0/24 | APNIC | Valid |
| 103.197.70.0/23 | APNIC | Valid |
| 103.197.70.0/24 | APNIC | Valid |
| 103.197.71.0/24 | APNIC | Valid |
| 116.206.100.0/22 | APNIC | Valid |
| 116.206.100.0/23 | APNIC, RADB | Valid |
| 116.206.102.0/23 | APNIC | Valid |
| 116.206.103.0/24 | APNIC | Valid |
| 140.235.8.0/24 | ARIN | Invalid: origin |
| 202.8.104.0/22 | APNIC | Valid |
| 202.8.104.0/23 | APNIC | Valid |
| 202.8.104.0/24 | APNIC | Valid |
| 202.8.105.0/24 | APNIC | Valid |
| 202.8.106.0/23 | APNIC | Valid |
| 202.8.106.0/24 | APNIC | Valid |
| 202.8.107.0/24 | APNIC | Valid |
| 2602:f863::/40 | ARIN | Valid |
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.