S L O W slow load times

  • Problem
  • Updated 6 years ago
very slow connects to phitter

3 30 ms 11 ms 14 ms ip70-183-64-53.ks.ks.cox.net [70.183.64.53]
4 55 ms 19 ms 19 ms kscydsrj01-ae2.rd.ks.cox.net [70.183.71.101]
5 20 ms 21 ms 17 ms 70.183.71.61
6 30 ms 31 ms 31 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
7 36 ms 30 ms 31 ms 10ge-ten1-1.dal-eqx-cor-2.peer1.net [216.187.124
134]
8 48 ms 52 ms 51 ms 10ge-ten2-1.atl-telx-cor-1.peer1.net [216.187.12
.118]
9 49 ms 50 ms 51 ms 216.187.120.210
10 68 ms 62 ms 57 ms atl2prddsrt03-vlan4.net.interland.net [64.224.0.
01]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
Photo of phittermaster

phittermaster

  • 6 Posts
  • 0 Reply Likes
  • what happened to the Phast Pheed

Posted 6 years ago

  • 2
Photo of phittermaster

phittermaster

  • 6 Posts
  • 0 Reply Likes
Even Kristie has this same issue... hello?
Photo of phittermaster

phittermaster

  • 6 Posts
  • 0 Reply Likes
I see others are having the same issue. Server space? Bandwidth?
Photo of Dragon

Dragon

  • 3 Posts
  • 1 Reply Like
Phittermaster, would you please do a tracert again when you notice Phitter being slow. BTW, the "Request Timed Out" messages above are normal and don't reflect a performance problem; they are caused because the networking equipment where the Phitter servers does not allow the type of communications that Tracert or Ping uses (ICMP) to get to the servers for security reasons.
Photo of phittermaster

phittermaster

  • 6 Posts
  • 0 Reply Likes
3 11 ms 11 ms 11 ms ip70-183-64-53.ks.ks.cox.net [70.183.64.53]
4 16 ms 22 ms 19 ms kscydsrj01-ae2.rd.ks.cox.net [70.183.71.101]
5 17 ms 20 ms 19 ms 70.183.71.61
6 34 ms 35 ms 37 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
7 42 ms 27 ms 30 ms 10ge-ten1-1.dal-eqx-cor-2.peer1.net [216.187.124
34]
8 79 ms 80 ms 83 ms 10ge-ten2-1.atl-telx-cor-1.peer1.net [216.187.12
118]
9 97 ms 78 ms 79 ms 216.187.120.210
0 81 ms 77 ms 76 ms atl2prddsrt03-vlan4.net.interland.net [64.224.0.
1]
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 *
Photo of phittermaster

phittermaster

  • 6 Posts
  • 0 Reply Likes
Photo of phittermaster

phittermaster

  • 6 Posts
  • 0 Reply Likes
3 23 ms 31 ms 19 ms ip70-183-64-53.ks.ks.cox.net [70.183.64.53]
4 87 ms 19 ms 18 ms kscydsrj01-ae2.rd.ks.cox.net [70.183.71.101]
5 37 ms 114 ms 21 ms 70.183.71.61
6 42 ms 32 ms 33 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
7 35 ms 30 ms 32 ms 10ge-ten1-1.dal-eqx-cor-2.peer1.net [216.187.124
34]
8 79 ms 82 ms 87 ms 10ge-ten2-1.atl-telx-cor-1.peer1.net [216.187.12
118]
9 83 ms 82 ms 79 ms 216.187.120.210
0 89 ms 78 ms 87 ms atl2prddsrt03-vlan4.net.interland.net [64.224.0.
1]
1 * * * Request timed out.
2 * *
Photo of Phitter Support

Phitter Support, Official Rep

  • 109 Posts
  • 8 Reply Likes
Official Response
Thank you for the detailed info...we are aware of the problem, partially caused by bot spam and we are addressing as well completing software and hardware upgrades by next tues hopefully.