Lifestream: PeeringDB fix list
AS200976 · peeringdb.com/net/28236
2 things to fix in Lifestream's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.
Make the changes on Lifestream's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.225.53 178.18.225.31 178.18.225.53 IPv6 address missing from PeeringDB none 2a03:5f80:4::225:31 2a03:5f80:4::225:53 - In the entry with IPv4 178.18.225.53: set IPv6 to 2a03:5f80:4::225:53 (now empty).
- Add an entry: IPv4 178.18.225.31, IPv6 2a03:5f80:4::225:31, speed 200000 (200G), RS peer yes.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 185.209.89.30 IPv6 – Speed Not published
From ixreport.com/net/200976/: 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.