ixreport

OCX

AS2915 · OCX

BBIX, Inc.

4Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
2Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If OCX has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126Not on its website members list
    IPv4101.203.90.38
    IPv62001:de8:c::2915:1
    Speed200000 Mbps (200G)
    IPv4101.203.90.39
    IPv62001:de8:c::2915:2
    Speed200000 Mbps (200G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

Exchanges over time

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

Map

Where OCX'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 1.2T across 4 exchanges.

Philippines BBIX Manila Manila, Philippines 61.245.0.24
61.245.0.25
2001:ded:4000::2915:1
2001:ded:4000::2915:2
2 × 200G PeeringDB
Japan BBIX Osaka Osaka, Japan 218.100.9.171
218.100.9.172
2001:de8:c:2::2915:1
2001:de8:c:2::2915:2
2 × 200G Yes PeeringDB
Singapore BBIX Singapore Singapore, Singapore 103.231.152.74
103.231.152.75
2001:df5:b800:bb00::2915:1
2001:df5:b800:bb00::2915:2
2 × 10G PeeringDB
Japan BBIX Tokyo Tokyo, Japan 101.203.90.38
101.203.90.39
2001:de8:c::2915:1
2001:de8:c::2915:2
2 × 200G Yes PeeringDB only

Exchanges in its buildings that it isn't on (8)

These exchanges have a switch in a facility where OCX lists itself in PeeringDB, but don't have OCX as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (2)

The buildings OCX lists in PeeringDB, and how many of the exchanges in each it's on.

Japan NTT DATA Otemachi BldgTokyo 1 of 6
Japan NTT DATA Dojima (building #4)Osaka 1 of 4