Immediate Error Report: Telekom -> Cloudflare -> GGG Entry Server

Immediate Error Report: Telekom -> Cloudflare -> GGG Entry Server

Scope
The affected path is session establishment to 173.233.128.92, a Servers.com-hosted entry server in the reassigned SERVERS-COM-LON1 block. The WinMTR trace shows that the route does not end directly at the origin, but passes through multiple Cloudflare hops before reaching the destination.



WinMTR log


Route Snapshot
Client / Telekom DE
-> *.dip0.t-ipconnect.de
-> b-eh3-i.b.de.net.dtag.de
-> ae10.edge5.ber1.sp.lumen.tech
-> dialup-212.162.17.178.frankfurt1.mik.net
-> 162.158.245.113
-> 162.158.245.140
-> 162.158.245.132
-> 188.42.187.153
-> 173.233.128.92

Critical Findings
Component Finding
DTAG access/core Early hops are stable, no loss.
Cloudflare edge path Multiple Cloudflare IPs appear before origin, indicating Cloudflare fronting.
Transit after Cloudflare Path degrades sharply after Cloudflare-adjacent hops.
Pre-target node 188.42.187.153 shows 2% loss and 70 ms average RTT.
Target 173.233.128.92 is reached with 2% loss, 68 ms average RTT, 143 ms worst RTT.
Origin hosting Target IP belongs to Servers.com, block labeled SERVERS-COM-LON1.

Fault Pattern
Telekom local path OK
Telekom -> Cloudflare suboptimal
Cloudflare -> transit detour / unstable
Transit -> origin degraded but reachable

Technical Assessment
The fault pattern is consistent with poor interconnect or peering behavior for Telekom traffic toward a Cloudflare-fronted origin. Because the entry server is exposed through Cloudflare Free, the traffic is likely falling back to a non-prioritized path with massive routing detours and elevated latency and jitter.

User Impact
- Delayed login and instance entry
- Elevated latency and jitter during session establishment
- Intermittent packet loss on the final path segment
- Disproportionate impact for Deutsche Telekom users

Required Action
- Move the affected Cloudflare-protected entry endpoint off the Free plan.
- Upgrade the Cloudflare service tier to Pro for the affected entry-facing hostname or IP path.
- Re-test DTAG routes after the change and verify lower RTT, reduced detour behavior, and loss removal at target.

Executive Statement
The issue is not a local access fault and not primarily a Servers.com origin outage. The active fault domain is the Telekom -> Cloudflare Free-tier routing path in front of the GGG entry server, and the operational fix is to raise the Cloudflare service tier to improve path treatment for Telekom-originating traffic.

DevOps Error Report — Telekom DE / Sunday 20:00

Incident Summary
Client: Telekom DE
Path: local access -> DTAG -> Colt -> Cloudflare -> target
Impact: in-game latency spikes up to 2000 ms
Status: unusable

Observed Route
fritz.box
192.168.*
*.dip0.t-ipconnect.de
f-eh1-i.f.de.net.dtag.de
193.158.39.70
ae1.3107.edge6.dus1.neo.colt.net
149.6.66.7
188.42.168.217
23.111.5.42

Packet Loss / Latency
193.158.39.70 19% loss
149.6.66.7 4% loss
188.42.168.217 19% loss
23.111.5.42 6% loss
Worst-case RTT 50-96 ms on transit hops
In-game spikes up to 2000 ms

Critical Findings
- Early LAN and Telekom hops are stable.

Packet loss begins after the DTAG segment.

Colt is present as an additional transit layer.

The path degrades further toward the target.

End-to-end usability is broken by severe RTT spikes and loss.

Fault Domain
Primary: external routing / peering
Secondary: Colt transit path
Tertiary: Cloudflare-fronted target path
Not primary: local client network

Required Action
Urgently move the affected Cloudflare Free setup to Cloudflare Pro.
The current Free-plan path is producing degraded routing treatment, detours, packet loss, and severe latency spikes for Telekom users.

There is a known issue with Telekom and Cloudflare re-routing and not an issue with GGG servers or game.

The recommended solution is to drop one of those two.

"

c0rnel#6051 wrote:

There is a known issue with Telekom and Cloudflare re-routing and not an issue with GGG servers or game.

The recommended solution is to drop one of those two.

better read it before posting pure trash.

it is in fact the cf free plan which is used so it IS a ggg case routing wise.

"

malignitass#3144 wrote:

The WinMTR trace shows that the route does not end directly at the origin, but passes through multiple Cloudflare hops before reaching the destination.

If you stop and think about this sentence... you'll realise it doesn't make sense.

"

malignitass#3144 wrote:

Speaking of things that don't make sense...

Why does it randomly say "jitter" with no value? What do the red arrows mean?

Please, for the love of god - stop asking ChatGPT to explain diagnostics to you. It attempts to guess at how the conversation continues. That's it - that's what the technology does. It doesn't know how to parse a WinMTR log; it isn't even trying to do that.

You know why it's saying "Cloudflare bad" ? Because its training data includes people saying that. That's how it works. It reads the prompt, and then shuffles elements of its training data around, and then spits out a hopefully coherent (not in this case!) response. That is literally all it does.

"

malignitass#3144 wrote:

DTAG access/core Early hops are stable, no loss.

Really?

Because that's where the AI put a bunch of scary, red, broken-looking arrows...

"

malignitass#3144 wrote:

Because the entry server is exposed through Cloudflare Free

It isn't, btw.

Cloudflare's Pricing webpage is publicly visible. You can literally read it at any time, and then you would know what to look for to confirm or deny the frankly bizarre fixation across several of your posts. Or, apparently, you can instead delegate critical thinking... to a chat bot.

"

malignitass#3144 wrote:

Because the entry server is exposed through Cloudflare Free, the traffic is likely falling back to a non-prioritized path with massive routing detours and elevated latency and jitter.

Yeah... no.

Cloudflare don't employ "massive routing detours" and "elevated latency and jitter" just because a company uses their free subscription tier, which GGG doesn't even do. Crazy stuff.

"

malignitass#3144 wrote:

Disproportionate impact for Deutsche Telekom users

Hang on.

A moment ago the traffic was fine at that stage of the route, and it was only big bad Cloudflare and their evil free tier which was causing problems. So which is it? Because they can't both be true.

"

malignitass#3144 wrote:

Upgrade the Cloudflare service tier to Pro

But what if GGG can't afford $20 / month? ☹️

"

malignitass#3144 wrote:

DevOps Error Report — Telekom DE / Sunday 20:00

That's... not what DevOps means...

"

malignitass#3144 wrote:

192.168.*

Any particular reason you're redacting a private IP address?

Maybe ask your chat bot to sit a CCNA exam sometime, because there is literally zero reason to do that.

https://en.wikipedia.org/wiki/Private_network#Private_IPv4_addresses

"

malignitass#3144 wrote:

better read it before posting pure trash.

The entire thread is nothing but ChatGPT-generated hallucinations which don't even have the decency to be internally consistent - every time it attempts to explain at what part of the route the problem occurs, it changes the answer. Because it doesn't know.

You're in no position to be denigrating the posts of others.