Why is DegreeForum so SLOW lately?

[ss20ts]

The lagging issues aren't happening for me today! YAY!!!

[rachel83az]

I haven't noticed any slowness today either.

[LevelUP]

Yesterday, 2 of my posts ended up timing out.

Hanging in there so far.

[LevelUP]

400 users are now online. Still fast.

[bjcheung77]

Great job, they seem to have fixed that load balancing, ISP, or server issues plaguing DegreeForum for the past week or so...

[bjcheung77]

In short... Noticed slowness issues today, so I did a ping and tracert like last time...
Here's the info, very similar to post #3, as hop #13 seems to be missing that server.

Microsoft Windows [Version 10.0.22000.2538]
© Microsoft Corporation. All rights reserved.

ping degreeforum.net

Pinging degreeforum.net [67.225.168.56] with 32 bytes of data:
Reply from 67.225.168.56: bytes=32 time=79ms TTL=56
Reply from 67.225.168.56: bytes=32 time=79ms TTL=56
Reply from 67.225.168.56: bytes=32 time=80ms TTL=56
Reply from 67.225.168.56: bytes=32 time=80ms TTL=56

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

tracert degreeforum.net

Tracing route to degreeforum.net [67.225.168.56]
over a maximum of 30 hops:

4 6 ms 7 ms 6 ms be-205-pe12.seattle.wa.ibone.comcast.net [173.167.57.213]
5 6 ms 6 ms 6 ms be-2112-cs01.seattle.wa.ibone.comcast.net [96.110.34.129]
6 6 ms 6 ms 6 ms be-1111-cr11.seattle.wa.ibone.comcast.net [96.110.47.178]
7 32 ms 31 ms 31 ms be-301-cr11.champa.co.ibone.comcast.net [96.110.36.209]
8 32 ms 31 ms 32 ms be-1311-cs03.champa.co.ibone.comcast.net [96.110.37.201]
9 33 ms 31 ms 32 ms be-1313-cr13.champa.co.ibone.comcast.net [96.110.37.234]
10 32 ms 32 ms 31 ms be-304-cr13.1601milehigh.co.ibone.comcast.net [96.110.36.206]
11 31 ms 32 ms 31 ms be-1113-cs01.1601milehigh.co.ibone.comcast.net [96.110.39.97]
12 32 ms 31 ms 32 ms be-1111-cr11.1601milehigh.co.ibone.comcast.net [96.110.39.66]
13 * * * Request timed out.
14 56 ms 56 ms 54 ms be-1121-cs21.350ecermak.il.ibone.comcast.net [68.86.82.241]
15 55 ms 58 ms 56 ms be-2103-pe03.350ecermak.il.ibone.comcast.net [96.110.37.18]
16 77 ms 78 ms 77 ms as32244-pe03.350ecermak.il.ibone.comcast.net [50.242.150.130]
17 81 ms 81 ms 81 ms lw-dc2-core1-nexus-eth3-19.rtr.liquidweb.com [209.59.157.224]
18 80 ms 81 ms 80 ms lw-dc2-dist3.rtr.liquidweb.com [209.59.157.101]
19 82 ms 80 ms 80 ms host3.degreeforum.net [67.225.168.56]

Trace complete.

[jch]

That traceroute does not actually indicate any issue. Note that after hop 13, you're still receiving responses, including from the final destination. How would that happen if you were experiencing 100% loss on hop 13? Well, it wouldn't. As all of your probes made it to and from the destination with an acceptable latency, there is no problem demonstrated. Note that, like any measurement system, it's important to think through traceroute responses and understand what it's actually telling you. There's a hop that simply won't respond to traceroutes, which is quite normal and not an issue. While traceroute appears to be a simple tool, it's quite difficult to apply and interpret correctly.

[bjcheung77]

Getting this error as well, in addition to the slowness issue.

[LevelUP]

Getting this error as well, in addition to the slowness issue.

Slow for me too.

736 users active in the past 15 minutes. 725 guests. Website traffic is higher than usual.

[RJ77]

Getting this error as well, in addition to the slowness issue.

I've been getting the same thing a lot the last few days. When the pages do load, they're extremely slow.