AWS-CLOUD: PeeringDB fix list

AS12345

5 things to fix in AWS-CLOUD's PeeringDB record, from what its exchanges publish: 5 to add. As of 2026-10-08 18:53 UTC.

AS12345 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (5)

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

DE-CIX Bengaluru Bengaluru, India · PeeringDB 5045From its IX-F export

The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
DE-CIX Chennai Chennai, India · PeeringDB 2588From its IX-F export

The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
DE-CIX Delhi Delhi, India · PeeringDB 2587From its IX-F export

The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
DE-CIX Hyderabad Hyderabad, India · PeeringDB 4263From its IX-F export

The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
DE-CIX Mumbai Mumbai, India · PeeringDB 832From its IX-F export

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

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