Echo Service Provider
AS327693 · Echotel Pty Ltd
Tools: Where can I peer with Echo Service Provider? · Where should Echo Service Provider peer next? · Compare Echo Service Provider with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list
Nothing to fix: Echo Service Provider's PeeringDB record matches the member lists of the 4 exchanges we could compare.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 4 |
| Nov 18, 2026 | 4 |
| Nov 17, 2026 | 4 |
| Nov 16, 2026 | 4 |
| Nov 15, 2026 | 4 |
| Nov 14, 2026 | 4 |
| Nov 13, 2026 | 4 |
| Nov 12, 2026 | 4 |
| Nov 11, 2026 | 4 |
| Nov 10, 2026 | 4 |
| Nov 9, 2026 | 4 |
| Nov 8, 2026 | 4 |
| Nov 7, 2026 | 4 |
| Nov 6, 2026 | 4 |
| Nov 5, 2026 | 4 |
| Nov 4, 2026 | 4 |
| Nov 3, 2026 | 4 |
| Nov 2, 2026 | 4 |
| Nov 1, 2026 | 4 |
| Oct 31, 2026 | 4 |
| Oct 30, 2026 | 4 |
| Oct 29, 2026 | 4 |
| Oct 28, 2026 | 4 |
| Oct 27, 2026 | 4 |
| Oct 26, 2026 | 4 |
| Oct 25, 2026 | 4 |
| Oct 24, 2026 | 4 |
| Oct 23, 2026 | 4 |
| Oct 22, 2026 | 4 |
| Oct 21, 2026 | 4 |
| Oct 20, 2026 | 4 |
| Oct 19, 2026 | 4 |
| Oct 18, 2026 | 4 |
| Oct 17, 2026 | 4 |
| Oct 16, 2026 | 4 |
| Oct 15, 2026 | 4 |
| Oct 14, 2026 | 4 |
| Oct 13, 2026 | 4 |
| Oct 12, 2026 | 4 |
| Oct 11, 2026 | 4 |
| Oct 10, 2026 | 4 |
| Oct 9, 2026 | 4 |
| Oct 8, 2026 | 4 |
| Oct 7, 2026 | 4 |
| Oct 6, 2026 | 4 |
| Oct 5, 2026 | 4 |
| Oct 4, 2026 | 4 |
| Oct 3, 2026 | 4 |
Map
Where Echo Service Provider'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.
| DINX Durban, South Africa | 100G | Both | |
| NAPAfrica IX Cape Town Cape Town, South Africa | 2 × 100G | Both | |
| NAPAfrica IX Durban Durban, South Africa | 2 × 100G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 2 × 200G | Both |
These exchanges have a switch in a facility where Echo Service Provider lists itself in PeeringDB, but don't have Echo Service Provider 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.
| JINXJohannesburg, South Africa | 215 | |
| NetIXSofia, Bulgaria | 204 | |
| CINXCape Town, South Africa | 128 | |
| NAPAfrica MAPS JohannesburgJohannesburg, South Africa | 31 | |
| Global Peer ExchangeWashington, United States | 6 | |
| JINX VoiceJohannesburg, South Africa | 4 |
Facilities (3)
The buildings Echo Service Provider lists in PeeringDB, and how many of the exchanges in each it's on.
| Teraco Johannesburg Campus, South AfricaJohannesburg | 1 of 6 | |
| Teraco CT1 Cape Town, South AfricaCape Town | 1 of 3 | |
| Teraco DB1 Durban, South AfricaDurban | 2 of 2 |