ixreport

Hostrebel, Inc.

AS211665 · Hostrebel, Inc.

3Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Network ServicesType
SelectivePeering policy
3Using the route servers
3To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Hostrebel, Inc.? · Where should Hostrebel, Inc. peer next? · Compare Hostrebel, Inc. 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 Hostrebel, Inc.'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 Hostrebel, Inc.'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 Hostrebel, Inc.'s PeeringDB record. Add one entry per connection with these values.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::3:3ad1:1
    SpeedNot published
    RS peerYes

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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G4G + 1G
    • In the entry with IPv4 195.66.228.125: set Speed to 4000 (4G) (now 10000).
    • In the entry with IPv4 195.66.228.128: set Speed to 1000 (1G) (now 10000).
  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB5.57.82.2245.57.82.224 5.57.82.225
    IPv6 address missing from PeeringDB2001:7f8:17::3:3ad1:12001:7f8:17::3:3ad1:1 2001:7f8:17::3:3ad1:2
    Port speed differs10G5G + 1G
    • In the entry with IPv4 5.57.82.224: set Speed to 1000 (1G) (now 10000).
    • Add an entry: IPv4 5.57.82.225, IPv6 2001:7f8:17::3:3ad1:2, speed 5000 (5G), 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.

Exchanges over time

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

Map

Where Hostrebel, Inc.'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 30G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:3ad1:1 Yes Not in PeeringDB
United Kingdom LINX LON1 London, United Kingdom 195.66.228.125
195.66.228.128
2001:7f8:4::3:3ad1:1
2001:7f8:4::3:3ad1:2
2 × 10G Up, 0 routes Both Speed differs
United Kingdom LONAP London, United Kingdom 5.57.82.224 2001:7f8:17::3:3ad1:1 10G Up, 0 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs

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

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

Netherlands GNM-IXAmsterdam, Netherlands 741 Telehouse - London (Docklands North)
Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Telehouse - London (Docklands North)
United Kingdom LINX LON2London, United Kingdom 315 Telehouse - London (Docklands North); Digital Realty London LHR19
Bulgaria NetIXSofia, Bulgaria 204 Telehouse - London (Docklands North); Digital Realty London LHR19
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands North)
United Kingdom Kent Internet Exchange PointKent, United Kingdom 102 Telehouse - London (Docklands North)
Romania Balcan-IXBucharest, Romania 29 Telehouse - London (Docklands North)
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 Telehouse - London (Docklands North)
United States Global Peer ExchangeWashington, United States 6 Telehouse - London (Docklands North)
Facilities (2)

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

United Kingdom Telehouse - London (Docklands North)London 2 of 11
United Kingdom Digital Realty London LHR19London 2 of 4