Wofbit Networks
AS207113 · WofBIT
Tools: Where can I peer with Wofbit Networks? · Where should Wofbit Networks peer next? · Compare Wofbit Networks with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in Wofbit Networks's PeeringDB record, from what its exchanges publish: 4 to add, 2 to correct, 2 to check. As of 2026-11-19 12:40 UTC.
Make the changes on Wofbit Networks'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 (4)
On the exchange's own member list, but not in Wofbit Networks's PeeringDB record. Add one entry per connection with these values.
-
IPv4 – IPv6 2001:7f8:ca:1:0:20:7113:1 Speed 1000 Mbps (1G) 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.
-
IPv4 149.112.29.127 IPv6 2001:504:125:e0::127 Speed Not published RS peer Not published -
IPv4 149.112.60.44 IPv6 2001:504:125:e2::44 Speed Not published RS peer Not published -
IPv4 149.112.50.124 IPv6 2001:504:125:e1::124 Speed 1000 Mbps (1G) 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 (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.
-
Problem PeeringDB has The export has Port speed differs 10G 40G - In the entry with IPv4 178.18.236.160: set Speed to 40000 (40G) (now 10000).
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 10G 1G - In the entry with IPv4 196.60.8.120: set Speed to 1000 (1G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If Wofbit Networks has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.66.228.80 IPv6 2001:7f8:4::3:2909:1 Speed 4000 Mbps (4G) -
IPv4 195.66.236.173 IPv6 2001:7f8:4:1:0:3:2909:1 Speed 4000 Mbps (4G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 15 |
| Nov 18, 2026 | 15 |
| Nov 17, 2026 | 15 |
| Nov 16, 2026 | 14 |
| Nov 15, 2026 | 14 |
| Nov 14, 2026 | 14 |
| Nov 13, 2026 | 14 |
| Nov 12, 2026 | 15 |
| Nov 11, 2026 | 15 |
| Nov 10, 2026 | 15 |
| Nov 9, 2026 | 15 |
| Nov 8, 2026 | 15 |
| Nov 7, 2026 | 15 |
| Nov 6, 2026 | 15 |
| Nov 5, 2026 | 15 |
| Nov 4, 2026 | 15 |
| Nov 3, 2026 | 15 |
| Nov 2, 2026 | 15 |
| Nov 1, 2026 | 15 |
| Oct 31, 2026 | 15 |
| Oct 30, 2026 | 15 |
| Oct 29, 2026 | 15 |
| Oct 28, 2026 | 15 |
| Oct 27, 2026 | 15 |
| Oct 26, 2026 | 15 |
| Oct 25, 2026 | 13 |
| Oct 24, 2026 | 12 |
| Oct 23, 2026 | 12 |
| Oct 22, 2026 | 14 |
| Oct 21, 2026 | 14 |
| Oct 20, 2026 | 15 |
| Oct 19, 2026 | 15 |
| Oct 18, 2026 | 15 |
| Oct 17, 2026 | 15 |
| Oct 16, 2026 | 15 |
| Oct 15, 2026 | 15 |
| Oct 14, 2026 | 15 |
| Oct 13, 2026 | 15 |
| Oct 12, 2026 | 15 |
| Oct 11, 2026 | 15 |
| Oct 10, 2026 | 15 |
| Oct 9, 2026 | 15 |
| Oct 8, 2026 | 15 |
| Oct 7, 2026 | 15 |
| Oct 6, 2026 | 15 |
| Oct 5, 2026 | 15 |
| Oct 4, 2026 | 15 |
| Oct 3, 2026 | 15 |
Map
Where Wofbit Networks'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.
| AMS-IX Amsterdam, Netherlands | 1G | Both | |
| ERA-IX Amsterdam Amsterdam, Netherlands | 10G | Both | |
| FogIXP Avers, Switzerland | 1G | Not in PeeringDB | |
| FREMIX Fremont, United States | Not in PeeringDB | ||
| Frys-IX Fryslân, Netherlands | 10G | Both | |
| GNM-IX Amsterdam, Netherlands | 10G | Both Speed differs | |
| LINX LON1 London, United Kingdom | 4G | PeeringDB only | |
| LINX LON2 London, United Kingdom | 4G | PeeringDB only | |
| LINX Mombasa Mombasa, Kenya | 4G | Both | |
| LINX Nairobi Nairobi, Kenya | 4G | Both | |
| LONAP London, United Kingdom | 1G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 10G | Both Speed differs | |
| NVIX Ashburn, United States | Not in PeeringDB | ||
| ONIX Toronto, Canada | 1G | Not in PeeringDB | |
| Speed-IX Dronten, Netherlands | 10G | Both |
These exchanges have a switch in a facility where Wofbit Networks lists itself in PeeringDB, but don't have Wofbit Networks 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.
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| INTERIXAmsterdam, Netherlands | 262 | |
| EVIXFremont, United States | 227 | |
| NetIXSofia, Bulgaria | 204 | |
| FCIXFremont, United States | 187 | |
| KIXP - NairobiNairobi, Kenya | 182 | |
| ixFabric - AmsterdamAmsterdam, Netherlands | 181 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 105 | |
| Kent Internet Exchange PointKent, United Kingdom | 102 | |
| SFMIXSan Francisco, United States | 100 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 57 | |
| PyramIXCairo, Egypt | 48 | |
| Giganet IXN AmsterdamAmsterdam, Netherlands | 47 | |
| KIXP-MombasaMombasa, Kenya | 41 | |
| Clue-IXAmsterdam, Netherlands | 36 | |
| PR-IXSan Juan, Puerto Rico | 33 | |
| Balcan-IXBucharest, Romania | 29 | |
| Asteroid AmsterdamAmsterdam, Netherlands | 27 | |
| ARIXFremont, Portland, Flagstaff, United States | 22 | |
| Lambda-IXFremont, United States | 22 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| RegPEXAnkara, Türkiye | 19 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| DACS-IX WestSilicon Valley, United States | 14 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| Ninja-IX Bay AreaNorthern California, United States | 6 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| Noord-IXLeeuwarden, Netherlands | 4 | |
| ixFabricGlobal, Australia | 2 |
Facilities (8)
The buildings Wofbit Networks lists in PeeringDB, and how many of the exchanges in each it's on.
| NIKHEF AmsterdamAmsterdam | 6 of 28 | |
| Hurricane Electric Fremont 2Fremont | 1 of 12 | |
| Telehouse - London (Docklands North)London | 4 of 11 | |
| Digital Realty AMS17 - AmsterdamAmsterdam | 4 of 8 | |
| Africa Data Centres, Nairobi NBO1, KenyaNairobi | 1 of 2 | |
| icolo.io Mombasa One (MBA1)Miritini | 1 of 2 | |
| icolo.io Nairobi One (NBO1)Karen | 1 of 2 | |
| Teraco Johannesburg Bredell CampusJohannesburg | 0 of 1 |
Recent changes Search them
- Nov 18, 2026 [WEB] AS207113 Wofbit Networks dropped from NAPAfrica IX Johannesburg's website list (still in PeeringDB and on its IX-F list)
- Oct 31, 2026 [WEB] AS207113 Wofbit Networks dropped from LINX LON1's website list (still in PeeringDB)
- Oct 31, 2026 [WEB] AS207113 Wofbit Networks dropped from LINX LON2's website list (still in PeeringDB)
- Oct 31, 2026 [IXF] AS207113 Wofbit Networks dropped from LINX LON1's IX-F list (still in PeeringDB and on its website's members list)
- Oct 31, 2026 [IXF] AS207113 Wofbit Networks dropped from LINX LON2's IX-F list (still in PeeringDB and on its website's members list)