ixreport

TELEVERGENCE

AS30188 · Televergence Solutions Inc

2Exchanges
1On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
1Using the route servers
2To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with TELEVERGENCE? · Where should TELEVERGENCE peer next? · Compare TELEVERGENCE with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in TELEVERGENCE's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-11-19 12:40 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.

Exchanges over time

012Oct 3, 2026Nov 19, 20262
Show as a table
DateExchanges
Nov 19, 20262
Nov 18, 20262
Nov 17, 20262
Nov 16, 20262
Nov 15, 20262
Nov 14, 20262
Nov 13, 20262
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20262
Nov 8, 20262
Nov 7, 20262
Nov 6, 20262
Nov 5, 20262
Nov 4, 20262
Nov 3, 20262
Nov 2, 20262
Nov 1, 20262
Oct 31, 20262
Oct 30, 20262
Oct 29, 20262
Oct 28, 20262
Oct 27, 20262
Oct 26, 20262
Oct 25, 20262
Oct 24, 20262
Oct 23, 20262
Oct 22, 20262
Oct 21, 20262
Oct 20, 20262
Oct 19, 20262
Oct 18, 20262
Oct 17, 20262
Oct 16, 20262
Oct 15, 20262
Oct 14, 20262
Oct 13, 20262
Oct 12, 20262
Oct 11, 20262
Oct 10, 20262
Oct 9, 20262
Oct 8, 20262
Oct 7, 20262
Oct 6, 20262
Oct 5, 20262
Oct 4, 20262
Oct 3, 20262

Map

Where TELEVERGENCE's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 1G, at the 1 of 2 exchanges with a speed in PeeringDB or the exchange's IX-F export.

United States Any2West Los Angeles and Silicon Valley, United States 206.72.210.203 1G Yes PeeringDB
United States MegaIX Los Angeles Los Angeles, United States 206.53.172.31 2606:a980:0:5::1f Not in PeeringDB

Exchanges in its buildings that it isn't on (3)

These exchanges have a switch in a facility where TELEVERGENCE lists itself in PeeringDB, but don't have TELEVERGENCE as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

United States BBIX US-WestWest Coast, United States 87 CoreSite - Los Angeles (LA1) One Wilshire
Peru JumboIX PeruLima, Peru 27 CoreSite - Los Angeles (LA1) One Wilshire
United States NYIIX Los AngelesLos Angeles, United States 21 CoreSite - Los Angeles (LA1) One Wilshire
Facilities (1)

The buildings TELEVERGENCE lists in PeeringDB, and how many of the exchanges in each it's on.

United States CoreSite - Los Angeles (LA1) One WilshireLos Angeles 2 of 5