Vogel Telecom
AS25933 · Algar Telecom
Vogel Soluções em Telecom e Informática S/A
Tools: Where can I peer with Vogel Telecom? · Where should Vogel Telecom peer next? · Compare Vogel Telecom with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in Vogel Telecom's PeeringDB record, from what its exchanges publish: 7 to add, 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on Vogel Telecom'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 (7)
On the exchange's own member list, but not in Vogel Telecom's PeeringDB record. Add one entry per connection with these values.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil · PeeringDB 177From 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.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Vogel Telecom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.41.108.53 IPv6 2001:504:40:108::1:53 Speed 100000 Mbps (100G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 10 |
| Nov 18, 2026 | 10 |
| Nov 17, 2026 | 10 |
| Nov 16, 2026 | 10 |
| Nov 15, 2026 | 10 |
| Nov 14, 2026 | 10 |
| Nov 13, 2026 | 10 |
| Nov 12, 2026 | 10 |
| Nov 11, 2026 | 10 |
| Nov 10, 2026 | 10 |
| Nov 9, 2026 | 10 |
| Nov 8, 2026 | 10 |
| Nov 7, 2026 | 10 |
| Nov 6, 2026 | 10 |
| Nov 5, 2026 | 10 |
| Nov 4, 2026 | 10 |
| Nov 3, 2026 | 10 |
| Nov 2, 2026 | 10 |
| Nov 1, 2026 | 10 |
| Oct 31, 2026 | 10 |
| Oct 30, 2026 | 10 |
| Oct 29, 2026 | 10 |
| Oct 28, 2026 | 10 |
| Oct 27, 2026 | 10 |
| Oct 26, 2026 | 10 |
| Oct 25, 2026 | 10 |
| Oct 24, 2026 | 10 |
| Oct 23, 2026 | 10 |
| Oct 22, 2026 | 10 |
| Oct 21, 2026 | 10 |
| Oct 20, 2026 | 10 |
| Oct 19, 2026 | 10 |
| Oct 18, 2026 | 10 |
| Oct 17, 2026 | 10 |
| Oct 16, 2026 | 10 |
| Oct 15, 2026 | 10 |
| Oct 14, 2026 | 10 |
| Oct 13, 2026 | 10 |
| Oct 12, 2026 | 10 |
| Oct 11, 2026 | 10 |
| Oct 10, 2026 | 10 |
| Oct 9, 2026 | 10 |
| Oct 8, 2026 | 10 |
| Oct 7, 2026 | 10 |
| Oct 6, 2026 | 10 |
| Oct 5, 2026 | 10 |
| Oct 4, 2026 | 10 |
| Oct 3, 2026 | 10 |
Map
Where Vogel Telecom'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 | 100G | PeeringDB only | |
| IX.br (PTT.br) Belo Horizonte Belo Horizonte/MG, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) Curitiba Curitiba, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) Florianópolis Florianópolis/SC, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) Goiânia Goiânia/GO, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) Lajeado Lajeado/RS, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil | 40G | Both | |
| IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) Salvador Salvador/BA, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 2 × 100G + 20G | Both |
These exchanges have a switch in a facility where Vogel Telecom lists itself in PeeringDB, but don't have Vogel Telecom 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.
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| Equinix AshburnAshburn, United States | 347 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| NetIXSofia, Bulgaria | 204 | |
| Equinix MiamiMiami, United States | 175 | |
| Equinix São PauloSão Paulo, Brazil | 163 | |
| NVIXAshburn, United States | 78 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| DE-CIX Sao PauloSao Paulo, Brazil | 58 | |
| LINX NoVAAshburn, Reston, Manassas, United States | 57 | |
| MegaIX AshburnAshburn, United States | 49 | |
| CIX-NoVAAshburn, Reston, Washington DC, United States | 34 | |
| JumboIX PeruLima, Peru | 27 | |
| DACS-IX EastWashington DC, United States | 15 | |
| 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 | |
| ixFabricGlobal, Australia | 2 |
Facilities (9)
The buildings Vogel Telecom lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix DC1-DC15,DC21-DC22 - AshburnAshburn | 0 of 9 | |
| Equinix MI1 - Miami, NOTAMiami | 1 of 9 | |
| Equinix SP4 - São PauloBarueri | 1 of 6 | |
| Equinix SP1 - São PauloSão Paulo | 1 of 4 | |
| Equinix SP2 - São PauloBarueri | 1 of 4 | |
| euNetworks AmsterdamAmsterdam | 0 of 3 | |
| Cirion Sao Paulo - SAO1Cotia | 1 of 2 | |
| Eletronet - Sao PauloSão Paulo | 1 of 2 | |
| TIVIT Sao PauloSão Paulo | 1 of 2 |