Network · data from 2026-11-12
AS204548 Kamatera INC Germany ASN
Registry name: CLOUDWEBMANAGE-IL-FR Kamatera Inc, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204548, 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.
| 154.222.133.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 63.250.59.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 63.250.60.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.108.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.229.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.229.85.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.229.86.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.229.87.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 103.13.211.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 103.240.144.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 113.30.190.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 113.30.191.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.47.174.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.53.210.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.139.230.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.181.10.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.227.108.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.227.111.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.237.14.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.237.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.237.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.237.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.247.118.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.36.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.37.80.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.238.122.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.115.110.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.83.41.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.147.248.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.28.6.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a06:c5c0:1100::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a07:3b80:1::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2.59.118.0/24 | Valid | RIR databaseRIPE | 219 33% |
AS-SET
AS204548'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 1 are in fix.csv.
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 154.222.133.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS204548 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.