Cloudflare DNS very slow?!
Hi devs! I've moticed 1-2 days ago that my site under Cloudflare (including all subdomains and subsites) was very slow.
I have already tried emptying the DNS cache and setting the proxy (turning it on/off), but I was unsuccessful.
What could be causing this slowness? At first I thought that the server was slow - but there are e.g. a phpmyadmin is installed, which is extremely slow at the address "pma.domain.com", and lightning fast when reache it directly by IP - so I don't think that my server is at fault.
I would like to add that there is also a Cloudflare pages page on this domain, which is also unbelievably slow.
24 Replies
would you be able to share the url of your pages site?
wait, opening it from your own domain is slow, but using the pages url it's fast?
yes
own domain is under cloudflare
that is very peculiar. sometimes isps will route connections through cloudflare a bit slower, but that doesn't seem to be the case here
have you also experienced the slowness on the main* domain?
i've spent about a day to know what is happening here but I have absolutely no idea
nope, they are both loading "equally" fast
does this issue only happen on a specific device?
or on multiple/for multiple people
to be honest i've also tried from mobile (with mobile network) and same issue
have you tried running a traceroute? that's
tracert nasicsomag.hu on windows
typing on mobile is hard...omg good idea! checking..
To main domain:
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 129 ms 136 ms 138 ms 2003:3c0:1600:8000::1
7 109 ms 109 ms 109 ms ash-b2-link.ip.twelve99.net [2001:2035:0:2829::1]
8 176 ms * * cloudflare-ic-328259.ip.twelve99-cust.net [2001:2035:0:7bc::2]
9 335 ms 323 ms 300 ms 2400:cb00:350:3::
10 253 ms 262 ms 262 ms 2a06:98c1:3120::7
when i tracert to pages.dev:
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 7 ms 7 ms 7 ms cloudflare-ic-356168.ip.twelve99-cust.net [2001:2035:0:15e5::2]
8 10 ms 7 ms 7 ms cloudflare-ic-356168.ip.twelve99-cust.net [2001:2035:0:15e5::2]
9 8 ms 7 ms 7 ms 2400:cb00:114:3::
10 7 ms 7 ms 7 ms 2606:4700:310c::ac42:2f09
well, thats pretty clear
any idea for the fix? i'm a bit tired
i have a cname (proxied) to my cloudflare pages content
I don't think there's anything that you can do
Those traceroutes look fine to me. Routers often drop ICMP ECHO REQUEST as theses do not run in the fast lane. What counts if the site can be reached, e.g. ping requests and/or curl sessions
traceroute may be helpful if a site cannot be reached.
the delay difference is significant tho, does that not make a difference?
335ms vs 7ms
Yup, 355ms is bad, real bad, but can happen with bad WiFi/mobile
Shouldn't though
At a second look the first bad connection maybe due to bad routing on the internet
A while back DTAG in Germany had such issues routing to some domain hosting providers (long time ago)
They refused to peer with some key partners for business reasons, it was a real pain
I assume that both those traceroutes were made over the same network
In this case I think it is more likely that a network link is broken
hm that could be the case too
yea same network, wired connection.
i'll contact my ISP tomorrow- and i'll try to check the site from my firends house/pc/devices.
Yes, they start from the same point, but if the target IPs are different t they may take different routes. You'd to study the BGP tables to make an informed guess where they go
True
So I have to revise my initial judgement a bit: traceroute is very helpful in this case 🙂
I just wanted to point out that the first timeouts in the traceroutes can be ignored as these happen often and are harmless
Using https://ping.eu/traceroute/ I'm getting almost the same results in traceroute with both domains
Online Ping, Traceroute, DNS lookup, WHOIS, Port check, Reverse loo...
Easy to use web-based traceroute service. Traceroute - Traces the route of packets to destination host from our server.
so It should be a local network issue
yea this seems to be a network/isp problem
my traceroutes to your domain and pages site are virtually identical (delay wise)