MDSTELECOM
AS269832 · MDSTELECOM
MDS TELECOM C.A.
Tools: Where can I peer with MDSTELECOM? · Where should MDSTELECOM peer next? · Compare MDSTELECOM with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
One thing to fix in MDSTELECOM's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.
Make the changes on MDSTELECOM's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 45.68.88.2 45.68.88.2 45.68.88.26 IPv6 address missing from PeeringDB 2801:18d::2 2801:18d::2 2801:18d::26 - In the entry with IPv4 45.68.88.2: set IPv6 to (empty) (now 2801:18d::2).
- Add an entry: IPv4 –, IPv6 2801:18d::2, speed 100000 (100G), RS peer yes.
- Add an entry: IPv4 45.68.88.26, IPv6 –, speed 100000 (100G), RS peer yes.
- Add an entry: IPv4 –, IPv6 2801:18d::26, speed 100000 (100G), RS peer yes.
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 2 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
Map
Where MDSTELECOM'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.
| FL-IX Miami, United States | 2 × 100G | Both | |
| NAPVE CCS Caracas, Venezuela | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB |
These exchanges have a switch in a facility where MDSTELECOM lists itself in PeeringDB, but don't have MDSTELECOM 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.
| NetIXSofia, Bulgaria | 204 | |
| Equinix MiamiMiami, United States | 175 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX MiamiMiami, United States | 10 | |
| Global Peer ExchangeWashington, United States | 6 | |
| PIT - LATAM InterconnectMiami, United States | 5 | |
| GNM-IX USNew York, United States | 4 | |
| Any2FloridaMiami/Orlando, United States | 2 |
Facilities (3)
The buildings MDSTELECOM lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix MI1 - Miami, NOTAMiami | 1 of 9 | |
| Cirion La UrbinaLa Urbina | 1 of 1 | |
| Daycohost - CaracasCaracas | No exchange |