Network · data from 2026-11-12
AS50118 Caribbean Telecom S.A
Registry name: CARITELE-AS Caribbean Telecom S.A, AI · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50118, 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.
| 2602:fb92:c00::/44 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 86.53.164.0/24 | Valid | None | 672 100% |
| 86.53.165.0/24 | Valid | None | 672 100% |
| 64.81.72.0/22 | Valid | RIR databaseARIN | 672 100% |
| 217.217.210.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS50118: AS50118:AS-CARITELE. 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 (AS50118 isn't in the set, or no route object for AS50118 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 | AS50118 in it | Not covered |
|---|---|---|---|---|---|
| AS50118:AS-CARITELE | RIPE | 0 | 1 | No | 5 |
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 8 are in fix.csv.
- ROA: none1
- Route object: none2
- AS-SET: own ASN1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:fb92:c00::/44 | No ROA covers it. Add a ROA for AS50118, maxLength 44. |
| Route object: none | 86.53.164.0/24 | No route object for it. Add a route object with origin AS50118 in the RIR database for the space. |
| Route object: none | 86.53.165.0/24 | No route object for it. Add a route object with origin AS50118 in the RIR database for the space. |
| AS-SET: own ASN | AS50118:AS-CARITELE | AS50118 isn't in AS50118:AS-CARITELE (RIPE) once expanded. Add AS50118 to it. |
Route objects not announced
Route objects with origin AS50118 whose prefix no peer sees AS50118 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 104.192.94.0/24 | ARIN | No ROA |
| 104.192.95.0/24 | ARIN | No ROA |
| 2602:fb92:5a0::/44 | ARIN | No ROA |
| 2602:fb92:c00::/38 | ARIN | 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.