bgpreport

Network · data from 2026-11-12

AS56207 COMCLARK-PH - ComClark Network & Technology Corp

Registry name: COMCLARK-PH - ComClark Network & Technology Corp, PH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56207, 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.
182.18.196.0/24 Valid Other origin only 666 99% 67
2403:4c0:7800::/37 Valid None 636 100% 69
139.135.192.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.196.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.200.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.204.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.208.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.212.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.216.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.224.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.228.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.232.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.236.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.240.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.244.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.248.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.252.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.254.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
139.135.255.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
202.81.164.0/24 Valid RIR databaseAPNIC 671 100% 67
139.135.220.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2

AS-SET

AS56207 isn't in PeeringDB, where networks name their 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 4 are in fix.csv.

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none182.18.196.0/24Route objects for it name AS23944. Add a route object with origin AS56207 in the RIR database for the space.666 of 673
Route object: none2403:4c0:7800::/37No route object for it. Add a route object with origin AS56207 in the RIR database for the space.636 of 636

Route objects not announced

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

61.9.64.0/24APNICValid
139.135.252.0/22APNIC, 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.