Network · data from 2026-11-12
AS136244 Panay Broadband / Buenavista CATV Inc.
Registry name: PBBCTI-AS-AP - Panay Broadband / Buenavista Cable TV Inc., PH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136244, 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.10.88.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 3 0%low visibility |
| 38.10.88.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 3 0%low visibility |
| 38.10.89.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 3 0%low visibility |
| 38.10.90.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 2 0%low visibility |
| 103.84.176.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.84.176.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.84.177.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 163.8.40.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 163.8.40.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 163.8.40.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 163.8.42.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 163.8.42.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 163.8.43.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 163.8.41.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df0:bf00::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS136244: AS136244:AS-PBBCTI-PH. 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 (AS136244 isn't in the set, or no route object for AS136244 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 | AS136244 in it | Not covered |
|---|---|---|---|---|---|
| AS136244:AS-PBBCTI-PH | APNIC | 2 | 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 12 are in fix.csv.
- ROA: none4
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.10.88.0/23 | No ROA covers it. Add a ROA for AS136244, maxLength 23. |
| Route object: RIR | 38.10.88.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 38.10.88.0/24 | No ROA covers it. Add a ROA for AS136244, maxLength 24. |
| Route object: RIR | 38.10.88.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 38.10.89.0/24 | No ROA covers it. Add a ROA for AS136244, maxLength 24. |
| Route object: RIR | 38.10.89.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 38.10.90.0/23 | No ROA covers it. Add a ROA for AS136244, maxLength 23. |
| Route object: RIR | 38.10.90.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS136244 whose prefix no peer sees AS136244 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.10.88.0/22 | RADB | No ROA |
| 38.10.90.0/24 | NTTCOM, RADB | No ROA |
| 38.10.91.0/24 | NTTCOM, RADB | No ROA |
| 2001:df0:bf00:bca::/64 | APNIC | 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.