ixreport

MVTELECOM

AS266269 · MV TELECOM

MV TELECOM

8Exchanges
6On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
2Using the route servers
6To fix in PeeringDB
0Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

6 things to fix in MVTELECOM's PeeringDB record, from what its exchanges publish: 6 to add. As of 2026-11-19 18:41 UTC.

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

  1. Brazil IX.br (PTT.br) Brasília Brasília/DF, Brazil · PeeringDB 178From 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.

  2. Brazil IX.br (PTT.br) Curitiba Curitiba, Brazil · PeeringDB 174From 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.

  3. Brazil IX.br (PTT.br) Florianópolis Florianópolis/SC, Brazil · PeeringDB 175From 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.

  4. Brazil IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil · PeeringDB 173From 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.

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

Exchanges over time

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

Map

Where MVTELECOM'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 60G, at the 2 of 8 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Brazil IX.br (PTT.br) Brasília Brasília/DF, Brazil Not in PeeringDB
Brazil IX.br (PTT.br) Curitiba Curitiba, Brazil Not in PeeringDB
Brazil IX.br (PTT.br) Florianópolis Florianópolis/SC, Brazil Not in PeeringDB
Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil 45.68.73.130 2001:12f8:0:9::145:130 20G 35 routes Both
Brazil IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil Not in PeeringDB
Brazil IX.br (PTT.br) Recife Recife/PE, Brazil 200.219.147.42 2001:12f8:0:10::42 40G 33 routes Both
Brazil IX.br (PTT.br) Salvador Salvador/BA, Brazil Down Not in PeeringDB
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil Not in PeeringDB

MVTELECOM lists no facilities in PeeringDB.