bgpreport

Network · data from 2026-11-12

AS132021 Kalibo Cable Television Network

Registry name: KALIBOCABLE-PH - Kalibo Cable Television Network Inc, PH · PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS132021, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132021, 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.

103.5.0.0/23 Valid RIR databaseAPNIC, NTTCOM 673 100% 68
103.5.0.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
103.5.1.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
103.5.2.0/23 Valid RIR databaseAPNIC, NTTCOM 673 100% 68
103.5.2.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
103.5.3.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
126.209.88.0/24 Valid RIR databaseAPNIC 673 100% 69
126.209.89.0/24 Valid RIR databaseAPNIC 673 100% 69
126.209.90.0/24 Valid RIR databaseAPNIC 673 100% 69

AS-SET

PeeringDB's irr_as_set for AS132021: AS132021:AS-KALIBOCABLE-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 (AS132021 isn't in the set, or no route object for AS132021 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.

NameDatabaseASNsSets Route objectsAS132021 in itNot covered
AS132021:AS-KALIBOCABLE-PH APNIC 61111 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 13 are in fix.csv.

  • Route object: not announced13

Route objects not announced

Route objects with origin AS132021 whose prefix no peer sees AS132021 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.5.0.0/22APNIC, NTTCOMValid
126.209.88.0/22APNICValid
126.209.88.0/23APNICValid
126.209.91.0/24APNICValid
2403:cd00::/32APNICValid
2403:cd00::/40APNICValid
2403:cd00::/48APNICValid
2403:cd00:1::/48APNICValid
2403:cd00:2::/48APNICValid
2403:cd00:100::/40APNICValid
2403:cd00:100::/48APNICValid
2403:cd00:101::/48APNICValid
2403:cd00:102::/48APNICValid

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.