Taipan Transit Articles

Noez alternative for GRE tunnels and routed IPv4

Repeated complete outages are a good reason to replace a GRE tunnel provider. A game server disconnects its players, a public VM disappears, and the operator spends time chasing an endpoint that should simply carry traffic. If that is why you are searching for a Noez alternative, Taipan Transit offers routed public IPv4 over GRE, WireGuard, or IPsec for the servers you already run.

Noez's public status history records repeated GRE infrastructure interruptions. This comparison examines those incidents, the available history, and the practical reasons to choose Taipan: three tunnel protocols, public IPv4 delivery to existing servers, and filtering before traffic reaches the customer tunnel.

A Noez address and a new Taipan address reach the same gateway and VM through separate tunnels.
Migration example with documentation addresses. The VM stays on the same hardware while a second tunnel provides a new public IPv4. Move DNS and clients only after testing that new path.

Noez GRE interruptions on consecutive days

The public Noez history lists GRE/FlexIP incidents on September 13, 14, and 15, 2026. Three selected entries lasted 15, 26, and 17 minutes respectively, based on their published start and end times.

Three published GRE incidents: September 13 lasted 15 minutes, September 14 lasted 26 minutes, and September 15 lasted 17 minutes.
Selected public incidents, September 2026. September 13 and 15 affected Node 1; September 14 affected Nodes 1 and 2. These durations describe the listed events, not every customer's downtime.

For a public-facing service, interruptions on successive days are a reason to evaluate another route. Game sessions can disconnect, remote access can fail, and hosted applications can become unreachable. A low monthly IP price does little to offset repeated disruption for users who depend on the service.

Evaluate the endpoint carrying your traffic and the behavior of your application. The relevant outcome is whether users can connect and stay connected during the hours they need it.

What the public Noez status history actually shows

On September 16, 2026, the Noez status page displayed 99.86% for GRE/FlexIP. Of its 90 daily bars, 28 had no percentage: June 19 through July 16.

Ninety daily status cells: 28 gray cells have no percentage and 62 blue cells contain a percentage.
Public HTML observed September 16, 2026. Gray means no percentage was displayed; blue means a value was present, including days with incidents. This chart measures history coverage, not uptime.

That leaves part of the displayed history unavailable for review. The headline percentage alone cannot explain what happened on those dates.

The dated extracted daily values preserve the observation. An aggregate infrastructure percentage cannot, on its own, establish availability for a particular customer's tunnel. That needs endpoint and application measurements covering the same period.

What Taipan Transit offers as a Noez alternative

Taipan Transit routes public IPv4 addresses through a tunnel to existing infrastructure. The same server can keep its applications, storage, and VMs while its public access moves to a new route. The customer handles local routing and firewall rules.

  • GRE for a compatible public endpoint. Keep a familiar Linux routing model when the uplink permits GRE.
  • WireGuard for NAT or changing endpoint addresses. Its outbound tunnel is useful for home labs and connections where a fixed public endpoint is unavailable. The dynamic-IP reference explains Taipan's supported setup.
  • IPsec for deployments that need it. Choose an encrypted tunnel compatible with the intended equipment.
  • Filtering before delivery. Taipan's DDoS protection operates upstream of the customer tunnel. Local firewall policy, uplink capacity, and application security still matter.

Taipan is a practical replacement when you want to keep your servers while changing their public network access. Start with one address and the tunnel protocol that fits the connection, then expand after validating the route with your applications.

Noez and Taipan: compare the actual entry costs

The following advertised rates were checked on September 16, 2026. The Noez column describes its GRE/FlexIP offer; the Taipan column uses the current tunnel campaign.

ItemNoez GRE/FlexIPTaipan Transit
Monthly tunnel fee€2.00€2.00 during the campaign
Monthly IPv4 charge€0.50 per address€0.70 per address
Tunnel plus one IPv4€2.50 advertised€2.70 from the displayed components
Included traffic1 TB per IPv41 TB per tunnel
Tunnel choices in the compared offersGREGRE, WireGuard, IPsec
Documented GRE endpoint requirementPublic IP, Linux, and an uplink that permits GRECheck requirements; WireGuard offers another delivery option for NAT

Noez has the lower advertised address charge. The displayed one-IP entry amounts differ by €0.20 monthly before reconciling checkout tax treatment, traffic, and discounts. Noez states that its prices include statutory VAT; confirm the final amount for your billing country on both checkouts. Taipan's campaign can change. Multiple IPs also change the included-traffic comparison.

A small difference in the entry fee makes a parallel evaluation practical. For someone experiencing repeated interruptions, the useful question is whether the replacement route keeps their service reachable under their actual workload.

Ready to evaluate a replacement for your Noez tunnel? Start with one Taipan IPv4, connect your existing server, and test a service before moving production traffic.

Set up a Taipan tunnelCheck current pricing

Migrate from Noez without moving the server

  1. Inventory the old public addresses. List DNS records, game connection addresses, partner allowlists, PTR records, and software with hardcoded IPs. A normal migration uses new Taipan-assigned IPv4 addresses; do not assume rented Noez addresses transfer.
  2. Create a separate tunnel. Choose GRE, WireGuard, or IPsec and follow the Taipan setup guide. Keep the existing route available while testing. Use distinct interface names and routing tables where appropriate.
  3. Move one test service. Route one new address to its host or VM. Permit the intended port and verify that replies sourced from that address return through the Taipan tunnel. The Proxmox guide covers guest routing.
  4. Measure from outside. Test from the networks your users actually use, including busy periods. Record timestamps, application failures, latency, jitter, and packet loss. Check MTU and MSS when small packets work but transfers stall.
  5. Switch clients and retain a rollback path. Reduce DNS TTL ahead of the change where possible, update records and allowlists, and notify users who connect by IP. Keep both services during the transition; end the old service after validating the new path.

For a game server, include real sessions in that evaluation. A successful ping cannot show whether players complete a connection, stay connected, and avoid stalls during play. For web services, include an application request and verify its response, not only an open TCP port.

Frequently asked questions

Is Taipan Transit an alternative to Noez FlexIP?

Yes. Taipan Transit delivers public IPv4 addresses through GRE, IPsec, or WireGuard tunnels to existing infrastructure. A Noez customer can configure a separate Taipan tunnel, test a service on a new address, and then migrate DNS and clients.

Does Noez publish GRE outages?

Yes. The public history reviewed on September 16, 2026 lists GRE/FlexIP incidents on consecutive days. The selected September 13, 14, and 15 entries lasted 15, 26, and 17 minutes respectively and affected specified nodes.

Can I use WireGuard instead of GRE with Taipan?

Yes. Taipan offers WireGuard as well as GRE and IPsec. WireGuard can initiate outbound from a network behind NAT when outbound UDP is allowed, making it useful when a public GRE endpoint is unavailable.

Can I keep my Noez-assigned IPv4 when switching to Taipan?

Do not assume that an address rented from Noez can transfer. A normal migration uses newly assigned Taipan addresses and updates DNS, allowlists, reverse DNS, and clients with hardcoded IPs. Separately owned address space requires a specific routing agreement.

How should I test an alternative for a game server?

Test real game sessions from the networks your players use. Compare application reachability, latency, jitter, and packet loss over time, including busy periods, before moving the production service.

Sources and comparison date