Telkom International slow

[Xman]

However, the slow international access should have been resolved (international seems adequate from our test ADSL line in the office).

Unfortunately not! 164 B/s

So, thats my Friday wasted. At least I could read something about Lesbians...

 

[wizard70]

Well my international on a 4 meg line is almost non existent. Test conducted on 01 February 2013 04:14:05 PM

Download Speed: 150 kbps (18.8 KB/sec transfer rate)

Upload Speed: 190 kbps (23.8 KB/sec transfer rate)

Latency: 233 ms

That was after waiting 10 minutes for the test to even start.


I just cannot use it at this time. I cannot sit for 10mins and wait for the server to respond in London. I hope this is resolved asap I cannot work like this until Sunday.

Timed this one took 6 minutes to start the actual download test.

Test conducted on 01 February 2013 04:47:03 PM

Download Speed: 141 kbps (17.6 KB/sec transfer rate)

Upload Speed: 198 kbps (24.8 KB/sec transfer rate)

Latency: 238 ms

 

[Paragon]

Confirmed, still incredibly slow. Unusable atm

 

[MickZA]

Confirmed, still incredibly slow. Unusable atm

Strange my capped accounts have been fine since mid-day, torrents & http downloads performing normally as I type.

 

[borro]

Eish, glad I'm not the only one, such crap speeds today:
0,12 kbps up / 0, 11 kbps down ??? ( sloooooow)

 

[Yuu]

Thanks as always for the feedback ranger .

 

[steel_dog]

Absolutely crazy
First my line was dog slow from the 3rd January... International was a consistent 0.5mbps.
Well now it's... non-existent... and neither is local (which used to be 3.5mbps).

Local: 0.1mbps / 0.41mpbs
Intl: can't do a speedtest. last attempt was 30kbps!

@Ranger: Dude please help. PM'd you regarding my original thread re slow international a week ago. Everything is gone to **** now

Here's my traceroute to www.google.co.za
Makes for interesting reading :erm:

Tracing route to www.google.co.za [173.194.41.159]
over a maximum of 30 hops:

  1     4 ms     2 ms     1 ms  192.168.0.1
  2   139 ms    11 ms    13 ms  224-136-1.dsl.subscriber.telkomsa.net [105.224.136.1]
  3   572 ms   132 ms   155 ms  226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6]
  4   324 ms    12 ms    20 ms  226-0-13.dsl.subscriber.telkomsa.net [105.226.0.13]
  5   446 ms   747 ms     *     wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
  6   518 ms   206 ms   300 ms  lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.46]
  7     *      171 ms   202 ms  196.25.191.146
  8  3204 ms     *        *     209.85.240.61
  9     *      189 ms   158 ms  72.14.238.55
 10   709 ms   611 ms   311 ms  lhr08s03-in-f31.1e100.net [173.194.41.159]

Trace complete.

... and a minute later better and it goes on like this...

Tracing route to www.google.co.za [173.194.41.159]
over a maximum of 30 hops:

  1     1 ms     1 ms     5 ms  192.168.0.1
  2   320 ms    12 ms    10 ms  224-136-1.dsl.subscriber.telkomsa.net [105.224.136.1]
  3    15 ms    12 ms   122 ms  226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6]
  4    13 ms    12 ms    12 ms  226-0-13.dsl.subscriber.telkomsa.net [105.226.0.13]
  5    21 ms    14 ms     *     wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
  6   198 ms   156 ms   156 ms  lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.46]
  7   156 ms   156 ms   157 ms  196.25.191.146
  8   404 ms     *      171 ms  209.85.240.61
  9   160 ms   158 ms   156 ms  72.14.238.55
 10   159 ms   158 ms   157 ms  lhr08s03-in-f31.1e100.net [173.194.41.159]

Trace complete.

 

[peter460332]

Absolutely ridiculous 5 kb/sec to Astraweb now at 22:00 and thats with telkom Uncapped - sucks

 

[Deckert]

Phew!

Janee, slow as molasses on a cold winter day. Local speeds are fine (and run normally), but access to international sites is crawling. This goes for all traffic types, SSH, FTP, HTTP, etc. I also note that this happened at around 10am this morning when I got an IP in a brand new IP range:

inetnum: 105.224.0.0 - 105.227.255.255
netname: Telkom-Internet

--deckert

 

[The Rookie]

Hi,

also experiencing such terrible connectivity.
I've never had it in all the years which I've been with Telkom.

But it's times like these when I am greatful I have an Afrihost account as a backup.

 

[ichigo]

Also slow browsing here today and never had a problem with my browsing for years with Telkom

 

[SaiyanZ]

Extremely slow international connection here. Pages load slow or sometimes not at all. Local is fine. I'm on 8ta but it seems like the problems are linked because of the same backbone.

First time my 8ta 3G is this bad.

 

[Brawler]

Terrible here to. Switched to afrihost account

 

[RichardG]

Same here on 8ta network and can feel that their are tethering hiccup problems at the moment. Whereby some pages loads, other pages don't load at all. Also experienced the same problem visiting mybroadband just a short while ago. I am assuming they working on peering with partners and can only do the updates during late evenings/early hours of the morning. Hopefully this has something to do with undersea cables... I am not sure if SAIX has peering agreements locally or if traffic is diverted internationally that's why I am experiencing no throughput or the title of the website will show but no content being loaded.

 

[ranger]

We are aware of congestion on a peering link from the London PoP to packetexchange.

We have escalated this.

However, it should have been possible for any of you affected users to report this (along with a traeceroute), so technical support could have logged an FQ while we were getting a bit of sleep.

 

[RichardG]

Awesome to know more and more undersea cables are heading to South Africa. www.cablemap.info

Things are once again operational. If this persist then what's the use to offer uncapped internet if they don't have enough infrastructure unless they lightning up the cable more, more, for traffic.

 

[ranger]

Should be better now:

 

[ranger]

Awesome to know more and more undersea cables are heading to South Africa. www.cablemap.info

Things are once again operational. If this persist then what's the use to offer uncapped internet if they don't have enough infrastructure unless they lightning up the cable more, more, for traffic.

The issue from 16h00 to now was not cable capacity, but capacity of a peering link between the London PoP and (I believe) a transit provider.

 

[MickeyD]

tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 10 ms 10 ms dsl-145-0-01.telkomadsl.co.za [41.145.0.1]
3 10 ms 10 ms 10 ms 196.43.21.158
4 * * * Request timed out.
5 55 ms 55 ms 54 ms 196.43.10.130
6 55 ms 54 ms 53 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za [196.43.33.5]
7 223 ms 223 ms 223 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.46]
8 248 ms 248 ms 250 ms 93-126-245-83.packetexchange.net [83.245.126.93]
9 * * * Request timed out.
10 243 ms 242 ms 242 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
11 250 ms 249 ms 248 ms 132.185.255.60
12 247 ms 247 ms 247 ms virtual-vip.thdo.bbc.co.uk [212.58.241.131]

Trace complete.

 

[ranger]

tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 10 ms 10 ms dsl-145-0-01.telkomadsl.co.za [41.145.0.1]
3 10 ms 10 ms 10 ms 196.43.21.158
4 * * * Request timed out.
5 55 ms 55 ms 54 ms 196.43.10.130
6 55 ms 54 ms 53 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za [196.43.33.5]
7 223 ms 223 ms 223 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.46]
8 248 ms 248 ms 250 ms 93-126-245-83.packetexchange.net [83.245.126.93]
9 * * * Request timed out.
10 243 ms 242 ms 242 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
11 250 ms 249 ms 248 ms 132.185.255.60
12 247 ms 247 ms 247 ms virtual-vip.thdo.bbc.co.uk [212.58.241.131]

Trace complete.

Before the routing change that occurred just after 02h00 (sorry for having to wake you Pieter ...), there was about 120-180ms latency between hop 7 and 8 in your trace above, which is now down to 24ms.