CreeperHost
AS201971
CreeperHost® LTD
Tools: Where can I peer with CreeperHost? · Where should CreeperHost peer next? · Compare CreeperHost 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 CreeperHost's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 18:41 UTC.
Make the changes on CreeperHost's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If CreeperHost 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.227.30 IPv6 2001:7f8:4::3:14f3:1 Speed 1000 Mbps (1G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 1 |
| Nov 18, 2026 | 1 |
| Nov 17, 2026 | 1 |
| Nov 16, 2026 | 1 |
| Nov 15, 2026 | 1 |
| Nov 14, 2026 | 1 |
| Nov 13, 2026 | 1 |
| Nov 12, 2026 | 1 |
| Nov 11, 2026 | 1 |
| Nov 10, 2026 | 1 |
| Nov 9, 2026 | 1 |
| Nov 8, 2026 | 1 |
| Nov 7, 2026 | 1 |
| Nov 6, 2026 | 1 |
| Nov 5, 2026 | 1 |
| Nov 4, 2026 | 1 |
| Nov 3, 2026 | 1 |
| Nov 2, 2026 | 1 |
| Nov 1, 2026 | 1 |
| Oct 31, 2026 | 1 |
| Oct 30, 2026 | 1 |
| Oct 29, 2026 | 1 |
| Oct 28, 2026 | 1 |
| Oct 27, 2026 | 1 |
| Oct 26, 2026 | 1 |
| Oct 25, 2026 | 1 |
| Oct 24, 2026 | 1 |
| Oct 23, 2026 | 1 |
| Oct 22, 2026 | 1 |
| Oct 21, 2026 | 1 |
| Oct 20, 2026 | 1 |
| Oct 19, 2026 | 1 |
| Oct 18, 2026 | 1 |
| Oct 17, 2026 | 1 |
| Oct 16, 2026 | 1 |
| Oct 15, 2026 | 1 |
| Oct 14, 2026 | 1 |
| Oct 13, 2026 | 1 |
| Oct 12, 2026 | 1 |
| Oct 11, 2026 | 1 |
| Oct 10, 2026 | 1 |
| Oct 9, 2026 | 1 |
| Oct 8, 2026 | 1 |
| Oct 7, 2026 | 1 |
| Oct 6, 2026 | 1 |
| Oct 5, 2026 | 1 |
| Oct 4, 2026 | 1 |
| Oct 3, 2026 | 1 |
Map
Where CreeperHost'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.
| LINX LON1 London, United Kingdom | 1G | PeeringDB only |
These exchanges have a switch in a facility where CreeperHost lists itself in PeeringDB, but don't have CreeperHost 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.
| GNM-IXAmsterdam, Netherlands | 741 | |
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| LINX LON2London, United Kingdom | 315 | |
| LONAPLondon, United Kingdom | 311 | |
| Any2WestLos Angeles and Silicon Valley, United States | 284 | |
| IX Australia Sydney (NSW-IX)Sydney, Australia | 270 | |
| MegaIX SydneySydney, Australia | 267 | |
| EdgeIX - SydneySydney, Australia | 230 | |
| NetIXSofia, Bulgaria | 204 | |
| DE-CIX DallasDallas, United States | 177 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| Kent Internet Exchange PointKent, United Kingdom | 102 | |
| MegaIX DallasDallas, United States | 30 | |
| Balcan-IXBucharest, Romania | 29 | |
| MegaIX Los AngelesLos Angeles, United States | 27 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (8)
The buildings CreeperHost lists in PeeringDB, and how many of the exchanges in each it's on.
| Telehouse - London (Docklands North)London | 1 of 11 | |
| DigiCo Sydney SYD1 (formerly Global Switch Australia)Sydney | 0 of 4 | |
| CoreSite - Los Angeles (LA2)Los Angeles | 0 of 3 | |
| Cologix DAL2Dallas | 0 of 2 | |
| Latitude.sh MH1São Paulo | 0 of 1 | |
| ColoCrossing BUF1Buffalo | No exchange | |
| ColoCrossing SEA1Seattle | No exchange | |
| iomart DC3 NottinghamNottingham | No exchange |