ixreport

First Cagayan Converge Data Center, Inc

AS131303 · LRData Center and Solutions, Inc.

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
1Using the route servers
0Facilities in PeeringDB

Tools: Where can I peer with First Cagayan Converge Data Center, Inc? · Where should First Cagayan Converge Data Center, Inc peer next? · Compare First Cagayan Converge Data Center, Inc with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list

Nothing to fix: First Cagayan Converge Data Center, Inc's PeeringDB record matches the member lists of the exchange we could compare (the others publish no list we could read).

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where First Cagayan Converge Data Center, Inc's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 3G across 3 exchanges.

Hong Kong HKIX Hong Kong, Hong Kong 123.255.91.12 1G Yes Both
Philippines PhOpenIX-Manila Manila, Philippines 198.32.172.100 1G PeeringDB
Taiwan TPIX-TW Taipei/Taiwan, Taiwan 203.163.222.58 1G PeeringDB

First Cagayan Converge Data Center, Inc lists no facilities in PeeringDB.