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.

The practical move is to bring up a replacement tunnel, test one service on its new address, and then switch clients over. This comparison covers a former Noez customer's experience, the limits of the public status history, current entry pricing, and that migration process.

Disclosure: This commercial comparison is published by Taipan Transit. The customer account below was supplied by the Taipan site operator, who reports previously using Noez. It is not an independent customer survey.

Why this former Noez customer wanted to leave

The operator reports complete service interruptions lasting hours on June 13, 17, 18, and 22, and July 2, 2026. They describe repeatedly contacting support and remaining dissatisfied with the outcome. These are the customer's reported dates; exact start times, recovery times, and total downtime have not been independently established.

In the supplied June 22 message, the customer wrote:

Again, again, again, how much will i need to open ticket for down endpoint ? why your statut still saying 100% uptime gre when it cut multiple everyday ?

This is the customer's complaint, including their description of the status at the time. The original ticket interface and a contemporaneous status screenshot were not available for this article. The message does not establish a measured daily outage rate.

The supplied support response points to attack-related overload

The operator also supplied a reply attributed to Noez support:

some of the problems seem to come from overload due to certain attacks which are hard to neutralize without impact.

The reply goes on to say that new clients were being distributed to other endpoints and that availability appeared to improve there. Its date was not supplied. The wording acknowledges a possible cause of some problems; it does not identify the cause of every reported interruption or promise that the existing customer's endpoint was fixed.

For this customer, the combination of long interruptions and an unresolved support experience was enough to look elsewhere. A public service needs a working route during the hours its users rely on 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. The customer's June 22 and July 2 reports fall within that interval.

The page also listed recent GRE incidents, including September 14, 01:13–01:39, and September 15, 00:53–01:10, in its displayed times. Those entries show that outages are published. The blank period cannot establish deliberate deletion or explain how the aggregate percentage was calculated.

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.

Separate throughput from complete loss of service

When the connection worked, the customer reports approximately 100 Mbps download and 40 Mbps upload. These figures describe their experience. No benchmark logs were supplied establishing the test server, tunnel configuration, MTU, or bottleneck.

A complete interruption is a separate failure: the service becomes unreachable. For a game server, even modest bandwidth use does not make that acceptable. When testing an alternative, check successful game sessions and sustained reachability alongside throughput.

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.

These are concrete reasons to evaluate Taipan when GRE alone no longer fits the deployment. No matched uptime or gaming benchmark is available here to claim universal performance superiority. Test the route that will carry your own users.

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.

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.

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.