ixreport

AT&T AP: PeeringDB fix list

AS2687 · peeringdb.com/net/671

2 things to fix in AT&T AP's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

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

  1. India DE-CIX Chennai Chennai, India · PeeringDB 2588From its IX-F export
    IPv4103.228.174.109
    IPv62400:d180:68::109
    Speed10000 Mbps (10G)
    RS peerYes

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. ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 218.100.52.90: set Speed to 100000 (100G) (now 10000).

    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/2687/: 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.