Network · data from 2026-11-12
AS57537 Net-D-Sign GmbH
Registry name: NETDSIGN-AS Net-D-Sign GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57537, 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.152.232.0/24 | Valid | Nonecovered by 185.152.232.0/22 | 384 57% |
| 185.152.233.0/24 | Valid | Nonecovered by 185.152.232.0/22 | 384 57% |
| 185.152.234.0/24 | Valid | Nonecovered by 185.152.232.0/22 | 384 57% |
| 185.152.235.0/24 | Valid | Nonecovered by 185.152.232.0/22 | 384 57% |
| 213.148.98.0/24 | Valid | Nonecovered by 213.148.96.0/19 | 384 57% |
| 213.148.99.0/24 | Valid | Nonecovered by 213.148.96.0/19 | 384 57% |
| 185.152.232.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 213.148.96.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 2a03:2cc0::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS57537: AS-NETDSIGN. 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 (AS57537 isn't in the set, or no route object for AS57537 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 | AS57537 in it | Not covered |
|---|---|---|---|---|---|
| AS-NETDSIGN | RIPE | 1 | 1 | Yes | 0 |
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 6 are in fix.csv.
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.152.232.0/24 | No route object for it. A route object for 185.152.232.0/22 with origin AS57537 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57537 in the RIR database for the space. |
| Route object: none | 185.152.233.0/24 | No route object for it. A route object for 185.152.232.0/22 with origin AS57537 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57537 in the RIR database for the space. |
| Route object: none | 185.152.234.0/24 | No route object for it. A route object for 185.152.232.0/22 with origin AS57537 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57537 in the RIR database for the space. |
| Route object: none | 185.152.235.0/24 | No route object for it. A route object for 185.152.232.0/22 with origin AS57537 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57537 in the RIR database for the space. |
| Route object: none | 213.148.98.0/24 | No route object for it. A route object for 213.148.96.0/19 with origin AS57537 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57537 in the RIR database for the space. |
| Route object: none | 213.148.99.0/24 | No route object for it. A route object for 213.148.96.0/19 with origin AS57537 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57537 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS57537 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.