Network · data from 2026-11-12
AS27745 Telefonia Bonairiano N.V.
Registry name: AS27745 - Telefonia Bonairiano N.V., BQ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27745, 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.
| 186.159.104.0/21 | Valid | Nonecovered by 186.159.96.0/20 | 673 100% |
| 190.4.64.0/21 | Valid | Nonecovered by 190.4.64.0/20 | 672 100% |
| 190.4.72.0/21 | Valid | Nonecovered by 190.4.64.0/20 | 672 100% |
| 190.4.78.0/24 | Valid | Nonecovered by 190.4.64.0/20 | 672 100% |
| 200.6.150.0/23 | Valid | Nonecovered by 200.6.144.0/21 | 672 100% |
| 186.159.96.0/21 | Valid | Nonecovered by 186.159.96.0/20 | 670 100% |
| 161.0.80.0/20 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 186.159.96.0/20 | Valid | RIR databaseLACNIC, NTTCOM | 673 100% |
| 190.4.64.0/20 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 672 100% |
| 200.6.144.0/21 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 2803:a000::/32 | Valid | RIR databaseLACNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS27745: NTTCOM::AS-TELBO. 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 (AS27745 isn't in the set, or no route object for AS27745 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 | AS27745 in it | Not covered |
|---|---|---|---|---|---|
| NTTCOM::AS-TELBO | NTTCOM | 4 | 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 7 are in fix.csv.
- Route object: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 186.159.104.0/21 | No route object for it. A route object for 186.159.96.0/20 with origin AS27745 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27745 in the RIR database for the space. |
| Route object: none | 190.4.64.0/21 | No route object for it. A route object for 190.4.64.0/20 with origin AS27745 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27745 in the RIR database for the space. |
| Route object: none | 190.4.72.0/21 | No route object for it. A route object for 190.4.64.0/20 with origin AS27745 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27745 in the RIR database for the space. |
| Route object: none | 190.4.78.0/24 | No route object for it. A route object for 190.4.64.0/20 with origin AS27745 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27745 in the RIR database for the space. |
| Route object: none | 200.6.150.0/23 | No route object for it. A route object for 200.6.144.0/21 with origin AS27745 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27745 in the RIR database for the space. |
| Route object: none | 186.159.96.0/21 | No route object for it. A route object for 186.159.96.0/20 with origin AS27745 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27745 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27745 whose prefix no peer sees AS27745 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.2.175.0/24 | NTTCOM | 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.