S3 Company
AS4849 · S3C
S3 Company Ltd.
Tools: Where can I peer with S3 Company? · Where should S3 Company peer next? · Compare S3 Company 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 S3 Company's PeeringDB record, from what its exchanges publish: 5 to correct, 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on S3 Company'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 (5)
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.169.198.191 193.169.198.191 193.169.199.101 IPv6 address missing from PeeringDB 2001:7f8:58::12f1:0:2 2001:7f8:58::12f1:0:1 2001:7f8:58::12f1:0:2 - In the entry with IPv4 193.169.198.191: set IPv6 to 2001:7f8:58::12f1:0:1 (now 2001:7f8:58::12f1:0:2).
- Add an entry: IPv4 193.169.199.101, IPv6 2001:7f8:58::12f1:0:2.
-
Problem PeeringDB has The export has Port speed differs 3 × 100G + 2 × 10G 3 × 100G + 10G 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.
-
Problem PeeringDB has The export has Port speed differs 2 × 10G 10G 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.
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 195.66.228.119: set Speed to 10000 (10G) (now 100000).
-
Problem PeeringDB has The export has IPv6 address differs 2001:7f8:8f::a504:4901:1 2001:7f8:8f::a500:4849:1 Port speed differs 100G 10G - In the entry with IPv4 185.1.32.117: set IPv6 to 2001:7f8:8f::a500:4849:1 (now 2001:7f8:8f::a504:4901:1); set Speed to 10000 (10G) (now 100000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If S3 Company has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 193.188.137.109 IPv6 – Speed 10000 Mbps (10G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 20 |
| Nov 18, 2026 | 20 |
| Nov 17, 2026 | 20 |
| Nov 16, 2026 | 20 |
| Nov 15, 2026 | 20 |
| Nov 14, 2026 | 20 |
| Nov 13, 2026 | 20 |
| Nov 12, 2026 | 20 |
| Nov 11, 2026 | 20 |
| Nov 10, 2026 | 20 |
| Nov 9, 2026 | 20 |
| Nov 8, 2026 | 19 |
| Nov 7, 2026 | 19 |
| Nov 6, 2026 | 19 |
| Nov 5, 2026 | 19 |
| Nov 4, 2026 | 19 |
| Nov 3, 2026 | 19 |
| Nov 2, 2026 | 19 |
| Nov 1, 2026 | 19 |
| Oct 31, 2026 | 19 |
| Oct 30, 2026 | 19 |
| Oct 29, 2026 | 19 |
| Oct 28, 2026 | 19 |
| Oct 27, 2026 | 19 |
| Oct 26, 2026 | 19 |
| Oct 25, 2026 | 19 |
| Oct 24, 2026 | 19 |
| Oct 23, 2026 | 19 |
| Oct 22, 2026 | 19 |
| Oct 21, 2026 | 19 |
| Oct 20, 2026 | 19 |
| Oct 19, 2026 | 19 |
| Oct 18, 2026 | 19 |
| Oct 17, 2026 | 19 |
| Oct 16, 2026 | 19 |
| Oct 15, 2026 | 19 |
| Oct 14, 2026 | 19 |
| Oct 13, 2026 | 19 |
| Oct 12, 2026 | 19 |
| Oct 11, 2026 | 19 |
| Oct 10, 2026 | 19 |
| Oct 9, 2026 | 19 |
| Oct 8, 2026 | 19 |
| Oct 7, 2026 | 19 |
| Oct 6, 2026 | 19 |
| Oct 5, 2026 | 19 |
| Oct 4, 2026 | 19 |
| Oct 3, 2026 | 19 |
In the last 30 days S3 Company joined 1 exchange and left 0. Growing networks
Joined
- InterLAN-IX Bucharest Nov 9, 2026
Map
Where S3 Company'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.
| BIX Budapest, Hungary | 10G | PeeringDB only | |
| BIX.BG Sofia, Bulgaria | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| Equinix Frankfurt Frankfurt, Germany | 10G | PeeringDB | |
| Frys-IX Fryslân, Netherlands | 100G | Both | |
| Giganet IXN Amsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 10G | PeeringDB | |
| Giganet IXN Frankfurt Frankfurt, Germany | 10G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 3 × 100G + 2 × 10G | Both Speed differs | |
| GNM-IX UA Kiev, Ukraine | 2 × 10G | PeeringDB | |
| GR-IX::Thessaloniki Thessaloniki, Greece | 1G | Both | |
| INTERIX Amsterdam, Netherlands | 100G | Both | |
| InterLAN-IX Bucharest, Romania | 2 × 10G | Both Speed differs | |
| LINX LON1 London, United Kingdom | 100G | Both Speed differs | |
| LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 100G | Both IPv6 differsSpeed differs | |
| nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 100G | Both | |
| PITER-IX Frankfurt Frankfurt, Germany | 10G | PeeringDB | |
| RegPEX Ankara, Türkiye | 10G | Both | |
| SIX.SK Bratislava, Slovakia | 10G | Both | |
| Speed-IX Dronten, Netherlands | 10G | Both | |
| TurkIX Sofia Sofia, Bulgaria | 100G | Both | |
| VarnaIX Varna, Bulgaria | 10G | PeeringDB |
These exchanges have a switch in a facility where S3 Company lists itself in PeeringDB, but don't have S3 Company 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.
| DE-CIX FrankfurtFrankfurt, Germany | 1,075 | |
| AMS-IXAmsterdam, Netherlands | 920 | |
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| FogIXPAvers, Switzerland | 532 | |
| TPIX PLWarsaw, Poland | 480 | |
| KleyReXFrankfurt, Germany | 471 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| ERA-IX AmsterdamAmsterdam, Netherlands | 244 | |
| NIX.CZPrague, Czechia | 225 | |
| Peering.czPrague, Bratislava, Vienna, Frankfurt, Czechia | 207 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| NetIXSofia, Bulgaria | 204 | |
| THINX WarsawWarsaw, Poland | 194 | |
| ixFabric - AmsterdamAmsterdam, Netherlands | 181 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| B-IXSofia, Bulgaria | 77 | |
| BALT-IXVilnius, Lithuania | 77 | |
| DE-CIX IstanbulIstanbul, Türkiye | 72 | |
| NIX.SKBratislava, Slovakia | 68 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 57 | |
| 91-IXFrankfurt, Germany | 53 | |
| Equinix AmsterdamAmsterdam, Netherlands | 51 | |
| BBIX AmsterdamAmsterdam, Netherlands | 50 | |
| PyramIXCairo, Egypt | 48 | |
| Giganet IXN AmsterdamAmsterdam, Netherlands | 47 | |
| SOX SerbiaBelgrade/Serbia, Serbia | 46 | |
| RoNIXBucharest, Romania | 43 | |
| Clue-IXAmsterdam, Netherlands | 36 | |
| Balcan-IXBucharest, Romania | 29 | |
| GIBIRIXİstanbul, Türkiye | 28 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| Asteroid AmsterdamAmsterdam, Netherlands | 27 | |
| 1-BG FREESofia, Bulgaria | 22 | |
| MegaIX SofiaSofia, Bulgaria | 20 | |
| NL-ix 2Amsterdam, Netherlands | 19 | |
| DSIXBucharest, Romania | 18 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| NVL-IXAthens, Greece | 14 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| T-CIXSofia, Bulgaria | 9 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| Noord-IXLeeuwarden, Netherlands | 4 |
Facilities (22)
The buildings S3 Company lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix FR5 - Frankfurt, KleyerStrasseFrankfurt | 8 of 33 | |
| NIKHEF AmsterdamAmsterdam | 8 of 28 | |
| TELEPOINT Sofia CentreSofia | 5 of 17 | |
| Digital Realty AMS9 - AmsterdamAmsterdam | 3 of 12 | |
| Equinix FR7 - Frankfurt, GutleutstrasseFrankfurt | 2 of 12 | |
| Equinix AM3 - Amsterdam, Science ParkAmsterdam | 3 of 10 | |
| Equinix FR4 - Frankfurt, WestFrankfurt | 2 of 9 | |
| Equinix FR6 - Frankfurt, WestFrankfurt | 2 of 9 | |
| Digital Realty AMS17 - AmsterdamAmsterdam | 2 of 8 | |
| NXDATA-1 Bucharest (BUH1)Bucharest | 2 of 8 | |
| Equinix SO1 - SofiaSofia | 2 of 7 | |
| Equinix FR8 - Frankfurt, WestFrankfurt | 2 of 6 | |
| NXDATA-2 Bucharest (BUH2)Bucharest | 1 of 6 | |
| Sofia Data Center (SDC)Sofia | 1 of 5 | |
| maincubes AMS01Schiphol Rijk | 1 of 4 | |
| PremierDC Veri Merkezi A.S. - IstanbulIstanbul | 0 of 3 | |
| S3 Company Ltd.Sofia | 3 of 3 | |
| Slovak University of TechnologyBratislava | 1 of 2 | |
| BIX Building (Victor Hugo street)Budapest | 1 of 1 | |
| Synapsecom SNC-1 ThessalonikiThessaloniki | 1 of 1 | |
| Varna Teleport CenterVarna | 0 of 1 | |
| Daticum DatacenterSofia | No exchange |
Recent changes Search them
- Nov 10, 2026 [PDB] AS4849 S3 Company now in PeeringDB at InterLAN-IX
- Nov 10, 2026 [PDB] AS4849 S3 Company no longer in PeeringDB at InterLAN-IX (still on its IX-F list)
- Nov 9, 2026 [IXF] AS4849 S3 Company now on InterLAN-IX's IX-F list
- Nov 9, 2026 [PDB] AS4849 S3 Company added to InterLAN-IX