ixreport

VECTRA

AS29314

VECTRA S.A.

6Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
4Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in VECTRA's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on VECTRA'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.

  1. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G200G

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

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

Map

Where VECTRA'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 1.3T across 6 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.213.90 2001:7f8:1::a502:9314:3 100G 396 routes Both
Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.40.120 2001:7f8:5b::120 100G Yes Both
Poland Equinix Warsaw Warsaw, Poland 195.182.219.10 2001:7f8:42::a502:9314:3 200G Yes PeeringDB
Poland POZIX Poznan, Poland 185.1.4.104 2001:7f8:4b::104 200G PeeringDB
Poland THINX Warsaw Warsaw, Poland 212.91.0.112
212.91.0.113
2 × 200G Both Speed differs
Poland TPIX PL Warsaw, Poland 195.149.232.38
195.149.233.130
195.149.233.182
2001:7f8:27::2:9314:1
2001:7f8:27::2:9314:2
2001:7f8:27::2:9314:3
3 × 100G Yes Both

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

These exchanges have a switch in a facility where VECTRA lists itself in PeeringDB, but don't have VECTRA 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.

Netherlands GNM-IXAmsterdam, Netherlands 741 LIM Warsaw
Poland EPIX.WarszawaWarsaw, Poland 483 LIM Warsaw
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 LIM Warsaw
Ukraine Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 268 LIM Warsaw
Bulgaria NetIXSofia, Bulgaria 204 LIM Warsaw
Ukraine RUDAKI-IXKiev, Ukraine 53 LIM Warsaw
Poland Giganet IXN WarsawWarsaw, Poland 49 LIM Warsaw
Poland 1-PL FREEWarsaw, Wroclaw, Katowice, Poland 32 LIM Warsaw
Facilities (1)

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

Poland LIM WarsawWarsaw 3 of 11