Network · data from 2026-11-12
AS11051 Cyberverse
Registry name: CYBERVERSE - Evocative, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11051, 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.
| 174.139.1.0/24 | No ROA | None | 3 0%low visibility |
| 67.43.144.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 64.118.160.0/24 | Valid | RIR databaseARIN | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS11051: AS-VPLS. 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 (AS11051 isn't in the set, or no route object for AS11051 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 | AS11051 in it | Not covered |
|---|---|---|---|---|---|
| AS-VPLS | RADBlists itself further down4 member sets in no database: AS207432:AS-ALL, AS207432:AS-CS, AS213607:AS-TEST, AS47614:AS-DOWNSTREAM | 489 | 95 | Yes | 1 |
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 10 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR1
- AS-SET: missing member4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 174.139.1.0/24 | No ROA covers it. Add a ROA for AS11051, maxLength 24. |
| Route object: none | 174.139.1.0/24 | No route object for it. Add a route object with origin AS11051 in the RIR database for the space. |
| Route object: RIR | 67.43.144.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-VPLS | AS-VPLS (RADB) lists AS207432:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-VPLS | AS-VPLS (RADB) lists AS207432:AS-CS; no IRR database read has it. |
| AS-SET: missing member | AS-VPLS | AS-VPLS (RADB) lists AS213607:AS-TEST; no IRR database read has it. |
| AS-SET: missing member | AS-VPLS | AS-VPLS (RADB) lists AS47614:AS-DOWNSTREAM; no IRR database read has it. |
Route objects not announced
Route objects with origin AS11051 whose prefix no peer sees AS11051 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.43.144.0/23 | ARIN | Valid |
| 67.118.160.0/24 | RADB | No ROA |
| 174.139.145.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.