ixreport

Redge Technologies

AS57811 · Atende Software, redGalaxy CDN, redCDN, Redge Guardian, redGuardian

Redge Technologies sp. z o.o.

8Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
7Using the route servers
3To fix in PeeringDB
10Facilities in PeeringDB

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

Make the changes on Redge Technologies'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 Redge Technologies's PeeringDB record. Add one entry per connection with these values.

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From 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. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G25G
    • In the entry with IPv4 185.0.20.20: set Speed to 25000 (25G) (now 100000).
    • In the entry with IPv4 185.0.21.42: set Speed to 25000 (25G) (now 100000).
  2. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB212.91.0.40 212.91.0.41 212.91.0.132 212.91.0.192212.91.0.40 212.91.0.41 212.91.0.44 212.91.0.132 212.91.0.192
    • In the entry with IPv4 212.91.0.132: set IPv4 to (empty) (now 212.91.0.132).
    • In the entry with IPv4 212.91.0.192: set IPv4 to (empty) (now 212.91.0.192).
    • In the entry with IPv4 212.91.0.40: set IPv4 to (empty) (now 212.91.0.40).
    • In the entry with IPv4 212.91.0.41: set IPv4 to (empty) (now 212.91.0.41).
    • Add an entry: IPv4 212.91.0.40, IPv6 –, speed 400000 (400G).
    • Add an entry: IPv4 212.91.0.41, IPv6 –, speed 400000 (400G).
    • Add an entry: IPv4 212.91.0.44, IPv6 –, speed 400000 (400G).
    • Add an entry: IPv4 212.91.0.192, IPv6 –, speed 400000 (400G).
    • Add an entry: IPv4 212.91.0.132, IPv6 –, speed 400000 (400G).

    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

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

In the last 30 days Redge Technologies joined 0 exchanges and left 2. Growing networks

Left

  • 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong Nov 12, 2026
  • 1-PL FREE Warsaw, Wroclaw, Katowice Nov 3, 2026 PeeringDB only

Map

Where Redge Technologies'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.5T, at the 7 of 8 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Ukraine 1-IX UA Kyiv, Ukraine Not in PeeringDB
Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.40.31
178.216.40.242
2001:7f8:5b::242
2001:7f8:5b::538
2 × 100G Yes Both
Poland EPIX.Warszawa Warsaw, Poland 89.46.144.19
89.46.146.31
2001:678:3ac::19
2001:678:3ac::683
2 × 100G Yes Both
Poland Equinix Warsaw Warsaw, Poland 195.182.218.228 2001:7f8:42::5:7811:2 100G Yes PeeringDB
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.218.1 2001:12f8::218:1 10G Down Both
Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia 185.0.20.20
185.0.21.42
2001:7f8:7f::20
2001:7f8:7f::c:42
2 × 100G Yes Both Speed differs
Poland THINX Warsaw Warsaw, Poland 212.91.0.40
212.91.0.41
212.91.0.132
212.91.0.192
2001:7f8:60::1026:d
2001:7f8:60::8798:1
2001:7f8:60::5:7811:1
2001:7f8:60::5:7811:2
4 × 100G Yes Both IPv4 not in PeeringDB
Poland TPIX PL Warsaw, Poland 195.149.233.99
195.149.233.111
195.149.233.141
195.149.233.206
2001:7f8:27::5:7811:2
2001:7f8:27::5:7811:5
2001:7f8:27::5:7811:6
2001:7f8:27::5:7811:7
4 × 100G Yes Both

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

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

United Kingdom LINX LON1London, United Kingdom 837 Equinix LD8 - London, Docklands
Netherlands GNM-IXAmsterdam, Netherlands 741 Telehouse - Paris 2 (Voltaire - Léon Frot); Equinix ZH4 - Zurich; CE Colo Prague and 1 more
Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Equinix LD8 - London, Docklands; Telehouse - Paris 2 (Voltaire - Léon Frot)
France France-IX ParisParis, France 452 Telehouse - Paris 2 (Voltaire - Léon Frot); Digital Realty Paris PAR5; OPCORE - DC2 / PAR2 and 1 more
United Kingdom LINX LON2London, United Kingdom 315 Equinix LD8 - London, Docklands
United Kingdom LONAPLondon, United Kingdom 311 Equinix LD8 - London, Docklands
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 Equinix LD8 - London, Docklands; Telehouse - Paris 2 (Voltaire - Léon Frot); CE Colo Prague and 3 more
Ukraine Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 268 Equinix WA1 - Warsaw, Centrum LIM; ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5); ATMAN Data Center Warsaw-1 (WAW-1, Grochowska 21A)
Netherlands INTERIXAmsterdam, Netherlands 262 Telehouse - Paris 2 (Voltaire - Léon Frot)
Switzerland SwissIXZurich, Switzerland 253 Equinix ZH4 - Zurich
France Equinix ParisParis, France 239 Telehouse - Paris 2 (Voltaire - Léon Frot)
Czechia NIX.CZPrague, Czechia 225 CE Colo Prague
Bulgaria NetIXSofia, Bulgaria 204 Equinix LD8 - London, Docklands; Telehouse - Paris 2 (Voltaire - Léon Frot); Equinix ZH4 - Zurich and 2 more
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - Paris 2 (Voltaire - Léon Frot); Equinix ZH4 - Zurich; OPCORE - DC2 / PAR2 and 1 more
Netherlands Global-IXAmsterdam, Netherlands 138 Equinix ZH4 - Zurich; CE Colo Prague; Equinix WA1 - Warsaw, Centrum LIM
Switzerland CHIX-CHFrauenfeld, Switzerland 66 Equinix ZH4 - Zurich
France HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France 58 Telehouse - Paris 2 (Voltaire - Léon Frot); OPCORE - DC2 / PAR2; OPCORE - DC3 / PAR3
United Kingdom Equinix LondonLondon, United Kingdom 53 Equinix LD8 - London, Docklands
Poland Giganet IXN WarsawWarsaw, Poland 49 Equinix WA1 - Warsaw, Centrum LIM; ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5); ATMAN Data Center Warsaw-1 (WAW-1, Grochowska 21A)
Netherlands Giganet IXN AmsterdamAmsterdam, Netherlands 47 ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)
Switzerland Equinix ZurichZurich, Switzerland 40 Equinix ZH4 - Zurich
Poland 1-PL FREEWarsaw, Wroclaw, Katowice, Poland 32 Equinix WA1 - Warsaw, Centrum LIM; ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5); ATMAN Data Center Warsaw-1 (WAW-1, Grochowska 21A)
France nine - six in ParisParis, France 24 Telehouse - Paris 2 (Voltaire - Léon Frot); OPCORE - DC2 / PAR2; OPCORE - DC3 / PAR3
France SFINXParis, France 23 Telehouse - Paris 2 (Voltaire - Léon Frot)
Ukraine Giganet IXN OdesaOdessa, Ukraine 22 Equinix WA1 - Warsaw, Centrum LIM
France 1-FR FREEParis, France 14 Telehouse - Paris 2 (Voltaire - Léon Frot)
France ERA-IX ParisParis, France 14 Telehouse - Paris 2 (Voltaire - Léon Frot)
France EuroRhine-IXStrasbourg, France 14 Telehouse - Paris 2 (Voltaire - Léon Frot)
Ukraine Giganet IXN KharkіvKharkiv, Ukraine 13 Equinix WA1 - Warsaw, Centrum LIM
Czechia NIX.CZ FENIXPrague, Czechia 8 CE Colo Prague
Czechia 1-CZ FREEPrague, Czechia 6 CE Colo Prague
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 Equinix LD8 - London, Docklands; Telehouse - Paris 2 (Voltaire - Léon Frot); Equinix ZH4 - Zurich
France France-IX Paris EssentielParis, France 6 Telehouse - Paris 2 (Voltaire - Léon Frot)
United States Global Peer ExchangeWashington, United States 6 Equinix LD8 - London, Docklands; Telehouse - Paris 2 (Voltaire - Léon Frot)
Facilities (10)

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

Recent changes Search them

  • Nov 12, 2026 [WEB] AS57811 Redge Technologies left 1-IX EU
  • Nov 3, 2026 [PDB] AS57811 Redge Technologies no longer in PeeringDB at 1-IX EU (still on its website's members list)
  • Nov 3, 2026 [PDB] AS57811 Redge Technologies left 1-PL FREE