Network · data from 2026-11-12
AS45499 Cablelink & Holdings Corp. Transit AS Internet Service Provider Philippines
Registry name: CABLELINK-TRANSIT-AS-AP - Cablelink & Holdings Corp. Transit AS Internet Service Provider Philippines, PH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45499, 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.60.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.5.61.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.5.62.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.5.63.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 110.5.64.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 110.5.64.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 110.5.66.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 110.5.67.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 110.5.68.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 110.5.69.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 110.5.70.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 110.5.71.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.81.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.82.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.85.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.87.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.88.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.89.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.90.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.91.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.92.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.94.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.206.224.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.206.224.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 116.206.225.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.118.244.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.118.244.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.118.245.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.118.247.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.235.80.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 111.235.83.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 111.235.86.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 111.235.93.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 111.235.80.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 2401:bc00::/32 | Valid | RIR databaseAPNIC | 635 100% |
| 2401:bc00:3::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2401:bc00:1::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2401:bc00:2::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2401:bc00:4::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2401:bc00:5::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2401:bc00:6::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 111.235.95.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 116.206.226.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 116.206.227.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 203.118.246.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS45499: AS45499. 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 (AS45499 isn't in the set, or no route object for AS45499 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 | AS45499 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS45499 | A single AS number, not a set: AS45499 (this network), 51 route objects. | |||||
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 6 are in fix.csv.
- Route object: not announced6
Route objects not announced
Route objects with origin AS45499 whose prefix no peer sees AS45499 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.5.60.0/22 | APNIC, NTTCOM, RADB | Valid |
| 110.5.65.0/24 | APNIC, NTTCOM, RADB | Valid |
| 111.235.84.0/24 | APNIC, NTTCOM, RADB | Valid |
| 2001:470:291::/48 | ARIN | Valid |
| 2001:470:2f0::/48 | ARIN | Valid |
| 2001:470:48d::/48 | ARIN | 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.