Managed to open terminal and ping... here's the results:
Spoke to our mail provider. They reckon 20% of their clients are having similar problems, and they are all with MWEB. Been for the past two days.
I got a friend to run my pop settings in thunderbird, 1500km away using Iburst, and he experiences the same problem. Told this to my mail provider, and he says that its possible Iburst routes through Mweb somewhere along the line. I'm really confused... anyone got any idea?
EDIT:
I got the two concerned parties to write me a mail outlaying their opinions on the problems, here they are:
MWEB:
-=-=-=-=-=-=-=-
From: "Norman Roberts - MWEB" <
[email protected]>
To: <
[email protected]>
Sent: Thu, 24 Jan 2008 09:16:18 +0200
Subject: Mail delay on external server
*
Hi Ryan,
*
*
The Specific Mail server you are relating to is not hosted on the mweb mail server,
so any mail delays or issues are normaly the responsibilty of the hosting server.
Your connection though is through Mweb and that according to you is 100%.
So we can only say that your connection speed would effect both mail and browsing equaly and if this is not the case,
In this instance, the hosting server, which in this case is the mail hosting server,*would be liable for the Mail delays.
*
Regards
Norman
-=-=-=-=-=-=-=-=-=-=-=-=-
NETAGE (MAIL HOSTING):
-=-=-=-=-=-=-=-=-=-=-=
From: "XXX [Net Age - Making websites that work!]" <
[email protected]>
To: XXX
Sent: Thu, 24 Jan 2008 10:18:38 +0200
Subject: Ping replays
Hi Ryan. As per our telephone conversation on 2008-01-24 at about 09:40 am
Comparing ping rates between our servers it's my conclusion that mweb is experiencing latency issues on their adsl servers...
I might be wrong in the assumption of using adsl.mweb.co.za to check the reply times, but from all the support queries we've had majority of callers were using mweb as their adsl/dialup service provider.
PING 196.7.37.187 (196.7.37.187) 56(84) bytes of data.
64 bytes from 196.7.37.187: icmp_seq=1 ttl=57 time=11.7 ms
64 bytes from 196.7.37.187: icmp_seq=2 ttl=57 time=15.9 ms
64 bytes from 196.7.37.187: icmp_seq=3 ttl=57 time=14.0 ms
64 bytes from 196.7.37.187: icmp_seq=4 ttl=57 time=11.7 ms
64 bytes from 196.7.37.187: icmp_seq=5 ttl=57 time=22.1 ms
64 bytes from 196.7.37.187: icmp_seq=6 ttl=57 time=13.9 ms
64 bytes from 196.7.37.187: icmp_seq=7 ttl=57 time=12.1 ms
64 bytes from 196.7.37.187: icmp_seq=8 ttl=57 time=12.4 ms
64 bytes from 196.7.37.187: icmp_seq=9 ttl=57 time=13.4 ms
64 bytes from 196.7.37.187: icmp_seq=10 ttl=57 time=15.1 ms
--- 196.7.37.187 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9023ms
rtt min/avg/max/mdev = 11.733/14.274/22.109/2.941 ms

PING adsl.mweb.co.za (196.2.63.185) 56(84) bytes of data.
64 bytes from 196.2.63.185: icmp_seq=1 ttl=41 time=83.0 ms
64 bytes from 196.2.63.185: icmp_seq=2 ttl=41 time=182 ms
64 bytes from 196.2.63.185: icmp_seq=3 ttl=41 time=188 ms
64 bytes from 196.2.63.185: icmp_seq=4 ttl=41 time=211 ms
64 bytes from 196.2.63.185: icmp_seq=5 ttl=41 time=202 ms
64 bytes from 196.2.63.185: icmp_seq=6 ttl=41 time=128 ms
64 bytes from 196.2.63.185: icmp_seq=7 ttl=41 time=173 ms
64 bytes from 196.2.63.185: icmp_seq=8 ttl=41 time=147 ms
64 bytes from 196.2.63.185: icmp_seq=9 ttl=41 time=113 ms
64 bytes from 196.2.63.185: icmp_seq=10 ttl=41 time=156 ms
--- adsl.mweb.co.za ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 83.071/158.738/211.108/38.870 ms
