Network · data from 2026-11-12
AS134497 Cine Cebu
Registry name: CINE-AS-AP - Cine Cebu, PH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134497, 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.
| 2400:6860:c000::4/127 | Invalid: maxLength | Nonecovered by 2400:6860:c000::/34 | 1 0%low visibility |
| 38.20.178.0/24 | No ROA | Nonecovered by 38.20.178.0/23 | 672 100% |
| 38.20.179.0/24 | No ROA | Nonecovered by 38.20.178.0/23 | 671 100% |
| 103.161.60.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.161.61.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 2400:6860::/34 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:6860:4000::/34 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:6860:8000::/34 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:6860:c000::/34 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS134497: AS134497:AS-CINEPH. 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 (AS134497 isn't in the set, or no route object for AS134497 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 | AS134497 in it | Not covered |
|---|---|---|---|---|---|
| AS134497:AS-CINEPH | APNIC | 2 | 1 | Yes | 1 |
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: maxLength1
- ROA: none2
- Route object: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2400:6860:c000::4/127 | ROA 2400:6860:c000::/34 AS134497 has maxLength 34; the route is a /127. Raise the maxLength, or add a ROA for 2400:6860:c000::4/127. |
| Route object: none | 2400:6860:c000::4/127 | No route object for it. A route object for 2400:6860:c000::/34 with origin AS134497 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS134497 in the RIR database for the space. |
| ROA: none | 38.20.178.0/24 | No ROA covers it. Add a ROA for AS134497, maxLength 24. |
| Route object: none | 38.20.178.0/24 | No route object for it. A route object for 38.20.178.0/23 with origin AS134497 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134497 in the RIR database for the space. |
| ROA: none | 38.20.179.0/24 | No ROA covers it. Add a ROA for AS134497, maxLength 24. |
| Route object: none | 38.20.179.0/24 | No route object for it. A route object for 38.20.178.0/23 with origin AS134497 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134497 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS134497 whose prefix no peer sees AS134497 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.20.178.0/23 | RADB | No ROA |
| 103.161.60.0/23 | APNIC, NTTCOM | 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.