Network · data from 2026-11-12
AS42316 KOBI-ASN Metisim Technologies Ltd
Registry name: KOBI-ASN Metisim Technologies Ltd, IL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42316, 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.159.131.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 45.159.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.187.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.113.47.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.159.129.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a0c:9280::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a0f:7680::/29 | Valid | RIR databaseRADB, RIPE | 635 100% |
AS-SET
AS42316 isn't in PeeringDB, where networks name their 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 13 are in fix.csv.
- Route object: RIR1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.159.131.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42316 whose prefix no peer sees AS42316 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.159.128.0/22 | RIPE | Valid |
| 45.159.128.0/24 | RIPE | Valid |
| 45.159.130.0/23 | RIPE | Valid |
| 185.187.160.0/22 | RADB, RIPE | Valid |
| 185.187.160.0/24 | RADB, RIPE | Valid |
| 185.187.161.0/24 | RIPE | Valid |
| 185.187.163.0/24 | RIPE | Valid |
| 2a0b:a880::/29 | RIPE | Valid |
| 2a0b:a880::/31 | RADB | Valid |
| 2a0b:a880::/32 | RIPE | Valid |
| 2a0c:9280::/31 | RADB | Valid |
| 2a0f:7680::/31 | RADB | 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.