ixreport

IPACCT

AS31287 · АЙ ПИ АКТ ООД

IPACCT Ltd.

12Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
11Using the route servers
3To fix in PeeringDB
9Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

3 things to fix in IPACCT's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on IPACCT'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 (1)

On the exchange's own member list, but not in IPACCT's PeeringDB record. Add one entry per connection with these values.

  1. Greece GR-IX::Athens Athens, Greece · PeeringDB 347From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (2)

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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

    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.

  2. Greece GR-IX::Thessaloniki Thessaloniki, Greece · PeeringDB 2386
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 1G1G

    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

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

Map

Where IPACCT'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 592G, at the 9 of 12 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Bulgaria 1-BG FREE Sofia, Bulgaria 195.60.91.211 2001:7f8:173::211 40G Yes PeeringDB
Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 185.0.43.125
185.0.43.126
2001:7f8:115:1::1:125
2001:7f8:115:1::1:126
4 × 40G Yes Both
Romania Balcan-IX Bucharest, Romania 80.97.248.73
80.97.248.84
2a02:d10:80::23
2a02:d10:80::26
2 × 10G Yes PeeringDB
Bulgaria BIX.BG Sofia, Bulgaria 193.169.198.140
193.169.198.141
2001:7f8:58::7a37:0:1
2001:7f8:58::7a37:0:2
2 × 100G Yes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.195.76 2001:7f8::7a37:0:1 100G 458 routes Both
Netherlands GNM-IX Amsterdam, Netherlands 178.18.237.27
178.18.237.28
2a03:5f80:4:2::237:27
2a03:5f80:4:2::237:28
2 × 10G Yes Both Speed differs
Greece GR-IX::Athens Athens, Greece Website list only
Greece GR-IX::Thessaloniki Thessaloniki, Greece 185.1.123.16
185.1.123.17
2001:7f8:ce::16
2001:7f8:ce::17
2 × 1G Yes Both Speed differs
Bulgaria NetIX Sofia, Bulgaria 185.1.226.154
185.1.227.154
2001:67c:29f0::3:1287:1
2001:67c:29f0::3:1287:2
Yes Both
Greece NetIX Greece Thessaloniki / Athens, Greece 185.0.28.30 2001:7f8:148::3:1287:1 Yes PeeringDB
Serbia SOX Serbia Belgrade/Serbia, Serbia 185.1.27.26
185.1.27.29
2001:7f8:1e::26
2001:7f8:1e::29
2 × 20G Yes PeeringDB
Bulgaria VarnaIX Varna, Bulgaria 185.1.137.151 2001:7f8:db::3:1287:1 10G Yes PeeringDB

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

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

Facilities (9)

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

Bulgaria TELEPOINT Sofia CentreSofia 7 of 17
Bulgaria Equinix SO1 - SofiaSofia 4 of 7
Bulgaria Equinix SO2 - SofiaSofia 4 of 5
Bulgaria Sofia Data Center (SDC)Sofia 3 of 5
Bulgaria TELEPOINT Sofia EastSofia 2 of 4
Bulgaria S3 Company Ltd.Sofia 1 of 3
Bulgaria Evolink Data Center Sofia 1Sofia 1 of 1
Bulgaria Evolink Data Center Sofia 2Sofia 1 of 1
Bulgaria BTC Core Network SofiaSofia No exchange

Recent changes Search them

  • Oct 15, 2026 [PDB] AS31287 IPACCT now in PeeringDB at 1-IX EU