ixreport

ReadyIDC

AS56309 · ReadyIDC

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

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

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

PeeringDB fix list Printable page · CSV

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

Make the changes on ReadyIDC'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 ReadyIDC's PeeringDB record. Add one entry per connection with these values.

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From 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

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
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, 20263
Oct 22, 20263
Oct 21, 20263
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

In the last 30 days ReadyIDC joined 1 exchange and left 0. Growing networks

Joined

Map

Where ReadyIDC'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 400G, at the 4 of 5 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Thailand BBIX Thailand Bangkok, Thailand 103.127.88.68 2001:df7:6500:1:0:5:6309:1 100G Yes PeeringDB
Japan BBIX Tokyo Tokyo, Japan Not in PeeringDB
Thailand BKNIX (Thailand) Bangkok, Thailand 203.159.68.144 2001:df5:b881::144 100G Yes Both
Singapore Equinix Singapore Singapore, Singapore 27.111.231.117 2001:de8:4::5:6309:1 100G Yes PeeringDB
Thailand THAILAND IX (TH-IX) Bangkok, Thailand 61.19.60.192 2001:c38:8000::5:6309:1 100G Yes Both

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

These exchanges have a switch in a facility where ReadyIDC lists itself in PeeringDB, but don't have ReadyIDC 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 (6)

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

Thailand Telehouse – BangkokBangkok 3 of 10
Singapore Equinix SG3 - SingaporeSingapore 1 of 7
Thailand NT Bangrak TowerBangkok 2 of 4
Thailand JasTel Data Center (Thailand)Nonthaburi 0 of 1
Thailand ReadyIDC DC1Pakkret No exchange
Thailand ReadyIDC Edge DC2 - SrisamanPakkret No exchange

Recent changes Search them

  • Oct 24, 2026 [PDB] AS56309 ReadyIDC added to Equinix Singapore