Network · data from 2026-11-12
AS266809 NERVICOM
Registry name: AS266809 - NERVICOM, C.A., VE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266809, 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.
| 45.236.28.0/23 | Valid | Nonecovered by 45.236.28.0/22 | 671 100% |
| 45.236.30.0/23 | Valid | Nonecovered by 45.236.28.0/22 | 671 100% |
| 38.188.240.0/23 | Valid | Nonecovered by 38.188.240.0/22 | 2 0%low visibility |
| 38.188.241.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 38.188.242.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.236.30.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 38.188.240.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 38.188.243.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 45.236.28.0/22 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 45.236.31.0/24 | Valid | RIR databaseLACNIC, RADB | 668 99% |
| 38.57.105.0/24 | Valid | RIR databaseARIN, RADB | 667 99% |
| 45.236.28.0/24 | Valid | RIR databaseLACNIC, RADB | 667 99% |
| 45.236.29.0/24 | Valid | RIR databaseLACNIC, RADB | 666 99% |
| 2803:60a0::/36 | Valid | RIR databaseLACNIC | 634 100% |
| 2803:60a0::/32 | Valid | RIR databaseLACNIC, RADB | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS266809: AS-NERVICOM. 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 (AS266809 isn't in the set, or no route object for AS266809 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 | AS266809 in it | Not covered |
|---|---|---|---|---|---|
| AS-NERVICOM | RADB | 37 | 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 11 are in fix.csv.
- Route object: none3
- Route object: RIR5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.236.28.0/23 | No route object for it. A route object for 45.236.28.0/22 with origin AS266809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266809 in the RIR database for the space. |
| Route object: none | 45.236.30.0/23 | No route object for it. A route object for 45.236.28.0/22 with origin AS266809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266809 in the RIR database for the space. |
| Route object: none | 38.188.240.0/23 | No route object for it. A route object for 38.188.240.0/22 with origin AS266809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266809 in the RIR database for the space. |
| Route object: RIR | 38.188.241.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 38.188.242.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.236.30.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 38.188.240.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 38.188.243.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266809 whose prefix no peer sees AS266809 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.188.240.0/22 | ARIN | Valid |
| 2001:470:3b3::/48 | ARIN | Valid |
| 2803:60a0:1000::/36 | LACNIC | 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.