ixreport

TELEVERGENCE: PeeringDB fix list

AS30188 · peeringdb.com/net/13787

PeeringDB

2 things to fix in TELEVERGENCE's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 18:53 UTC.

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

  1. United States MegaIX Los Angeles Los Angeles, United States · PeeringDB 1175From its IX-F export
    IPv4206.53.172.31
    IPv62606:a980:0:5::1f
    SpeedNot published
    RS peerNo

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If TELEVERGENCE has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United States Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142Not on its website members list
    IPv4206.72.210.203
    IPv6–
    Speed1000 Mbps (1G)

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

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