Network · data from 2026-11-12
AS272118 DATALINK, C.A.
Registry name: AS272118 - DATALINK, C.A., VE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272118, 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.
| 38.150.94.0/24 | Valid | Nonecovered by 38.150.88.0/21 | 668 99% |
| 38.150.95.0/24 | Valid | Nonecovered by 38.150.88.0/21 | 668 99% |
| 38.150.89.0/24 | Valid | Nonecovered by 38.150.88.0/21 | 665 99% |
| 38.150.90.0/24 | Valid | Nonecovered by 38.150.88.0/21 | 665 99% |
| 38.150.91.0/24 | Valid | Nonecovered by 38.150.88.0/21 | 665 99% |
| 38.150.92.0/24 | Valid | Nonecovered by 38.150.88.0/21 | 2 0%low visibility |
| 38.150.88.0/24 | Valid | Other IRR onlyRADB | 663 99% |
| 2803:4f10::/34 | Valid | Other IRR onlyRADB | 630 99% |
AS-SET
PeeringDB's irr_as_set for AS272118: AS272118:AS-PEERS. 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 (AS272118 isn't in the set, or no route object for AS272118 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 | AS272118 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS272118:AS-PEERS | In no IRR database read today. | |||||
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 13 are in fix.csv.
- Route object: none6
- Route object: RIR2
- AS-SET: not found1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 38.150.94.0/24 | No route object for it. A route object for 38.150.88.0/21 with origin AS272118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272118 in the RIR database for the space. |
| Route object: none | 38.150.95.0/24 | No route object for it. A route object for 38.150.88.0/21 with origin AS272118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272118 in the RIR database for the space. |
| Route object: none | 38.150.89.0/24 | No route object for it. A route object for 38.150.88.0/21 with origin AS272118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272118 in the RIR database for the space. |
| Route object: none | 38.150.90.0/24 | No route object for it. A route object for 38.150.88.0/21 with origin AS272118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272118 in the RIR database for the space. |
| Route object: none | 38.150.91.0/24 | No route object for it. A route object for 38.150.88.0/21 with origin AS272118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272118 in the RIR database for the space. |
| Route object: none | 38.150.92.0/24 | No route object for it. A route object for 38.150.88.0/21 with origin AS272118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272118 in the RIR database for the space. |
| Route object: RIR | 38.150.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2803:4f10::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS272118:AS-PEERS | PeeringDB names AS272118:AS-PEERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS272118 whose prefix no peer sees AS272118 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.150.88.0/21 | ARIN | Valid |
| 170.81.147.0/24 | LACNIC | Valid |
| 2803:4f10::/32 | LACNIC, RADB | Valid |
| 2803:4f10:4000::/34 | RADB | 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.