Metro Lightspeed: PeeringDB fix list
AS142631 · peeringdb.com/net/29061
4 things to fix in Metro Lightspeed's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Metro Lightspeed'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 Metro Lightspeed's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.16.103.77 IPv6 2001:de8:12:100::103:77 Speed 1000 Mbps (1G) RS peer Yes
Correct these entries (3)
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.
-
Problem PeeringDB has The export has Port speed differs 2 × 1G 2 × 10G - In the entry with IPv4 103.162.254.50: set Speed to 10000 (10G) (now 1000).
- In the entry with IPv4 103.162.254.73: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 9G + 2G 2 × 10G - In the entry with IPv4 103.119.234.34: set Speed to 10000 (10G) (now 2000).
- In the entry with IPv4 103.119.234.43: set Speed to 10000 (10G) (now 9000).
-
Problem PeeringDB has The export has Port speed differs 8G 10G - In the entry with IPv4 103.10.57.2: set Speed to 10000 (10G) (now 8000).
From ixreport.com/net/142631/: 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.