ixreport

KCV Communications

AS55376

10Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
9Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with KCV Communications? · Where should KCV Communications peer next? · Compare KCV Communications with another network

This network elsewhere: the registry history of AS55372-AS55396, the block AS55376 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in KCV Communications's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on KCV Communications's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in KCV Communications's PeeringDB record. Add one entry per connection with these values.

  1. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

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

Map

Where KCV Communications'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 51.2G, at the 9 of 10 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands BBIX Amsterdam Amsterdam, Netherlands 101.203.78.53 2403:c780:7200:b078:0:5:5376:1 300M Yes PeeringDB
Japan BBIX Fukuoka Fukuoka, Japan 101.203.104.30 2001:de8:c:4:0:5:5376:1 10G Yes PeeringDB
Hong Kong BBIX Hong Kong Hong Kong, Hong Kong 103.203.158.54 2403:c780:b800:bb00:0:5:5376:1 300M Yes PeeringDB
Japan BBIX Osaka Osaka, Japan 218.100.9.207 2001:de8:c:2:0:5:5376:2 10G Yes PeeringDB
Singapore BBIX Singapore Singapore, Singapore 103.231.152.54 2001:df5:b800:bb00:0:5:5376:1 300M Yes PeeringDB
Japan BBIX Tokyo Tokyo, Japan 101.203.89.52 2001:de8:c::5:5376:1 10G Yes Both
United States BBIX US-West West Coast, United States 101.203.74.39 2403:c780:7200:b074:0:5:5376:1 300M Yes PeeringDB
Japan JPIX FUKUOKA Fukuoka, Japan 103.177.65.43 2001:de8:8:9:0:5:5376:1 10G Yes PeeringDB
Japan JPIX OSAKA Osaka, Japan 103.246.232.89 2001:de8:8:6:0:5:5376:1 10G Yes PeeringDB
Japan JPIX TOKYO Tokyo, Japan Not in PeeringDB

KCV Communications lists no facilities in PeeringDB.