bgpreport

Network · data from 2026-11-12

AS147042 Panabo Satellite Cable Television

Registry name: PANABO-AS-AP - Panabo Satellite Cable Television Inc., PH · PeeringDB

3IPv4 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
17Route objects not announced registered with origin AS147042, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS147042, 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.173.110.0/23 Valid RIR databaseAPNIC 673 100% 66
103.173.110.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.173.111.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66

AS-SET

AS147042's PeeringDB record names no AS-SET.

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 17 are in fix.csv.

  • Route object: not announced17

Route objects not announced

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

2407:e640::/32APNICValid
2407:e640::/36APNICValid
2407:e640:1000::/36APNICValid
2407:e640:2000::/36APNICValid
2407:e640:3000::/36APNICValid
2407:e640:4000::/36APNICValid
2407:e640:5000::/36APNICValid
2407:e640:6000::/36APNICValid
2407:e640:7000::/36APNICValid
2407:e640:8000::/36APNICValid
2407:e640:9000::/36APNICValid
2407:e640:a000::/36APNICValid
2407:e640:b000::/36APNICValid
2407:e640:c000::/36APNICValid
2407:e640:d000::/36APNICValid
2407:e640:e000::/36APNICValid
2407:e640:f000::/36APNICValid

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.