Extremely slow speed to this site

Mean_Monster

Senior Member
Joined
Mar 2, 2004
Messages
584
Reaction score
0
Location
Cape Town, South Africa
Hi guys,

Just wondering if anyone else is experiencing very slow response from this site tonight 8July 2008 @ 9:35PM. News section doesn't even want to open properly?
 
i think it was last night that i found it to be very slow. there is another south african forum i have been trying to get on for a week or so and i cannot get on there for some reason. its annoying.
 
ping times seem normal to me to hetzner, myadsl.co.za and google.co.za yet it's slow as schitte. improved a wee bit when I turned on ad block and added google-analytics. Will turn it off again when things improve

gru@ogre:~$ ping -c5 www.myadsl.co.za
PING www.myadsl.co.za (196.40.97.13) 56(84) bytes of data.
64 bytes from 196.40.97.13: icmp_seq=1 ttl=246 time=48.9 ms
64 bytes from 196.40.97.13: icmp_seq=2 ttl=246 time=47.1 ms
64 bytes from 196.40.97.13: icmp_seq=3 ttl=246 time=47.2 ms
64 bytes from 196.40.97.13: icmp_seq=4 ttl=246 time=47.1 ms
64 bytes from 196.40.97.13: icmp_seq=5 ttl=246 time=48.4 ms

--- www.myadsl.co.za ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 20331ms
rtt min/avg/max/mdev = 47.148/47.800/48.956/0.796 ms

gru@ogre:~$ ping -c5 www.hetzner.co.za
PING hetzner.co.za (196.22.142.41) 56(84) bytes of data.
64 bytes from dedi141.jnb1.host-h.net (196.22.142.41): icmp_seq=1 ttl=247 time=26.9 ms
64 bytes from dedi141.jnb1.host-h.net (196.22.142.41): icmp_seq=2 ttl=247 time=29.5 ms
64 bytes from dedi141.jnb1.host-h.net (196.22.142.41): icmp_seq=3 ttl=247 time=28.4 ms
64 bytes from dedi141.jnb1.host-h.net (196.22.142.41): icmp_seq=4 ttl=247 time=26.8 ms
64 bytes from dedi141.jnb1.host-h.net (196.22.142.41): icmp_seq=5 ttl=247 time=28.2 ms

--- hetzner.co.za ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 26.803/28.019/29.597/1.055 ms

gru@ogre:~$ ping -c5 www.google.co.za
PING www.l.google.com (209.85.129.99) 56(84) bytes of data.
64 bytes from fk-in-f99.google.com (209.85.129.99): icmp_seq=1 ttl=235 time=345 ms
64 bytes from fk-in-f99.google.com (209.85.129.99): icmp_seq=2 ttl=235 time=346 ms
64 bytes from fk-in-f99.google.com (209.85.129.99): icmp_seq=3 ttl=235 time=345 ms
64 bytes from fk-in-f99.google.com (209.85.129.99): icmp_seq=4 ttl=235 time=354 ms
64 bytes from fk-in-f99.google.com (209.85.129.99): icmp_seq=5 ttl=235 time=346 ms

--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 345.071/347.558/354.069/3.374 ms

gru@ogre:~$ ping -c5 secure-za.imrworldwide.com
PING secure-za.imrworldwide.com (196.36.153.226) 56(84) bytes of data.
64 bytes from dn02-za.imrworldwide.com (196.36.153.226): icmp_seq=1 ttl=58 time=48.7 ms
64 bytes from dn02-za.imrworldwide.com (196.36.153.226): icmp_seq=2 ttl=58 time=50.0 ms
64 bytes from dn02-za.imrworldwide.com (196.36.153.226): icmp_seq=3 ttl=58 time=48.2 ms
64 bytes from dn02-za.imrworldwide.com (196.36.153.226): icmp_seq=4 ttl=58 time=49.7 ms
64 bytes from dn02-za.imrworldwide.com (196.36.153.226): icmp_seq=5 ttl=58 time=50.0 ms

--- secure-za.imrworldwide.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 48.231/49.353/50.036/0.762 ms

gru@ogre:~$ ping -c5 www.imrworldwide.com
PING www.imrworldwide.com (203.166.18.175) 56(84) bytes of data.
64 bytes from 203.166.18.175: icmp_seq=1 ttl=45 time=335 ms
64 bytes from 203.166.18.175: icmp_seq=2 ttl=45 time=334 ms
64 bytes from 203.166.18.175: icmp_seq=3 ttl=45 time=337 ms
64 bytes from 203.166.18.175: icmp_seq=4 ttl=45 time=349 ms
64 bytes from 203.166.18.175: icmp_seq=5 ttl=45 time=335 ms

--- www.imrworldwide.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 21902ms
rtt min/avg/max/mdev = 334.349/338.504/349.894/5.781 ms

gru@ogre:~$ ping -c5 google-analytics.com
PING google-analytics.com (64.233.161.99) 56(84) bytes of data.
64 bytes from od-in-f99.google.com (64.233.161.99): icmp_seq=1 ttl=239 time=331 ms
64 bytes from od-in-f99.google.com (64.233.161.99): icmp_seq=2 ttl=239 time=331 ms
64 bytes from od-in-f99.google.com (64.233.161.99): icmp_seq=3 ttl=239 time=329 ms
64 bytes from od-in-f99.google.com (64.233.161.99): icmp_seq=4 ttl=239 time=335 ms
64 bytes from od-in-f99.google.com (64.233.161.99): icmp_seq=5 ttl=239 time=330 ms

--- google-analytics.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3997ms
rtt min/avg/max/mdev = 329.010/331.581/335.263/2.209 ms
 
Yeah I'm battling to browse this site too, using DSL or 3G makes no difference, slow, very slow....
 
I am on Virgin GPRS posting this because my ADSL is slow I can't open the forum. International is effected as well :mad:

Those China Telscum evil mongers and their loops :mad:
 
Seems to be slightly better, back on ADSL.

I noticed something, I'll report this post to tell uncle rpm. I thought that after uninstalling noscript tonight that it left over files which "blocked" the ads on the site, so I reinstalled Firefox and gave it a complete new installation.

Even after the reinstallation the ads were gone, when I switched to Virgin just now, all of the sudden the ads were back. This could either be that SAIX was blocking the ads, or I don't have a clue :confused:

Weird stuff going on lately :p
 
Seems to have become normal now. Notice before something about serv.mybroadband.co.za << maybe ads server? Maybe that is why I had so many page cannot be displayed errors on news section.
 
I think RPM mentioned earlier today somewhere something about network whatever ..... back to normal now though :D
 
This was definitely an SAIX issue, since both the Telscum and Webafrica account did it :(
 
Sorry to dredge up a moderately old thread :D

Site is horrendously slow almost all the time - confirmed with 3 others from different cities. Anyone else having this issue? I'm determined to figure out why. Perhaps it's just vBulletin being bloated :D
 
Top
Sign up to the MyBroadband newsletter
X