ixreport

EPIC_TELECOM

AS206101 · Epic Telecom

EPIC SOLUTIONS, S.L.

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

Tools: Where can I peer with EPIC_TELECOM? · Where should EPIC_TELECOM peer next? · Compare EPIC_TELECOM 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 EPIC_TELECOM's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on EPIC_TELECOM'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. Spain DE-CIX Barcelona Barcelona, Spain · PeeringDB 3446
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:10a:0:3:2515:0:1
    • In the entry with IPv4 185.1.119.5: set IPv6 to 2001:7f8:10a:0:3:2515:0:1 (now empty).

Exchanges over time

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

Map

Where EPIC_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.

Exchanges

Total port capacity 1G across 1 exchange.

Spain DE-CIX Barcelona Barcelona, Spain 185.1.119.5 1G 4 routes Both IPv6 not in PeeringDB

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

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

Spain CATNIXBarcelona, Spain 55 Templus DC Barcelona BCN01
Spain ixFabric - BarcelonaBarcelona, Spain 52 Templus DC Barcelona BCN01
Spain Barcelona-IXBarcelona, Spain 47 Templus DC Barcelona BCN01
United States Global Peer ExchangeWashington, United States 6 Templus DC Barcelona BCN01
Facilities (1)

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

Spain Templus DC Barcelona BCN01L'Hospitalet de Llobregat 1 of 5

Recent changes Search them

  • Oct 16, 2026 [PDB] AS206101 EPIC_TELECOM now in PeeringDB at DE-CIX Barcelona