Network · data from 2026-11-12
AS12212 Ravand Cybertech
Registry name: RAVAND - Ravand Cybertech Inc., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12212, 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.
| 207.176.224.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 207.176.223.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 198.55.62.0/24 | No ROA | RIR databaseARIN, RADB | 2 0%low visibility |
| 66.179.20.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS12212: AS-RAVAND. 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 (AS12212 isn't in the set, or no route object for AS12212 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 | AS12212 in it | Not covered |
|---|---|---|---|---|---|
| AS-RAVAND | RADB1 member set in no database: AS53356:AS-FRC | 10 | 1 | Yes | 0 |
| ARIN (also)1 member set in no database: AS53356:AS-FRC | 7 | 1 | 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 16 are in fix.csv.
- ROA: none3
- Route object: RIR2
- AS-SET: missing member1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 207.176.224.0/24 | No ROA covers it. Add a ROA for AS12212, maxLength 24. |
| Route object: RIR | 207.176.224.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 207.176.223.0/24 | No ROA covers it. Add a ROA for AS12212, maxLength 24. |
| Route object: RIR | 207.176.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.55.62.0/24 | No ROA covers it. Add a ROA for AS12212, maxLength 24. |
| AS-SET: missing member | AS-RAVAND | AS-RAVAND (RADB) lists AS53356:AS-FRC; no IRR database read has it. |
Route objects not announced
Route objects with origin AS12212 whose prefix no peer sees AS12212 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.59.71.0/24 | ARIN | Valid |
| 66.179.20.0/23 | ARIN, RADB | Valid |
| 66.179.21.0/24 | ARIN, RADB | Valid |
| 204.225.179.0/24 | RADB | No ROA |
| 206.130.26.0/24 | RADB | No ROA |
| 2602:fd50:10::/48 | RADB | No ROA |
| 2602:fed2::/32 | RADB | No ROA |
| 2605:8900:f000::/36 | ARIN | Valid |
| 2606:a80::/32 | RADB | No ROA |
| 2a0f:9400::/29 | 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.