Securebit AG
AS58057 · Securebit, SB, SBAG
Securebit
Tools: Where can I peer with Securebit AG? · Where should Securebit AG peer next? · Compare Securebit AG with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
7 things to fix in Securebit AG's PeeringDB record, from what its exchanges publish: 1 to add, 6 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Securebit AG'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 Securebit AG's PeeringDB record. Add one entry per connection with these values.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list
IPv4 193.239.118.8 IPv6 2001:7f8:13::a505:8057:1 Speed Not published RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (6)
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 in PeeringDB, not in the export 185.1.170.175 185.1.170.176 185.1.170.175 IPv6 address in PeeringDB, not in the export 2001:7f8:9e::e2c9:0:1 2001:7f8:9e::e2c9:0:2 2001:7f8:9e::e2c9:0:1 Port speed differs 2 × 1G 10G - In the entry with IPv4 185.1.170.175: set Speed to 10000 (10G) (now 1000).
- The entry with IPv4 185.1.170.176, IPv6 2001:7f8:9e::e2c9:0:2 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 80.81.195.219: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 185.1.210.185 185.1.210.223 185.1.210.223 IPv6 address in PeeringDB, not in the export 2001:7f8:3d::e2c9:0:1 2001:7f8:3d::e2c9:0:2 2001:7f8:3d::e2c9:0:2 Port speed differs 2 × 1G 10G - The entry with IPv4 185.1.210.185, IPv6 2001:7f8:3d::e2c9:0:1 isn't in the export: delete it if that connection is gone.
- In the entry with IPv4 185.1.210.223: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 185.1.208.180 185.1.208.191 185.1.208.180 IPv6 address in PeeringDB, not in the export 2001:7f8:44::e2c9:0:1 2001:7f8:44::e2c9:0:2 2001:7f8:44::e2c9:0:2 Port speed differs 2 × 1G 10G - In the entry with IPv4 185.1.208.180: set Speed to 10000 (10G) (now 1000).
- The entry with IPv4 185.1.208.191, IPv6 2001:7f8:44::e2c9:0:1 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has Port speed differs 2G + 1G 2 × 1G - In the entry with IPv4 206.81.104.242: set Speed to 1000 (1G) (now 2000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 1G 100M - In the entry with IPv4 193.189.82.71: set Speed to 100 (100M) (now 1000).
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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 16 |
| Nov 18, 2026 | 16 |
| Nov 17, 2026 | 16 |
| Nov 16, 2026 | 16 |
| Nov 15, 2026 | 16 |
| Nov 14, 2026 | 16 |
| Nov 13, 2026 | 16 |
| Nov 12, 2026 | 16 |
| Nov 11, 2026 | 16 |
| Nov 10, 2026 | 16 |
| Nov 9, 2026 | 16 |
| Nov 8, 2026 | 16 |
| Nov 7, 2026 | 16 |
| Nov 6, 2026 | 16 |
| Nov 5, 2026 | 16 |
| Nov 4, 2026 | 16 |
| Nov 3, 2026 | 16 |
| Nov 2, 2026 | 16 |
| Nov 1, 2026 | 16 |
| Oct 31, 2026 | 16 |
| Oct 30, 2026 | 16 |
| Oct 29, 2026 | 16 |
| Oct 28, 2026 | 16 |
| Oct 27, 2026 | 16 |
| Oct 26, 2026 | 16 |
| Oct 25, 2026 | 16 |
| Oct 24, 2026 | 16 |
| Oct 23, 2026 | 16 |
| Oct 22, 2026 | 16 |
| Oct 21, 2026 | 16 |
| Oct 20, 2026 | 16 |
| Oct 19, 2026 | 16 |
| Oct 18, 2026 | 16 |
| Oct 17, 2026 | 16 |
| Oct 16, 2026 | 16 |
| Oct 15, 2026 | 16 |
| Oct 14, 2026 | 16 |
| Oct 13, 2026 | 16 |
| Oct 12, 2026 | 16 |
| Oct 11, 2026 | 16 |
| Oct 10, 2026 | 16 |
| Oct 9, 2026 | 16 |
| Oct 8, 2026 | 16 |
| Oct 7, 2026 | 16 |
| Oct 6, 2026 | 16 |
| Oct 5, 2026 | 16 |
| Oct 4, 2026 | 16 |
| Oct 3, 2026 | 16 |
Map
Where Securebit AG'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.
| 4b42 Internet Exchange Point Zurich, Switzerland | 2 × 10G | Both | |
| DE-CIX Dusseldorf Düsseldorf, Germany | 2 × 1G | Both IPv4 not in exportIPv6 not in exportSpeed differs | |
| DE-CIX Frankfurt Frankfurt, Germany | 1G | Both Speed differs | |
| DE-CIX Hamburg Hamburg, Germany | 2 × 1G | Both IPv4 not in exportIPv6 not in exportSpeed differs | |
| DE-CIX Munich Munich, Germany | 2 × 1G | Both IPv4 not in exportIPv6 not in exportSpeed differs | |
| EVIXVIX Fremont, United States | 2G + 1G | Both Speed differs | |
| FCIX Fremont, United States | 10G | Both | |
| KleyReX Frankfurt, Germany | 1G | Both Speed differs | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | Not in PeeringDB | ||
| SBIX Amsterdam Amsterdam, Netherlands | 10G | PeeringDB | |
| SBIX Dusseldorf Dusseldorf, Germany | 2 × 10G | PeeringDB | |
| SBIX FRE Fremont / Neuheim, United States | 10G | PeeringDB | |
| SBIX Zurich Lupfig, Switzerland | 2 × 10G | PeeringDB | |
| Speed-IX Dronten, Netherlands | 10G | Both | |
| SwissIX Zurich, Switzerland | 1G | Both | |
| UNM-Exch Canada-West Vancouver, Canada | 1G | Both |
These exchanges have a switch in a facility where Securebit AG lists itself in PeeringDB, but don't have Securebit AG 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.
| AMS-IXAmsterdam, Netherlands | 920 | |
| GNM-IXAmsterdam, Netherlands | 741 | |
| FogIXPAvers, Switzerland | 532 | |
| DE-CIX MumbaiMumbai, India | 454 | |
| Frys-IXFryslân, Netherlands | 338 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| DE-CIX New YorkNew York, United States | 281 | |
| SGIXSingapore, Singapore | 277 | |
| IX Australia Sydney (NSW-IX)Sydney, Australia | 270 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| MegaIX SydneySydney, Australia | 267 | |
| INTERIXAmsterdam, Netherlands | 262 | |
| Extreme IX MumbaiMumbai, India | 246 | |
| ERA-IX AmsterdamAmsterdam, Netherlands | 244 | |
| EdgeIX - SydneySydney, Australia | 230 | |
| Equinix SydneySydney, Australia | 219 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| LOCIX DUSSELDORFDusseldorf, Germany | 204 | |
| NetIXSofia, Bulgaria | 204 | |
| ixFabric - AmsterdamAmsterdam, Netherlands | 181 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| FREMIXFremont, United States | 141 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| Equinix TokyoTokyo, Japan | 127 | |
| LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 105 | |
| SFMIXSan Francisco, United States | 100 | |
| MegaIX DusseldorfDusseldorf, Germany | 97 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| CHIX-CHFrauenfeld, Switzerland | 66 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 57 | |
| TYIXTokyo, Japan | 53 | |
| PyramIXCairo, Egypt | 48 | |
| Giganet IXN AmsterdamAmsterdam, Netherlands | 47 | |
| LOCIX NETHERLANDSMeppel, Netherlands | 46 | |
| MegaIX SingaporeSingapore, Singapore | 46 | |
| PIT MXQueretaro, Mexico | 46 | |
| Clue-IXAmsterdam, Netherlands | 36 | |
| PR-IXSan Juan, Puerto Rico | 33 | |
| Asteroid AmsterdamAmsterdam, Netherlands | 27 | |
| ARIXFremont, Portland, Flagstaff, United States | 22 | |
| Lambda-IXFremont, United States | 22 | |
| MegaIX New YorkNew York, United States | 22 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| RegPEXAnkara, Türkiye | 19 | |
| NDIXEnschede / Münster, Netherlands | 15 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| DACS-IX WestSilicon Valley, United States | 14 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| Equinix SeoulSeoul, South Korea | 9 | |
| FogIXP ZurichZurich, Switzerland | 9 | |
| Equinix MexicoMexico City, Mexico | 8 | |
| Exchange7Winterthur, Switzerland | 8 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| Ninja-IX Bay AreaNorthern California, United States | 6 | |
| STACIXFrankfurt, Germany | 5 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| Noord-IXLeeuwarden, Netherlands | 4 | |
| ixFabricGlobal, Australia | 2 |
Facilities (16)
The buildings Securebit AG lists in PeeringDB, and how many of the exchanges in each it's on.
| NIKHEF AmsterdamAmsterdam | 2 of 28 | |
| Hurricane Electric Fremont 2Fremont | 2 of 12 | |
| Digital Realty Zurich ZUR1Glattbrugg | 1 of 6 | |
| Equinix SY3 - SydneySydney | 0 of 6 | |
| firstcolo - FRA4Frankfurt | 1 of 6 | |
| WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7Düsseldorf | 2 of 6 | |
| Equinix TY8 - TokyoTokyo | 0 of 4 | |
| Green Datacenter ZRH1 (fka: Green Lupfig)Lupfig | 3 of 4 | |
| KoloDC NL1Dronten | 1 of 4 | |
| QTS Piscataway (PNJ1)Piscataway | 0 of 3 | |
| Equinix MX1/MX2 - Mexico CityEl Marques | 0 of 2 | |
| Equinix SL1 - SeoulSeoul | 0 of 2 | |
| Racks CentralSingapore | 0 of 2 | |
| YOTTA NM1Panvel, Raigad, | 0 of 2 | |
| VoltaLondon | 0 of 1 | |
| Gigahost SandefjordSandefjord | No exchange |