Network · data from 2026-11-12
AS57575 NETMOUNTAINS
Registry name: NETM-AS NETMOUNTAINS Group GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57575, 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.
| 109.122.11.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 109.205.197.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.153.54.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a13:9a40::/32 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS57575: AS57575:AS-NETM. 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 (AS57575 isn't in the set, or no route object for AS57575 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 | AS57575 in it | Not covered |
|---|---|---|---|---|---|
| AS57575:AS-NETM | RIPE3 member sets in no database: AS199746:AS-NEXTSERV, AS215110:AS-CUSTOMERS, AS39753:AS-LIUXYON | 293 | 69 | 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 5 are in fix.csv.
- AS-SET: missing member3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS57575:AS-NETM | AS57575:AS-NETM (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it. |
| AS-SET: missing member | AS57575:AS-NETM | AS57575:AS-NETM (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it. |
| AS-SET: missing member | AS57575:AS-NETM | AS57575:AS-NETM (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it. |
Route objects not announced
Route objects with origin AS57575 whose prefix no peer sees AS57575 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.207.156.0/24 | RIPE | Valid |
| 2a13:9a41::/32 | 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.