ixreport

JianyueLab Global Backbone: PeeringDB fix list

AS215172 · peeringdb.com/net/35815

PeeringDB

2 things to fix in JianyueLab Global Backbone's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.

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

  1. United Kingdom Kent Internet Exchange Point Kent, United Kingdom · PeeringDB 4316From its IX-F export
    IPv4185.0.24.228
    IPv62001:7f8:aa::228
    Speed10000 Mbps (10G)
    RS peerYes

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

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. Taiwan STUIX Taipei City, Taiwan · PeeringDB 3352
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 103.158.187.182: set Speed to 10000 (10G) (now 1000).

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

From ixreport.com/net/215172/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.