Networks
Network Infrastructure

GRE Tunneling Solutions

Route your leased IPv4 address space through dedicated tunnels, delivered over GRE or WireGuard. Connect to any infrastructure worldwide.

Tunnel Features

Low Latency

Optimized tunnel endpoints in major data center hubs across Europe, US, and Asia for minimal latency overhead.

Global Endpoints

Choose tunnel endpoints in 20+ locations. Route your leased IPs through the nearest point of presence.

GRE or WireGuard

We support both GRE and WireGuard as tunnel delivery protocols. Choose the option that best fits your network setup and environment.

WireGuard Support

Choose between standard GRE and modern WireGuard tunnels. WireGuard works through NAT and CGNAT, making it ideal for locations without a public IP.

Custom Configuration

Tailored MTU settings, keepalive timers, and routing policies. We configure everything to your specifications.

Redundant Tunnels

Set up primary and failover tunnels for high availability. Automatic failover with sub-second convergence.

Technical Specifications

Our tunnel infrastructure is built on enterprise-grade hardware with redundant uplinks.

ProtocolGRE (RFC 2784) / WireGuard
Bandwidth250 Mbit/s
MTUConfigurable, default 1476
Uptime target99% target
DDoS ProtectionOptional
tunnel-config-example.txt
# GRE Tunnel Configuration Example
interface Tunnel0
  ip address 10.0.0.2 255.255.255.252
  tunnel source 203.0.113.1
  tunnel destination 198.51.100.1
  tunnel mode gre ip
  ip mtu 1476

# WireGuard Alternative
[Interface]
Address = 10.0.0.2/30
PrivateKey = <your-private-key>
Table = off

[Peer]
PublicKey = <rtm-public-key>
Endpoint = 198.51.100.1:51820
AllowedIPs = 0.0.0.0/0

Common Use Cases

Host Servers Without ISP IPs

Run servers from your office or on-premise location using your leased IPv4 space via a tunnel, without depending on your ISP's address allocation.

Bypass Port 25 Restrictions

Most residential and business ISPs block outbound port 25. Route your mail traffic through a tunnel to send email from your leased IPv4 addresses.

Remote Data Center Connectivity

Connect leased IPv4 blocks to your infrastructure in remote data centers without requiring direct peering or transit.

Rent Less Than a /24

A /24 is the smallest self-routable block, but you don't always need 256 IPs. Rent exactly what you need and take advantage of our low per-IP pricing, far below what hosting providers or ISPs typically charge.

What a tunnel actually does

Leased or owned IPv4 space is registered in one place, but you usually want to use it somewhere else: a server in another country, a provider that will not accept a Letter of Authorization, or infrastructure with no BGP session of its own. A tunnel bridges that gap.

We terminate the address space on our own routers and build an encapsulated point-to-point link to your endpoint. Traffic for your block arrives at our edge, travels through the tunnel, and emerges on your machine as though the addresses were configured locally. Return traffic takes the same path. Your server needs no BGP session and no relationship with a registry.

Because encapsulation adds header overhead, the usable MTU inside the tunnel is lower than on a plain interface. We supply the correct MTU and MSS clamping settings alongside the configuration, so this never surfaces as the classic symptom where small requests succeed but large transfers stall.

GRE or WireGuard

We deliver tunnels over either. Which one fits depends on what your endpoint supports and whether you need the traffic encrypted.

GRE

Lightweight encapsulation with no encryption and very little CPU cost. Supported natively by effectively every router and by the Linux kernel. The better choice when the path between us is already trusted, or when raw throughput matters more than confidentiality.

WireGuard

Modern encrypted tunnelling with a small, auditable codebase and strong performance. The better choice when traffic crosses networks you do not control, or when your endpoint sits behind NAT, where plain GRE becomes awkward.

If you are not sure, tell us what the endpoint is and we will recommend one.

Tunnelling questions

Do I need my own ASN?

No, and that is the main reason to use a tunnel. We announce the space and hand it to you over the link, so your endpoint needs nothing more than the ability to bring up a tunnel interface.

What does a tunnel do to latency?

It adds the round trip to our nearest endpoint, so siting matters more than the protocol. Pick an endpoint close to your server and the overhead is typically small. We will tell you which endpoint suits your location before you commit.

Will it work behind NAT?

WireGuard handles NAT well. Plain GRE does not traverse NAT reliably, so if your endpoint has no public address of its own, WireGuard is the option to take.

What MTU should I use?

Lower than the standard 1500, to leave room for the encapsulation headers. We supply the exact value with your configuration along with MSS clamping, which is what prevents small packets working while large transfers hang.

Can I run BGP over the tunnel?

Yes, if you have an ASN and want to manage the announcement yourself. Most customers do not need this and take the simpler static setup instead.

Can I tunnel space I bought elsewhere?

Yes. We can route address space you already hold, provided you can issue a Letter of Authorization showing you are entitled to announce it.

Related Services

Other ways we help with IPv4 address space.

Further reading

A Complete Guide to GRE Tunneling for IPv4 Routing

Learn how GRE tunnels work, when to use them, and how to configure them for routing leased or owned IPv4 address space through your infrastructure.

Need your IPv4 space routed?

Tell us where your endpoints are and whether GRE or WireGuard suits your setup. We usually reply in 1-3 business hours.

Contact Us