Network · data from 2026-11-12
AS33554 Neutral Data
Registry name: ASN-NEUTRAL-DATA - Neutral Data Centers Corp., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33554, 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.
| 67.21.231.0/24 | Invalid: maxLength | Nonecovered by 67.21.224.0/19 | 26 4%low visibility |
| 63.142.160.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 66.51.240.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 67.21.224.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 204.16.200.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 208.71.112.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 204.14.16.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 2001:4938::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS33554: AS-NDCC-CUSTOMERS. 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 (AS33554 isn't in the set, or no route object for AS33554 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 | AS33554 in it | Not covered |
|---|---|---|---|---|---|
| AS-NDCC-CUSTOMERS | RADB2 member sets in no database: AS-MOTP, AS9327:AS-HOPCOUNT | 65 | 12 | 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.
- ROA: maxLength1
- Route object: none1
- AS-SET: missing member2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 67.21.231.0/24 | ROA 67.21.224.0/19 AS33554 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 67.21.231.0/24. |
| Route object: none | 67.21.231.0/24 | No route object for it. A route object for 67.21.224.0/19 with origin AS33554 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33554 in the RIR database for the space. |
| AS-SET: missing member | AS-NDCC-CUSTOMERS | AS-NDCC-CUSTOMERS (RADB) lists AS-MOTP; no IRR database read has it. |
| AS-SET: missing member | AS-NDCC-CUSTOMERS | AS-NDCC-CUSTOMERS (RADB) lists AS9327:AS-HOPCOUNT; no IRR database read has it. |
Route objects not announced
Route objects with origin AS33554 whose prefix no peer sees AS33554 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.112.88.0/24 | RADB | No ROA |
| 38.116.194.0/24 | RADB | No ROA |
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.