ixreport

ByteArk

AS59238 · Innovative Extremist

ByteArk Company Limited

8Exchanges
1On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
8Using the route servers
3To fix in PeeringDB
5Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

3 things to fix in ByteArk's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-11-19 12:40 UTC.

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

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::e766:1
    SpeedNot published
    RS peerYes

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Hong Kong AMS-IX Hong Kong Hong Kong, Hong Kong · PeeringDB 577
    ProblemPeeringDB hasThe export has
    Port speed differs200M250M
    • In the entry with IPv4 103.247.139.77: set Speed to 250 (250M) (now 200).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (1)

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

  1. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30Not on its website members list
    IPv4210.171.225.194
    IPv62001:de8:8::5:9238:1
    Speed500 Mbps (500M)

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

Exchanges over time

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

Map

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

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::e766:1 Yes Not in PeeringDB
Hong Kong AMS-IX Hong Kong Hong Kong, Hong Kong 103.247.139.77 2001:df0:296::a505:9238:1 200M 2 routes Both Speed differs
Thailand BKNIX (Thailand) Bangkok, Thailand 203.159.68.12
203.159.68.24
2001:df5:b881::12
2001:df5:b881::24
2 × 10G Yes Both
Thailand BKNIX Chiang Mai (Thailand) Chiang Mai, Thailand 203.159.67.13 2001:df5:b881:1::13 20G Yes Both
Japan JPIX TOKYO Tokyo, Japan 210.171.225.194 2001:de8:8::5:9238:1 500M Yes PeeringDB only
Germany KleyReX Frankfurt, Germany 193.189.83.74 2001:7f8:33::a105:9238:1 100M 3 routes Both
Singapore SGIX Singapore, Singapore 103.16.102.99 2001:de8:12:100::99 10G Yes Both
Thailand THAILAND IX (TH-IX) Bangkok, Thailand 61.19.60.45 2001:c38:8000::5:9238:1 10G Yes Both

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

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

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

Singapore Equinix SG1 - SingaporeSingapore 1 of 11
Thailand Telehouse – BangkokBangkok 2 of 10
Thailand CS LoxInfo Data Center - The CloudBangkok 1 of 5
Thailand NT Bangrak TowerBangkok 1 of 4
Hong Kong EdgeX by HGCTsing Yi No exchange