Network · data from 2026-11-12
AS46373 Concentus.net
Registry name: CONCENTUSNET - Concentus.net, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46373, 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.
| 64.94.64.0/24 | No ROA | Nonecovered by 64.94.64.0/23 | 671 100% |
| 64.94.65.0/24 | No ROA | Nonecovered by 64.94.64.0/23 | 671 100% |
| 64.94.66.0/24 | No ROA | Nonecovered by 64.94.66.0/23 | 671 100% |
| 64.94.67.0/24 | No ROA | Nonecovered by 64.94.66.0/23 | 671 100% |
| 38.129.106.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS46373: AS-CTS-MIDATL. 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 (AS46373 isn't in the set, or no route object for AS46373 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 | AS46373 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-CTS-MIDATL | In no IRR database read today. | |||||
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 15 are in fix.csv.
- ROA: none5
- Route object: none4
- Route object: RIR1
- AS-SET: not found1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.94.64.0/24 | No ROA covers it. Add a ROA for AS46373, maxLength 24. |
| Route object: none | 64.94.64.0/24 | No route object for it. A route object for 64.94.64.0/23 with origin AS46373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46373 in the RIR database for the space. |
| ROA: none | 64.94.65.0/24 | No ROA covers it. Add a ROA for AS46373, maxLength 24. |
| Route object: none | 64.94.65.0/24 | No route object for it. A route object for 64.94.64.0/23 with origin AS46373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46373 in the RIR database for the space. |
| ROA: none | 64.94.66.0/24 | No ROA covers it. Add a ROA for AS46373, maxLength 24. |
| Route object: none | 64.94.66.0/24 | No route object for it. A route object for 64.94.66.0/23 with origin AS46373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46373 in the RIR database for the space. |
| ROA: none | 64.94.67.0/24 | No ROA covers it. Add a ROA for AS46373, maxLength 24. |
| Route object: none | 64.94.67.0/24 | No route object for it. A route object for 64.94.66.0/23 with origin AS46373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46373 in the RIR database for the space. |
| ROA: none | 38.129.106.0/24 | No ROA covers it. Add a ROA for AS46373, maxLength 24. |
| Route object: RIR | 38.129.106.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-CTS-MIDATL | PeeringDB names AS-CTS-MIDATL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS46373 whose prefix no peer sees AS46373 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.94.64.0/22 | RADB | No ROA |
| 64.94.64.0/23 | RADB | No ROA |
| 64.94.66.0/23 | RADB | No ROA |
| 2001:470:1ca::/48 | ARIN | 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.