• Unfortunately, we have experienced significant hard drive damage that requires urgent maintenance and rebuilding. The forum will be a state of read only until we install our new drives and rebuild all the configurations needed. Please follow our Facebook page for updates, we will be back up shortly! (The forum could go offline at any given time due to the nature of the failed drives whilst awaiting the upgrades.) When you see an Incapsula error, you know we are in the process of migration.

So slow

Joined
Jun 23, 2010
Messages
2,324
Reaction score
2,195
It's so damn slow, RZ.
Or is it just me, other websites are loading fine.

Code:
ping forum.ragezone.com /t

Pinging 2vr86.x.incapdns.net [149.126.72.206] with 32 bytes of data:
Request timed out.
Reply from 149.126.72.206: bytes=32 time=108ms TTL=52
Request timed out.
Reply from 149.126.72.206: bytes=32 time=118ms TTL=52
Request timed out.
Reply from 149.126.72.206: bytes=32 time=79ms TTL=52
Reply from 149.126.72.206: bytes=32 time=21ms TTL=52
Reply from 149.126.72.206: bytes=32 time=23ms TTL=52
Reply from 149.126.72.206: bytes=32 time=24ms TTL=52
Reply from 149.126.72.206: bytes=32 time=17ms TTL=52
Reply from 149.126.72.206: bytes=32 time=18ms TTL=52
Request timed out.
Reply from 149.126.72.206: bytes=32 time=118ms TTL=52
Request timed out.
Reply from 149.126.72.206: bytes=32 time=107ms TTL=52
Reply from 149.126.72.206: bytes=32 time=115ms TTL=52
Reply from 149.126.72.206: bytes=32 time=114ms TTL=52
Reply from 149.126.72.206: bytes=32 time=111ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Reply from 149.126.72.206: bytes=32 time=25ms TTL=52
Reply from 149.126.72.206: bytes=32 time=21ms TTL=52
Reply from 149.126.72.206: bytes=32 time=14ms TTL=52
Reply from 149.126.72.206: bytes=32 time=27ms TTL=52
Reply from 149.126.72.206: bytes=32 time=14ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 149.126.72.206: bytes=32 time=15ms TTL=52
Reply from 149.126.72.206: bytes=32 time=15ms TTL=52
Reply from 149.126.72.206: bytes=32 time=27ms TTL=52
Reply from 149.126.72.206: bytes=32 time=31ms TTL=52
Reply from 149.126.72.206: bytes=32 time=24ms TTL=52
Request timed out.
Reply from 149.126.72.206: bytes=32 time=107ms TTL=52
Request timed out.
Request timed out.
Reply from 149.126.72.206: bytes=32 time=114ms TTL=52
Request timed out.
Reply from 149.126.72.206: bytes=32 time=113ms TTL=52
Request timed out.
Reply from 149.126.72.206: bytes=32 time=115ms TTL=52
Request timed out.
Reply from 149.126.72.206: bytes=32 time=24ms TTL=52
Request timed out.
Reply from 149.126.72.206: bytes=32 time=113ms TTL=52
Request timed out.

Ping statistics for 149.126.72.206:
    Packets: Sent = 51, Received = 29, Lost = 22 (43% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 118ms, Average = 61ms

Seems some sort of dddoss.

It's slightly better now and not that annoying.
 
Last edited:
Moderator
Staff member
Moderator
Joined
Jul 30, 2012
Messages
1,103
Reaction score
432
Still as unstable as to when 'we' complained about Like being slow. Its not as annoying like browsing is ok but still slower than other sites.

Unstable being its sometimes ok and sometimes really slow.
 
Back
Top