Network · data from 2026-11-12
AS15874 Interkam
Registry name: INTERKAM INTERKAM sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15874, 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.
| 37.130.49.0/24 | Valid | Nonecovered by 37.130.0.0/18 | 22 3%low visibility |
| 37.130.0.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 91.231.24.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.231.25.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.231.26.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.231.27.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS15874'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 5 are in fix.csv.
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 37.130.49.0/24 | No route object for it. A route object for 37.130.0.0/18 with origin AS15874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15874 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15874 whose prefix no peer sees AS15874 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.174.232.0/22 | RIPE | Valid |
| 46.174.238.0/24 | RIPE | Valid |
| 2a0c:1680::/29 | RIPE | Valid |
| 2a10:f781:10:c5e::/64 | RIPE | No ROA |
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.