Ping requests time out to CF IPs, site loads slowly in real world

[john247]

What is the name of the domain?

schoolleaderhq.com

What is the error message?

request timed out

What is the issue you’re encountering

dropped packets, slow loading

What steps have you taken to resolve the issue?

I have checked settings on CF. Reviewed help and set up guidance. Checked speed
test information - real world is poor but CF test is good, caching is set up correctly as far as I can see.

What feature, service or problem is this related to?

I don’t know

What are the steps to reproduce the issue?

ping 188.114.96.3 to see the delays vs the origin server of 77.72.2.35.

Screenshot of the error

[DarkDeviL]

@john247

ping 188.114.96.3

What about traceroute (tracert with Windows)?

@john247

real world is poor

Can you elaborate on where you see these issues?

1. What ISP / provider, preferably their AS number?
   The AS number can be found here:

• https://1.1.1.1/help
  → AS Number
• https://bgp.tools/
  → The AS number shown under “You are connecting from” like this: “Cloudflare, Inc. (AS13335)”
• https://bgp.he.net/
  → The AS number shown like this: “Your ISP is AS13335 (Cloudflare, Inc.)”

2. What country (and preferably state/region)?

[john247]

Thanks for responding. To answer your question I am [AS3320] Working from Germany via DT.
I noticed that the site was loading exceptionally slowly, I have been otherwise engaged for a couple of weeks and had not checked it until now. Previously it was working very well and no config changes were made in the interim. I have gone through and checked all DNS settings, caching etc seem to be correctly configured. The ping to the server seems to correspond to the slow response times. Tracert result added below.

[john247]

Also - just noticed that I miss-typed the url, schoolleadershiphq.com
Thanks in advance,
j

[DarkDeviL]

@john247

I am [AS3320] Working from Germany via DT.

That is unfortunately a well-known problem, which has been brought up multiple times already, such as e.g. here:

@DarkDeviL

@DarkDeviL

The issue(s) with AS3320 Deutsche Telekom has been well-known for years, not only in regards to Cloudflare.

AS3320 Deutsche Telekom seem to refuse to peer directly with Cloudflare (as well as many other networks), which in the end is causing the result that traffic has to go through alternative paths (assuming such alternative paths are available, which they may not always be).

AS3320 Deutsche Telekom have similarly been in the media several times over the years, allegedly for not wanting to ensure proper capacity on their peering links, and so forth, which for example caused AS174 Cogent Communiations to send a lawsuit towards AS3320 Deutsche Telekom some years ago.

Unless AS3320 Deutsche Telekom wants to man up and participate in creating a better Internet, I’m unfortunately afraid you shouldn’t be expecting any remediation from AS3320 Deutsche Telekom (or any of it’s subsidiaries).

AS3320 Deutsche Telekom’s bad decisions is not only hitting Cloudflare, but also (many) other networks.