ixreport

Epsilon: PeeringDB fix list

AS44356 · peeringdb.com/net/6852

PeeringDB

7 things to fix in Epsilon's PeeringDB record, from what its exchanges publish: 3 to add, 3 to correct, 1 to check. As of 2026-10-08 21:56 UTC.

Make the changes on Epsilon'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 (3)

On the exchange's own member list, but not in Epsilon's PeeringDB record. Add one entry per connection with these values.

  1. United States Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142From 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.

  2. United States DE-CIX New York New York, United States · PeeringDB 804From its IX-F export and website members list
    IPv4206.82.104.157
    IPv62001:504:36::ad44:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  3. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699From its IX-F export and website members list

    The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G10G + 50M
  2. United States MASS-IX Boston, United States · PeeringDB 1086
    ProblemPeeringDB hasThe export has
    Port speed differs500M1G
    • In the entry with IPv4 206.53.143.49: set Speed to 1000 (1G) (now 500).
  3. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs10G2G
    • In the entry with IPv4 103.16.102.66: set Speed to 2000 (2G) (now 10000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Epsilon 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.224.115
    IPv62001:de8:8::4:4356:1
    Speed100 Mbps (100M)

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

From ixreport.com/net/44356/: 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.