Telecom Italia Sparkle: PeeringDB fix list

AS6762 · peeringdb.com/net/31

PeeringDB

6 things to fix in Telecom Italia Sparkle's PeeringDB record, from what its exchanges publish: 6 to add. As of 2026-10-08 20:58 UTC.

Make the changes on Telecom Italia Sparkle'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 (6)

On the exchange's own member list, but not in Telecom Italia Sparkle'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. Bulgaria B-IX Sofia, Bulgaria · PeeringDB 326From 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.

  3. Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil · PeeringDB 710From 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.

  4. Brazil IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil · PeeringDB 177From 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.

  5. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From 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.

  6. Italy Namex Rome Rome, Italy · PeeringDB 121From 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.

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