ixreport

Docusign: PeeringDB fix list

AS62856 · peeringdb.com/net/11884

PeeringDB

2 things to fix in Docusign's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

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

  1. United States SIX Seattle Seattle, United States · PeeringDB 13From its IX-F export and website members list
    IPv4206.81.81.243
    IPv62001:504:16::f588
    SpeedNot published
    RS peerNot published

    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. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 206.53.202.48: set Speed to 200000 (200G) (now 10000).

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