site slow?

Currently reading:
site slow?

Yes, I'm sure .

..and yes, every time, every load, every submittal.
When I'm in the mood, I'll change th MTU settings, and see if it makes a difference, failing that I'll get BT to change it their end. Just need to get my ass into gear to do it.

Appreciate your support. (y)
How about that hamster site? Is that the same?
 
Nope, managed to flip through lots of their pages with no trouble at all.
Curses.

They use exactly the same proxy system as us, so I would have expected the same issue.

Oh I know! How about Eper - does that also run just as slow?

Oh and try https://endrop.com - also on the same server, but doesn't go through CloudFlare.
 
Eper, just as slow.

endrop, is fine, pages loading snappily.
At least that tells us the problem is definitely with CloudFlare.

Just not sure where we go from here....

Oh, I wonder if it's a problem with IPv6.

If you ping www.fiatforum.com when using the VPN, does it give you an IPv4 address? (and IPv6 without the VPN?)

And if so, does temporarily disabling IPv6 in linux solve the issue?
 
Yes, it does.

With VPN = IPv4

Command Prompt opened in admin

C:\Windows\system32>ping www.fiatforum.com

Pinging www.fiatforum.com [104.21.64.1] with 32 bytes of data:
Reply from 104.21.64.1: bytes=32 time=11ms TTL=57
Reply from 104.21.64.1: bytes=32 time=12ms TTL=57
Reply from 104.21.64.1: bytes=32 time=11ms TTL=57
Reply from 104.21.64.1: bytes=32 time=11ms TTL=57

Ping statistics for 104.21.64.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms

Without VPN = IPv6
Command Prompt opened in admin

Pinging www.fiatforum.com [2606:4700:3030::6815:5001] with 32 bytes of data:
Reply from 2606:4700:3030::6815:5001: time=9ms
Reply from 2606:4700:3030::6815:5001: time=10ms
Reply from 2606:4700:3030::6815:5001: time=9ms
Reply from 2606:4700:3030::6815:5001: time=9ms

Ping statistics for 2606:4700:3030::6815:5001:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 10ms, Average = 9ms
And if so, does temporarily disabling IPv6 in linux solve the issue?
Not sure about that one, I'm using Win10.
 
Yes, it does.

With VPN = IPv4

Command Prompt opened in admin

C:\Windows\system32>ping www.fiatforum.com

Pinging www.fiatforum.com [104.21.64.1] with 32 bytes of data:
Reply from 104.21.64.1: bytes=32 time=11ms TTL=57
Reply from 104.21.64.1: bytes=32 time=12ms TTL=57
Reply from 104.21.64.1: bytes=32 time=11ms TTL=57
Reply from 104.21.64.1: bytes=32 time=11ms TTL=57

Ping statistics for 104.21.64.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms

Without VPN = IPv6
Command Prompt opened in admin

Pinging www.fiatforum.com [2606:4700:3030::6815:5001] with 32 bytes of data:
Reply from 2606:4700:3030::6815:5001: time=9ms
Reply from 2606:4700:3030::6815:5001: time=10ms
Reply from 2606:4700:3030::6815:5001: time=9ms
Reply from 2606:4700:3030::6815:5001: time=9ms

Ping statistics for 2606:4700:3030::6815:5001:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 10ms, Average = 9ms

Not sure about that one, I'm using Win10.
Ok, so let's see if disabling IPv6 solves it


If it does, then we have more clues!

AHAH!

 
Ok, so let's see if disabling IPv6 solves it


If it does, then we have more clues!

AHAH!


Seems it does. With IPv6 disabled it works fine....

Whats the solution, can it be site specific, I'll look into it as well.
 
Code:
C:\Windows\system32>tracert /d /4 www.fiatforums.com
Tracing route to fiatforums.com [34.120.237.47]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.254
  2     8 ms     6 ms     5 ms  172.16.14.190
  3     *        *        *     Request timed out.
  4     9 ms     9 ms     8 ms  62.172.102.236
  5    10 ms     9 ms    35 ms  194.74.16.175
  6    10 ms     9 ms    10 ms  109.159.253.219
  7    10 ms    11 ms    10 ms  216.239.62.75
  8    11 ms    11 ms    10 ms  142.251.52.145
  9    10 ms     9 ms    10 ms  34.120.237.47

Trace complete.

C:\Windows\system32>tracert /d /6 www.fiatforums.com
Unable to resolve target system name www.fiatforums.com.


First trace is using IPv4, second is IPv6
 
Code:
C:\Windows\system32>tracert /d /4 www.fiatforum.com

Tracing route to www.fiatforum.com [104.21.96.1]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.254
  2     6 ms     6 ms     5 ms  172.16.14.190
  3     *        *        *     Request timed out.
  4    10 ms     9 ms     9 ms  62.172.102.232
  5    10 ms     9 ms     9 ms  195.99.127.50
  6     9 ms     8 ms     8 ms  194.72.16.175
  7     9 ms     9 ms     9 ms  166.49.209.128
  8     9 ms     9 ms     9 ms  166.49.250.59
  9    12 ms    11 ms    10 ms  195.66.225.179
 10    11 ms    11 ms    10 ms  141.101.71.117
 11    10 ms     9 ms    10 ms  104.21.96.1

Trace complete.

C:\Windows\system32>tracert /d /6 www.fiatforum.com

Tracing route to www.fiatforum.com [2606:4700:3030::6815:5001]
over a maximum of 30 hops:

  1  General failure.

Trace complete.

C:\Windows\system32>

Well, at least it found it this time.
I wonder what a 'general failure' is?
 
Code:
C:\Windows\system32>tracert /d /4 www.fiatforum.com

Tracing route to www.fiatforum.com [104.21.96.1]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.254
  2     6 ms     6 ms     5 ms  172.16.14.190
  3     *        *        *     Request timed out.
  4    10 ms     9 ms     9 ms  62.172.102.232
  5    10 ms     9 ms     9 ms  195.99.127.50
  6     9 ms     8 ms     8 ms  194.72.16.175
  7     9 ms     9 ms     9 ms  166.49.209.128
  8     9 ms     9 ms     9 ms  166.49.250.59
  9    12 ms    11 ms    10 ms  195.66.225.179
 10    11 ms    11 ms    10 ms  141.101.71.117
 11    10 ms     9 ms    10 ms  104.21.96.1

Trace complete.

C:\Windows\system32>tracert /d /6 www.fiatforum.com

Tracing route to www.fiatforum.com [2606:4700:3030::6815:5001]
over a maximum of 30 hops:

  1  General failure.

Trace complete.

C:\Windows\system32>

Well, at least it found it this time.
I wonder what a 'general failure' is?
You've remembered to enable IPv6 in Windows already? :LOL:

If it's already on, then I guess that explains why you can't access us / very slowly (if it keeps retrying until no failure)
 
You've remembered to enable IPv6 in Windows already? :LOL:

If it's already on, then I guess that explains why you can't access us / very slowly (if it keeps retrying until no failure)
No, I disabled it. It's pages etc, load fine now. Looks like someones trying to fix it. I've had my fill of it for now.
 
  • Like
Reactions: ben
Back
Top