International speed problems - current network issue?

[zugzug]

Is anyone else having problems at present with the V3G responsiveness?

I am way below my cap. SA sites are loading fast and fine. For offshore sites it is the slowest I have ever, ever seen it. I didn't even think is was working at all but finally after 8 minutes (!!!) the Dilbert.com home page came up. Other offshore sites taking equally long. Is this a current network issue? I am in the CT area. Getting 3G coverage.

Regards Steven

 

[BBSA]

Steven, as I understand most 3G users experience network problems at the moment.

Vodacom did not plan for their growth and now they have run out of capacity. The strange thing is that they still advertising for new 3G customers.

Apparently they are busy upgrading their network; maybe V3G can give us a status report

 

[ic]

zugzug, please post a tracert to the sites you're having problems with, but enclose it in a

 block :).

 

[vodacom3g]

It's a continuous game of catchup in upgrading the international bandwidth. When I spoke to the networking guys earlier this week, they already had the new line in and running but wanted to do some stability tests.

Will check with them on Monday on status.

 

[ic]

Perhaps this is related? or maybe not?

 

[biometrics]

So how about putting in more capacity than needed rather than playing "catchup"?

 

[vodacom3g]

You're right, of course, upgrades should be done 'just-in-time'. Hopefully the new infrastructure going in will allow for this. The 'old' system just ran out of upgrade capability.

 

[BBSA]

The 'old' system just ran out of upgrade capability.

This could have been avoided if Vodacom did proper forecasting and capacity planning and upgraded their “old” system before it run out of capacity.

 

[ic]

This could have been avoided if Vodacom did proper forecasting and capacity planning and upgraded their “old” system before it run out of capacity.

True, but I suspect there is a lot more to this whole story, and I expect that Vodacom would prefer not to wash dirty laundry in public, just remember that for as long as links/pipes are being used that are rented from Telkomonopoly, the timeframe for any capacity upgrade is a ball that Telkomonopoly has 100% control over, and how does one plan the next capacity upgrade when the last one has not been actioned yet by Telkomonopoly...?

Supposition here on my part, but it is what I suspect has been happening with Vodacom's 3G, it is well known that Telkomonopoly drag their feet on many other peering capacity upgrades [not just the IS/SAIX links], and part of that is possibly bcos Telkomonopoly have retrenched so many people that no one is left to do the job in a reasonable amount of time...

 

[zugzug]

Super slow again! (tracert included)

Me again. Having a painful experience again. Here is a tracert example for www.cnet.com. Looks like it is taking the long way round with pretty horrible times for each step. Comments?

C:\Documents and Settings\OM59573>tracert www.cnet.com

Tracing route to c10-ssa-xw-lb.cnet.com [216.239.115.141]
over a maximum of 30 hops:

  1   536 ms   459 ms   446 ms  196-46-160-1.gprs.vodacom.co.za [196.46.160.1]
  2   425 ms   459 ms   461 ms  168.210.129.129
  3   418 ms   473 ms   536 ms  196.37.82.29
  4   423 ms   488 ms   549 ms  168.209.86.121
  5   426 ms   459 ms   449 ms  core2a-rba-gi4-0-0.rtr.isnet.net [196.26.0.8]
  6   726 ms   588 ms   570 ms  168.209.100.78
  7   467 ms   500 ms   479 ms  168.209.2.3
  8   615 ms   709 ms   730 ms  168.209.0.90
  9   787 ms   707 ms   870 ms  168.209.0.10
 10   970 ms   746 ms   759 ms  core1b-ny.nmszone.is.co.za [168.209.244.3]
 11   696 ms   759 ms  1029 ms  POS1-2.IG2.NYC4.ALTER.NET [208.192.177.205]
 12   730 ms   938 ms   710 ms  0.so-0-0-0.XL2.NYC4.ALTER.NET [152.63.18.66]
 13   748 ms   869 ms   799 ms  0.so-0-1-0.XL2.SFO4.ALTER.NET [152.63.50.162]
 14   924 ms   861 ms   777 ms  POS7-0.GW3.SFO4.ALTER.NET [152.63.51.125]
 15   775 ms   800 ms   879 ms  cnet-gw.customer.alter.net [157.130.196.186]
 16   849 ms   889 ms   849 ms  ge5-2.xch-sfo1-6506-1.cnet.com [216.239.127.22]

 17   726 ms   789 ms   800 ms  vlan509.xch-sfo1-6506-2.cnet.com [216.239.127.30
]
 18   749 ms   828 ms  1112 ms  ge5-2.att-sql1-6506-2.cnet.com [216.239.127.25]

 19   960 ms   799 ms   879 ms  c10-ssa-xw-lb.cnet.com [216.239.115.141]

Trace complete.