Network · data from 2026-11-12
AS62925 CRE Network LLC
Registry name: CRENET-ASN-01 - CRE NETWORK, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62925, 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.
| 2a0e:b107:2680::/44 | No ROA | RIR databaseALTDB, RIPE | 635 100% |
| 2602:fa93:ff8::/48 | Valid | Nonecovered by 2602:fa93:ff0::/44 | 66 10% |
| 2602:fa93:ff9::/48 | Valid | Nonecovered by 2602:fa93:ff0::/44 | 66 10% |
| 2602:fa93:ff0::/44 | Valid | RIR databaseALTDB, ARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS62925: AS-CRENET. 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 (AS62925 isn't in the set, or no route object for AS62925 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 | AS62925 in it | Not covered |
|---|---|---|---|---|---|
| AS-CRENET | RIPE | 9 | 2 | Yes | 0 |
| ALTDB (also) | 9 | 2 | Yes | 0 | |
| ARIN (also) | 9 | 2 | 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 3 are in fix.csv.
- ROA: none1
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0e:b107:2680::/44 | No ROA covers it. Add a ROA for AS62925, maxLength 44. |
| Route object: none | 2602:fa93:ff8::/48 | No route object for it. A route object for 2602:fa93:ff0::/44 with origin AS62925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62925 in the RIR database for the space. |
| Route object: none | 2602:fa93:ff9::/48 | No route object for it. A route object for 2602:fa93:ff0::/44 with origin AS62925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62925 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS62925 is announced.
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.