mancombseepgood
Executive Member
Man this is frustrating... switching to old vrot dial-up
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is the ultimate French toast topping?
Trouble with MTN GPRS
- Thread starter sun
- Start date
mancombseepgood
Executive Member
This is not just an MTN problem by the looks of things. I am on dial-up to saix and cant access www.vodacom.co.za among other sites. Probably a SAIX peering problem
bekdik
Honorary Master
EdRobinson said:
Doesn't work for me either. May be a dns problem.
Skeptik
Banned
VODA has been quite stable for a record time. MTN could learn something ;-)ajax said:
snorbaard
Active Member
Ye olde lurker here. Came here in despreration because I've been having this abovementioned problems since Friday.
Now Saturday evening, and it seems that local sites are ok (streaming 702 no problem), but anything international just makes my PDA browsers timeout.
Of course this would happen just as I bought a 350MB bundle.. Grr..
Now Saturday evening, and it seems that local sites are ok (streaming 702 no problem), but anything international just makes my PDA browsers timeout.
Of course this would happen just as I bought a 350MB bundle.. Grr..
While GPRS mostly seems to be back, I have been having intermittent trouble with overseas traffic...resulting in DNS lookup failures and very slow page loads/timeouts/"document contains no data", etc.
For the past few days, I've been avoiding this by running through an HTTP proxy in my office, so that at least for WWW stuff (i) no DNS lookup needed, (ii) my international stuff goes via TENET.
This afternoon, even that seems to be running deadly slow...connections to my local proxy are horrible as well.
From looking at a bunch of pings and traceroutes, it looks like there's heavy packet loss going anywhere outside MTNs backbone (I can see www.mtn.co.za just fine), but get 30%+ packet loss anyplace else...
FWIW, here's a couple of traceroutes:
to www.mtn.co.za -- looks good:
traceroute to www.mtn.co.za (196.11.240.60), 30 hops max, 38 byte packets
1 * * *
2 196.11.241.209 540.096 ms 596.912 ms 664.855 ms
3 196.11.241.214 587.107 ms 598.981 ms 647.010 ms
4 196.11.240.122 585.010 ms 742.962 ms 611.994 ms
5 196.11.240.122 589.949 ms 610.063 ms 614.953 ms
To a box in Canada -- looks awful:
traceroute to soren.aalto.tv (209.121.69.99), 30 hops max, 38 byte packets
1 * * *
2 196.11.241.209 794.887 ms 599.947 ms 542.993 ms
3 196.11.241.214 635.976 ms 675.006 ms 585.995 ms
4 196.11.241.6 639.992 ms 608.972 ms *
5 196.44.8.210 574.752 ms * 437.772 ms
6 196.44.8.86 670.017 ms 695.955 ms 635.998 ms
7 209.212.111.129 838.237 ms * 974.872 ms
8 213.152.230.90 761.212 ms * 839.553 ms
9 208.184.231.174 911.048 ms 815.963 ms 824.282 ms
10 * * 64.125.31.186 1130.029 ms
11 64.125.31.46 925.983 ms 899.996 ms 962.024 ms
12 64.125.29.185 893.981 ms * 1087.819 ms
13 216.200.254.29 908.978 ms * *
14 * 154.11.4.67 1102.931 ms 973.898 ms
15 208.181.240.89 935.074 ms 941.944 ms 949.275 ms
16 * 209.121.69.99 1111.853 ms !<10> 792.206 ms !<10>
...that's 11 missed probes out of the 39 sent from hop 4
onwards, which is about 25%. Not really livable.
For the past few days, I've been avoiding this by running through an HTTP proxy in my office, so that at least for WWW stuff (i) no DNS lookup needed, (ii) my international stuff goes via TENET.
This afternoon, even that seems to be running deadly slow...connections to my local proxy are horrible as well.
From looking at a bunch of pings and traceroutes, it looks like there's heavy packet loss going anywhere outside MTNs backbone (I can see www.mtn.co.za just fine), but get 30%+ packet loss anyplace else...
FWIW, here's a couple of traceroutes:
to www.mtn.co.za -- looks good:
traceroute to www.mtn.co.za (196.11.240.60), 30 hops max, 38 byte packets
1 * * *
2 196.11.241.209 540.096 ms 596.912 ms 664.855 ms
3 196.11.241.214 587.107 ms 598.981 ms 647.010 ms
4 196.11.240.122 585.010 ms 742.962 ms 611.994 ms
5 196.11.240.122 589.949 ms 610.063 ms 614.953 ms
To a box in Canada -- looks awful:
traceroute to soren.aalto.tv (209.121.69.99), 30 hops max, 38 byte packets
1 * * *
2 196.11.241.209 794.887 ms 599.947 ms 542.993 ms
3 196.11.241.214 635.976 ms 675.006 ms 585.995 ms
4 196.11.241.6 639.992 ms 608.972 ms *
5 196.44.8.210 574.752 ms * 437.772 ms
6 196.44.8.86 670.017 ms 695.955 ms 635.998 ms
7 209.212.111.129 838.237 ms * 974.872 ms
8 213.152.230.90 761.212 ms * 839.553 ms
9 208.184.231.174 911.048 ms 815.963 ms 824.282 ms
10 * * 64.125.31.186 1130.029 ms
11 64.125.31.46 925.983 ms 899.996 ms 962.024 ms
12 64.125.29.185 893.981 ms * 1087.819 ms
13 216.200.254.29 908.978 ms * *
14 * 154.11.4.67 1102.931 ms 973.898 ms
15 208.181.240.89 935.074 ms 941.944 ms 949.275 ms
16 * 209.121.69.99 1111.853 ms !<10> 792.206 ms !<10>
...that's 11 missed probes out of the 39 sent from hop 4
onwards, which is about 25%. Not really livable.