Network · data from 2026-11-12
AS213305 SIMSALASIMDE
Registry name: SIMSALASIMDE Simsalasim Germany GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213305, 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.
| 185.196.9.0/24 | No ROA | None | 98 15% |
| 154.17.82.0/24 | Valid | Nonecovered by 154.17.82.0/23 | 671 100% |
| 154.17.83.0/24 | Valid | Nonecovered by 154.17.82.0/23 | 671 100% |
| 2a04:1a00::/32 | Valid | Nonecovered by 2a04:1a00::/29 | 634 100% |
| 38.188.112.0/20 | Valid | RIR databaseARIN | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS213305: RADB::AS213305. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS213305 isn't in the set, or no route object for AS213305 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS213305 in it | Not covered | |
|---|---|---|---|---|---|---|
| RADB::AS213305 | A single AS number, not a set: AS213305 (this network), 4 route objects. | |||||
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 8 are in fix.csv.
- ROA: none1
- Route object: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.196.9.0/24 | No ROA covers it. Add a ROA for AS213305, maxLength 24. |
| Route object: none | 185.196.9.0/24 | No route object for it. Add a route object with origin AS213305 in the RIR database for the space. |
| Route object: none | 154.17.82.0/24 | No route object for it. A route object for 154.17.82.0/23 with origin AS213305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213305 in the RIR database for the space. |
| Route object: none | 154.17.83.0/24 | No route object for it. A route object for 154.17.82.0/23 with origin AS213305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213305 in the RIR database for the space. |
| Route object: none | 2a04:1a00::/32 | No route object for it. A route object for 2a04:1a00::/29 with origin AS213305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213305 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213305 whose prefix no peer sees AS213305 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.17.82.0/23 | ARIN | Valid |
| 206.148.2.0/23 | ARIN | Valid |
| 2a04:1a00::/29 | RIPE | 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.