Network

Connectivity from 1 to 20 Gbps

Network for high-bandwidth dedicated servers: 1, 2.5, 5, 10 and 20 Gbps uplinks, DDoS filtering, dual-stack IPv4 and IPv6 addressing, BGP sessions and out-of-band management.

Uplink options

1 Gbps

Port speed

2.5 Gbps

Port speed

5 Gbps

Port speed

10 Gbps

Port speed

20 Gbps

Port speed

Addressing

  • IPv4 addresses assigned per service, additional space on request.
  • IPv6 enabled by default with a routed prefix per service.
  • Reverse DNS and BGP sessions available on request.

DDoS protection

  • Volumetric attack filtering in front of dedicated servers and colocated racks.
  • Always-on detection; mitigation profiles can be tuned per service.
  • Attack events and mitigation windows are visible to support on request.

Network reach

Every location where our announced address space is registered, drawn from the same configuration as the home page map.

United KingdomPolandBelgiumGermanyRomaniaUnited StatesSouth AfricaTurkey

Live location status

Location overview

Countries where the IPv4 prefixes announced by AS208949 are registered.

11 announced prefixes

Belgium

1 prefix · 256 IPv4

  • 45.148.145.0/24

Germany

1 prefix · 256 IPv4

  • 45.154.228.0/24

Poland

2 prefixes · 512 IPv4

  • 45.88.0.0/24
  • 45.148.146.0/24

Romania

1 prefix · 256 IPv4

  • 93.113.203.0/24

Russia

1 prefix · 256 IPv4

  • 193.151.109.0/24

South Africa

1 prefix · 256 IPv4

  • 102.165.51.0/24

Turkey

1 prefix · 256 IPv4

  • 195.211.191.0/24

United Kingdom

1 prefix · 512 IPv4

  • 185.114.146.0/23

United States

2 prefixes · 512 IPv4

  • 102.129.200.0/24
  • 192.101.68.0/24

Registry information only. Live latency and availability measurements are not published — see the status page for the current service state.

Our network

AS208949HBING LIMITED

We operate our own autonomous system registered with the RIPE NCC. Address space is announced by us and signed with RPKI, so routes can be validated independently.

View public registry record
Autonomous system
AS208949
Registry
RIPE NCC
Allocated
2023-04-11
IPv4 addresses
3,072
Announced prefixes
11
RPKI
Signed & valid

Announced IPv4 prefixes

  • 185.114.146.0/23512 IPs
  • 45.88.0.0/24256 IPs
  • 45.148.145.0/24256 IPs
  • 45.148.146.0/24256 IPs
  • 45.154.228.0/24256 IPs
  • 93.113.203.0/24256 IPs
  • 102.129.200.0/24256 IPs
  • 102.165.51.0/24256 IPs
  • 192.101.68.0/24256 IPs
  • 193.151.109.0/24256 IPs
  • 195.211.191.0/24256 IPs

BGP router panel

Run your own routing on AS208949

Bring your own autonomous system and address space and announce it from your server or rack over an eBGP session with our border routers — or let us announce space from our own pool while you are still applying for yours.

eBGP session on your port

A full eBGP session over IPv4 and IPv6 from your dedicated server or colocated rack to our border routers, on the same port as your normal traffic.

Announce your own prefixes

Bring your own address space and announce it through our autonomous system. Both a full transit view and a default-only session are available.

Communities and filtering

BGP communities for prepending, selective announcement and blackholing. Prefix filters are built from your route objects, so nothing leaves that is not registered.

RPKI validation

We validate announcements against RPKI. Publish a ROA for each prefix and origin ASN so other networks can verify your routes as valid.

Session monitoring

Session state, accepted prefix counts and prefix-limit warnings are visible to support, so a flapping or over-limit session is caught quickly.

Redundant sessions

A second session to a separate border router is available so a single router maintenance window does not drop your announcements.

Becoming your own ISP

How to get your own ASN and IP space

Numbers are issued by a Regional Internet Registry, not by a hosting provider. In Europe and the Middle East that is the RIPE NCC; elsewhere it is ARIN, APNIC, AFRINIC or LACNIC. The path is the same in each region.

  1. 1

    Become an RIR member (LIR)

    Address space and AS numbers are issued by a Regional Internet Registry — RIPE NCC in Europe, and ARIN, APNIC, AFRINIC or LACNIC elsewhere. You join as a Local Internet Registry, which is a registered legal entity paying an annual membership fee.

  2. 2

    Request an AS number

    An ASN is issued when you can show you will multihome — that is, peer with two or more networks — or otherwise need a distinct routing policy. The request names the networks you intend to peer with.

  3. 3

    Obtain IP address space

    IPv4 is exhausted, so new members receive a small allocation from the waiting list or lease or buy space on the transfer market. IPv6 is allocated freely and should be requested at the same time.

  4. 4

    Register objects in the routing registry

    Create aut-num, route and route6 objects in the RIPE database (or another IRR) and keep an as-set of anything you announce for others. Upstreams build their filters from these objects.

  5. 5

    Sign your routes with RPKI

    Publish a ROA for every prefix, naming the origin ASN and maximum prefix length. Networks that drop RPKI-invalid routes will otherwise not accept your announcements.

  6. 6

    Peer with us and announce

    Send us your ASN, the prefixes to be announced, your IRR objects and a technical contact. We configure the session, apply the filters and you announce from your own router.

What we need to turn up a session

  • Your AS number and the RIR that issued it
  • The exact IPv4 and IPv6 prefixes you will announce
  • Matching route / route6 objects in an IRR
  • A valid ROA for each prefix and origin ASN
  • A 24/7 technical and abuse contact
  • A prefix limit agreed for the session

Please note

We do not sell AS numbers or address space and we cannot register them on your behalf. Membership of a Regional Internet Registry is a direct relationship between you and the registry. If you do not have your own numbers yet, we can announce space from our own pool instead.

Contact us about BGP

Tell us your AS number, the prefixes you want to announce and a technical contact, and we will confirm what we need to turn up the session. If you do not have your own numbers yet, we can talk through the options. Write to sales@hbing.uk or open a request on our support page.

Contact us

Facilities

  • GB-1HBING — United Kingdom

Upstream carriers, internet exchange participation and facility certifications are not published. Contact sales@hbing.uk if you need these details for a procurement review.

These uplinks serve our dedicated servers and colocation racks. See the full list of platform features.