Network · data from 2026-11-12
AS55243 CEDARNET - Cedar Wireless, Inc.
Registry name: CEDARNET - Cedar Wireless, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55243, 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.
| 2620:26:c002::/48 | Valid | Nonecovered by 2620:26:c000::/44 | 635 100% |
| 199.119.166.0/24 | Valid | RIR databaseARIN | 673 100% |
| 198.148.6.0/24 | Valid | RIR databaseARIN | 671 100% |
| 198.148.7.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.119.164.0/24 | Valid | RIR databaseARIN | 671 100% |
| 199.119.165.0/24 | Valid | RIR databaseARIN | 671 100% |
| 2620:26:c000::/48 | Valid | RIR databaseARIN | 635 100% |
| 2620:26:c001::/48 | Valid | RIR databaseARIN | 635 100% |
| 2001:470:96::/48 | Valid | RIR databaseARIN | 634 100% |
AS-SET
AS55243 isn't in PeeringDB, where networks name their AS-SET.
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: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2620:26:c002::/48 | No route object for it. A route object for 2620:26:c000::/44 with origin AS55243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55243 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55243 whose prefix no peer sees AS55243 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 198.148.6.0/23 | RADB | No ROA |
| 199.119.164.0/22 | RADB | No ROA |
| 199.119.167.0/24 | ARIN | Valid |
| 2606:a600:0:e00::/56 | RADB | No ROA |
| 2620:26:c000::/44 | 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.