bgpreport

Network · data from 2026-11-12

AS17970 Tri.ph

Registry name: SKYBB-AS-AP - SKYBroadband SKYCable Corporation, PH · PeeringDB

26IPv4 routes 96.2% RPKI valid · 96.2% with a route object
0IPv6 routes
1RPKI invalid 0 origin · 1 maxLength
0No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
68Route objects not announced registered with origin AS17970, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17970, 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.
219.90.94.0/24 Invalid: maxLength Nonecovered by 219.90.92.0/22 2 0%low visibility 3
43.255.216.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
61.9.32.0/19 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
61.14.192.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
61.14.199.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
103.239.200.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
202.81.168.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
202.81.168.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
202.81.172.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
202.81.174.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
203.76.192.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
203.76.192.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
203.76.195.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
203.76.196.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
203.76.196.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.80.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.80.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.84.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.84.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.86.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.88.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.90.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.91.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.92.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
219.90.92.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
61.9.96.0/19 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS17970'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 70 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced68
ChangePrefix or setDetailFull-table peers
ROA: maxLength219.90.94.0/24ROA 219.90.80.0/20 AS17970 has maxLength 20; ROA 219.90.92.0/22 AS17970 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 219.90.94.0/24.2 of 673
Route object: none219.90.94.0/24No route object for it. A route object for 219.90.92.0/22 with origin AS17970 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17970 in the RIR database for the space.2 of 673

Route objects not announced

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

61.9.0.0/17NTTCOM, RADBNo ROA
61.9.32.0/20APNICValid
61.9.32.0/21APNICValid
61.9.32.0/22APNICValid
61.9.36.0/22APNICValid
61.9.40.0/21APNICValid
61.9.40.0/22APNICValid
61.9.44.0/22APNICValid
61.9.48.0/20APNICValid
61.9.48.0/21APNICValid
61.9.48.0/22APNICValid
61.9.52.0/22APNICValid
61.9.56.0/21APNICValid
61.9.56.0/22APNICValid
61.9.60.0/22APNICValid
61.9.96.0/20APNICValid
61.9.96.0/21APNICValid
61.9.96.0/22APNIC, NTTCOM, RADBValid
61.9.100.0/22APNICValid
61.9.104.0/21APNICValid
61.9.104.0/22APNICValid
61.9.108.0/22APNICValid
61.9.112.0/20APNICValid
61.9.112.0/21APNICValid
61.9.112.0/22APNICValid
61.9.116.0/22APNICValid
61.9.120.0/21APNICValid
61.9.120.0/22APNICValid
61.9.124.0/22APNICValid
61.14.192.0/22APNIC, NTTCOM, RADBValid
61.14.192.0/23APNIC, NTTCOM, RADBValid
61.14.192.0/24APNIC, NTTCOM, RADBValid
61.14.193.0/24APNIC, NTTCOM, RADBValid
61.14.194.0/23APNIC, NTTCOM, RADBValid
61.14.194.0/24APNIC, NTTCOM, RADBValid
61.14.195.0/24APNIC, NTTCOM, RADBValid
61.14.196.0/22APNIC, NTTCOM, RADBValid
61.14.196.0/23APNIC, NTTCOM, RADBValid
61.14.196.0/24APNIC, NTTCOM, RADBValid
61.14.197.0/24APNIC, NTTCOM, RADBValid
61.14.198.0/23APNIC, NTTCOM, RADBValid
61.14.198.0/24APNIC, NTTCOM, RADBValid
202.81.160.0/19NTTCOMNo ROA
202.81.160.0/20NTTCOM, RADBNo ROA
202.81.172.0/24APNIC, NTTCOM, RADBValid
202.81.173.0/24APNIC, NTTCOM, RADBValid
202.81.175.0/24APNIC, NTTCOM, RADBValid
202.81.176.0/20NTTCOMNo ROA
203.76.192.0/18RADBNo ROA
203.76.192.0/19NTTCOMNo ROA
203.76.192.0/20NTTCOM, RADBNo ROA
203.76.208.0/20NTTCOMNo ROA
203.76.240.0/20NTTCOMNo ROA
219.90.64.0/19NTTCOMNo ROA
219.90.64.0/20NTTCOMNo ROA
219.90.68.0/24NTTCOMNo ROA
219.90.69.0/24NTTCOMNo ROA
219.90.70.0/24NTTCOMNo ROA
219.90.71.0/24NTTCOMNo ROA
219.90.72.0/24NTTCOMNo ROA
219.90.73.0/24NTTCOMNo ROA
219.90.74.0/24NTTCOMNo ROA
219.90.75.0/24NTTCOMNo ROA
219.90.76.0/24NTTCOMNo ROA
219.90.77.0/24NTTCOMNo ROA
219.90.78.0/24NTTCOMNo ROA
219.90.79.0/24NTTCOMNo ROA
219.90.87.0/24APNIC, NTTCOM, RADBValid

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.