Network · data from 2026-11-12
AS59437 Northern Data
Registry name: NORTHERNDATA Northern Data AG, DE · PeeringDB
32IPv4 routes
87.5% RPKI valid · 68.8% with a route object
11IPv6 routes
100.0% RPKI valid · 90.9% with a route object
4RPKI invalid
0 origin · 4 maxLength
0No ROA
11 with no route object for this origin
4Low visibility
seen by under 10% of full-table peers
18Route objects not announced
registered with origin AS59437, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS59437, 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.
| 176.56.202.34/32 | Invalid: maxLength | Nonecovered by 176.56.192.0/19 | 2 0%low visibility |
| 176.56.202.38/32 | Invalid: maxLength | Nonecovered by 176.56.192.0/19 | 2 0%low visibility |
| 176.56.212.42/32 | Invalid: maxLength | Nonecovered by 176.56.192.0/19 | 2 0%low visibility |
| 176.56.212.58/32 | Invalid: maxLength | Nonecovered by 176.56.192.0/19 | 2 0%low visibility |
| 176.56.192.0/21 | Valid | Nonecovered by 176.56.192.0/19 | 672 100% |
| 176.56.192.0/24 | Valid | Nonecovered by 176.56.192.0/19 | 672 100% |
| 176.56.200.0/21 | Valid | Nonecovered by 176.56.192.0/19 | 672 100% |
| 176.56.204.0/23 | Valid | Nonecovered by 176.56.192.0/19 | 672 100% |
| 176.56.212.0/24 | Valid | Nonecovered by 176.56.192.0/19 | 672 100% |
| 176.56.213.0/24 | Valid | Nonecovered by 176.56.192.0/19 | 672 100% |
| 2a03:90c0:2b6::/48 | Valid | Nonecovered by 2a03:90c0:2b0::/44 | 634 100% |
| 85.234.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.234.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.234.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.234.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.120.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 92.38.143.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.119.168.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.119.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.56.208.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 176.56.210.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.251.18.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.194.200.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.239.86.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.156.254.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.241.110.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.211.49.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 198.212.32.0/24 | Valid | RIR databaseARIN | 672 100% |
| 85.234.78.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.234.79.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.234.82.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 176.56.192.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 176.56.206.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 2606:c4c0::/48 | Valid | RIR databaseARIN | 635 100% |
| 2a03:90c0:2b0::/44 | Valid | RIR databaseRIPE | 635 100% |
| 2a03:90c0:680::/44 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:3c80::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:3c81::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:3c80::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0c:3c82::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a0c:3c83::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a0b:d40::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a11:cc80::/29 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS59437: AS-NORTHERNDATA. 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 (AS59437 isn't in the set, or no route object for AS59437 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 | AS59437 in it | Not covered |
|---|---|---|---|---|---|
| AS-NORTHERNDATA | RIPElists itself further down | 4 | 2 | Yes | 4 |
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 33 are in fix.csv.
- ROA: maxLength4
- Route object: none11
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 176.56.202.34/32 | ROA 176.56.192.0/19 AS59437 has maxLength 24; ROA 176.56.200.0/21 AS59437 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 176.56.202.34/32. |
| Route object: none | 176.56.202.34/32 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59437 in the RIR database for the space. |
| ROA: maxLength | 176.56.202.38/32 | ROA 176.56.192.0/19 AS59437 has maxLength 24; ROA 176.56.200.0/21 AS59437 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 176.56.202.38/32. |
| Route object: none | 176.56.202.38/32 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59437 in the RIR database for the space. |
| ROA: maxLength | 176.56.212.42/32 | ROA 176.56.192.0/19 AS59437 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 176.56.212.42/32. |
| Route object: none | 176.56.212.42/32 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59437 in the RIR database for the space. |
| ROA: maxLength | 176.56.212.58/32 | ROA 176.56.192.0/19 AS59437 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 176.56.212.58/32. |
| Route object: none | 176.56.212.58/32 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59437 in the RIR database for the space. |
| Route object: none | 176.56.192.0/21 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59437 in the RIR database for the space. |
| Route object: none | 176.56.192.0/24 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59437 in the RIR database for the space. |
| Route object: none | 176.56.200.0/21 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59437 in the RIR database for the space. |
| Route object: none | 176.56.204.0/23 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59437 in the RIR database for the space. |
| Route object: none | 176.56.212.0/24 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59437 in the RIR database for the space. |
| Route object: none | 176.56.213.0/24 | No route object for it. A route object for 176.56.192.0/19 with origin AS59437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59437 in the RIR database for the space. |
| Route object: none | 2a03:90c0:2b6::/48 | No route object for it. A route object for 2a03:90c0:2b0::/44 with origin AS59437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59437 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59437 whose prefix no peer sees AS59437 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.234.86.0/24 | RIPE | Valid |
| 85.234.90.0/24 | RIPE | Valid |
| 85.234.93.0/24 | RIPE | Valid |
| 87.121.28.0/22 | RIPE | Valid |
| 91.226.226.0/24 | RIPE | Valid |
| 93.113.170.0/24 | RIPE | Valid |
| 109.61.121.0/24 | RIPE | Valid |
| 185.159.86.0/24 | RIPE | Valid |
| 2001:470:328::/48 | ARIN | Valid |
| 2a03:90c0:650::/44 | RIPE | Valid |
| 2a03:90c0:7a0::/44 | RIPE | Valid |
| 2a03:90c0:7b0::/44 | RIPE | Valid |
| 2a0c:3c81::/48 | RIPE | Valid |
| 2a0c:3c84::/32 | RIPE | Valid |
| 2a0c:3c85::/32 | RIPE | Valid |
| 2a0c:3c86::/32 | RIPE | Valid |
| 2a0c:3c87::/32 | RIPE | Valid |
| 2a10:9640::/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.