UUNet uncapped worst ADSL ever?

Anyway, just to illustrate, if you look at UUNet's ping times now during the weekend they are brilliant, sub 100ms (60ms average) to MWeb and about 360ms to World of Warcraft in the US. It's not like UUNet's network is incapable of extremely good performance, it's however to do with the amount of workload the network is under, which kinda tells me that if they can get this bandwidth to the BRAS installed it'll go a long way to alleviating these problems.
 
Tharaxis, surely if UUNET has its own network - and is not run on the Telkom/SAIX network...how can you blame Telkom for not carrying out the upgrades?
 
Well, If Telkom weren't the only fixed line provider, then you could probably connect to UUNET directly. I.E UUNET as a vans would run their own Copper.
As Telkom is the only fixed line provider, they dictate to everyone else how it works (The SNO is still hidden under a rock at the mo so ignore them).

It is very.... short sighted of ICASA, Government and every other tard, to let Telkom screw IS, UUNET and everyone else by being hard line on the Peering Link Upgrades. At the end of the day it Just makes everyone hate the big bad 900 pound gorilla.

Telkom is being very anti-competive about it.
 
"Last time i checked the UUNET datacentre in Cape Town, the only had a 5Mb/s line for all ADSL accounts. With all the sign-ups, this is obviously getting overloaded.."

K, where did you thumb suck that from?
The datacentre is in Johannesburg, my Boss was standing in it Yesterday.
And they have 3, yes 3, 155mbps ATM links. And there international bandwidth is a bit more the 5 Mb.
Click to expand...

UUNET have datacentres in both Cape Town and Johanesburg, relax people. I think a few traceroutes should reveal whether they are peering in both or not, but I suspect that it is only in JHB. As far as I am aware their egineers are currently in JHB this weekend working on something with Telkom that was supposed to have happenned the previous weekend.

Finally I don't think they have officially launched the product, not from what their sales staff in CPT are saying.
 
It seems that things have been sorted out. Currently my pings are 30-40 locally and 300-350 internationally. I'm wondering if they finaly got around to upgrading the lines!
 
Dominic, UUNet may have their own network, but they had to buy that from Telkom, also, they have to rely on Telkom to perform any bandwidth upgrades to their network (additional cabling, etc.)... every ISP with their own network (national and International) has to do this, so they are very much being held up by Telkom.

For example, UUNet's connection to Miami Florida is through SAT-3, they can't lay their own cable to hit Miami, they have to go through what Telkom offers them.
 
Okay I switched to UUnet now and low and behold the pings are solid.. .but I have an issue... local pings are 280-284ms and international is 560-570... not it's all great that it's now stable... but the routing seems to be off. Here is a trace root:
Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 276 ms 276 ms 276 ms atm4-0-0sub106.gw11.jnb6.alter.net [196.7.196.21]
4 277 ms 276 ms 277 ms pos8-1-0.gw11.jnb6.alter.net [196.30.121.157]
5 277 ms 276 ms 277 ms ge0-0.br1.jnb6.alter.net [196.30.156.41]
6 279 ms 277 ms 278 ms other-side.atm6-0sub1.br1.jnb6.alter.net{196.31.39.53]
7 300 ms 300 ms 300 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
8 303 ms 302 ms 301 ms wblv-ip-www-1.telkom-ipnet.co.za [196.25.1.200]

Now to me those should all be Sub 50ms is there a routing issue you think for DBN? Time to call the UUnet guys and ask :)

Regards
Hellhound a.k.a Cerberus
Trace complete.
 
Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 3 ms <1 ms <1 ms 192.168.1.1
2 10 ms 9 ms 9 ms 196-47-3-1.access.uunet.co.za [196.47.3.1]
3 11 ms 10 ms 10 ms atm4-0-0sub106.gw11.jnb6.alter.net [196.7.196.21
]
4 11 ms 11 ms 11 ms pos8-1-0.gw11.jnb6.alter.net [196.30.121.157]
5 13 ms 12 ms 11 ms ge0-0.br1.jnb6.alter.net [196.30.156.41]
6 13 ms 13 ms 13 ms other-side.atm6-0sub1.br1.jnb6.alter.net [196.31
.39.53]
7 35 ms 36 ms 35 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
8 38 ms 37 ms 36 ms wblv-ip-www-1.telkom-ipnet.co.za [196.25.1.200]


Trace complete.
===========================

International
===========================
Tracing route to www.google.akadns.net [64.233.161.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 10 ms 196-47-3-1.access.uunet.co.za [196.47.3.1]
3 11 ms 11 ms 11 ms atm4-0-0sub106.gw11.jnb6.alter.net [196.7.196.21
]
4 11 ms 11 ms 11 ms pos8-1-0.gw11.jnb6.alter.net [196.30.121.157]
5 10 ms 11 ms 11 ms fe4-1-0.cr2.jnb6.alter.net [196.30.156.34]
6 296 ms 301 ms 301 ms Serial5-0-1.GW3.LND10.Alter.NET [146.188.5.217]

7 302 ms 298 ms 320 ms ge5-0.cr2.lnd10.gbb.uk.uu.net [158.43.150.33]
8 304 ms 296 ms 299 ms sc-7-0-0.xr2.lnd9.alter.net [158.43.150.102]
9 299 ms 299 ms 298 ms so-1-1-0.TR1.LND9.ALTER.NET [146.188.15.37]
10 * * * Request timed out.
11 291 ms 294 ms 290 ms so-2-2-0.LONCR1.re.OPENTRANSIT.NET [146.188.50.1
46]
12 292 ms 294 ms 292 ms So7-2-0.LONCR1.London.opentransit.net [193.251.2
40.9]
13 295 ms 292 ms 294 ms P12-0.LONCR3.London.opentransit.net [193.251.242
.169]
14 296 ms 297 ms 297 ms P3-0.NYKCR3.New-york.opentransit.net [193.251.24
3.21]
15 300 ms 301 ms 301 ms P7-0.NYKBB3.New-york.opentransit.net [193.251.24
1.242]
16 297 ms 298 ms 302 ms Google-US-Customers-4.GW.opentransit.net [193.25
1.250.26]
17 298 ms 303 ms 298 ms 64.233.175.106
18 306 ms 296 ms 299 ms 216.239.46.137
19 298 ms 300 ms 296 ms 216.239.47.149
20 301 ms 307 ms 297 ms 216.239.49.246
21 298 ms 299 ms 300 ms 64.233.161.104

Trace complete.


Mine seems fine
 
Are you in DBN area? I was thinking it was maybe the way the DBN line connects to their backbone that hasn't been set up correctly? Just a guess though :( but local pings are solid at 280-290ms and international is 560ms.Anyone else in DBN that can confirm this?

Hellhound a.k.a Cerberus
 
Some stats for Monday Morning, 8am.

Pinging www.unreal.co.za [196.7.147.24] with 32 bytes of data:

Reply from 196.7.147.24: bytes=32 time=40ms TTL=248
Reply from 196.7.147.24: bytes=32 time=39ms TTL=248
Reply from 196.7.147.24: bytes=32 time=38ms TTL=248
Reply from 196.7.147.24: bytes=32 time=39ms TTL=248
Reply from 196.7.147.24: bytes=32 time=38ms TTL=248
Reply from 196.7.147.24: bytes=32 time=38ms TTL=248
Reply from 196.7.147.24: bytes=32 time=38ms TTL=248
Reply from 196.7.147.24: bytes=32 time=40ms TTL=248
Reply from 196.7.147.24: bytes=32 time=40ms TTL=248
Reply from 196.7.147.24: bytes=32 time=37ms TTL=248
Reply from 196.7.147.24: bytes=32 time=37ms TTL=248
Reply from 196.7.147.24: bytes=32 time=39ms TTL=248
Reply from 196.7.147.24: bytes=32 time=38ms TTL=248
Reply from 196.7.147.24: bytes=32 time=37ms TTL=248
Reply from 196.7.147.24: bytes=32 time=37ms TTL=248
Reply from 196.7.147.24: bytes=32 time=39ms TTL=248
Reply from 196.7.147.24: bytes=32 time=40ms TTL=248
Reply from 196.7.147.24: bytes=32 time=37ms TTL=248
Reply from 196.7.147.24: bytes=32 time=39ms TTL=248
Reply from 196.7.147.24: bytes=32 time=37ms TTL=248

Ping statistics for 196.7.147.24:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 40ms, Average = 38ms

Pinging www.google.akadns.net [64.233.161.99] with 32 bytes of data:

Reply from 64.233.161.99: bytes=32 time=304ms TTL=238
Reply from 64.233.161.99: bytes=32 time=305ms TTL=238
Reply from 64.233.161.99: bytes=32 time=319ms TTL=238
Reply from 64.233.161.99: bytes=32 time=309ms TTL=238
Reply from 64.233.161.99: bytes=32 time=314ms TTL=238
Reply from 64.233.161.99: bytes=32 time=301ms TTL=238
Reply from 64.233.161.99: bytes=32 time=313ms TTL=238
Reply from 64.233.161.99: bytes=32 time=319ms TTL=238
Reply from 64.233.161.99: bytes=32 time=305ms TTL=238
Reply from 64.233.161.99: bytes=32 time=303ms TTL=238
Reply from 64.233.161.99: bytes=32 time=313ms TTL=238
Reply from 64.233.161.99: bytes=32 time=305ms TTL=238
Reply from 64.233.161.99: bytes=32 time=306ms TTL=238
Reply from 64.233.161.99: bytes=32 time=305ms TTL=238
Reply from 64.233.161.99: bytes=32 time=309ms TTL=238
Reply from 64.233.161.99: bytes=32 time=302ms TTL=238
Reply from 64.233.161.99: bytes=32 time=300ms TTL=238
Reply from 64.233.161.99: bytes=32 time=300ms TTL=238
Reply from 64.233.161.99: bytes=32 time=308ms TTL=238
Reply from 64.233.161.99: bytes=32 time=298ms TTL=238
Reply from 64.233.161.99: bytes=32 time=303ms TTL=238
Reply from 64.233.161.99: bytes=32 time=315ms TTL=238

Ping statistics for 64.233.161.99:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 298ms, Maximum = 319ms, Average = 307ms

Still seems very good, I did notice my line doing down twice for 30mins or so yesterday, so UUNET did do something!
 
And the other side of the world: Aus.
Code: 
Pinging [url]www.australia.com.ngrs.net[/url] [203.202.25.131] with 32 bytes of data:
Reply from 203.202.25.131: bytes=32 time=584ms TTL=108
Reply from 203.202.25.131: bytes=32 time=560ms TTL=108
Reply from 203.202.25.131: bytes=32 time=570ms TTL=108
Reply from 203.202.25.131: bytes=32 time=560ms TTL=108
Ping statistics for 203.202.25.131:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 560ms, Maximum = 584ms, Average = 568ms

Tracing route to [url]www.australia.com.ngrs.net[/url] [203.202.25.131] over a maximum of 30 hops:
  1     *        *        *     Request timed out.
  2    56 ms    59 ms    59 ms  atm4-0-0sub106.gw11.jnb6.alter.net [196.7.196.21]
  3    59 ms    59 ms    59 ms  pos8-1-0.gw11.jnb6.alter.net [196.30.121.157]
  4   310 ms   319 ms   309 ms  atm1-1-0sub902.ir2.mia16.alter.net [196.30.229.209]
  5   310 ms   309 ms   309 ms  POS0-1-0.IH4.MIA4.ALTER.NET [152.63.86.145]
  6   310 ms   309 ms   319 ms  202.at-5-1-0.XR2.MIA4.ALTER.NET [152.63.7.130]
  7   320 ms   319 ms   309 ms  0.so-4-2-0.XL2.MIA4.ALTER.NET [152.63.101.46]
  8   330 ms   319 ms   319 ms  0.so-4-2-0.XL2.ATL5.ALTER.NET [152.63.81.81]
  9   320 ms   319 ms   319 ms  0.so-7-0-0.BR3.ATL5.ALTER.NET [152.63.87.93]
 10   329 ms   329 ms   329 ms  so-1-1-0.gar2.Atlanta1.Level3.net [4.68.127.177]
 11   330 ms   319 ms   389 ms  so-3-3-0.bbr1.Atlanta1.Level3.net [4.68.96.13]
 12   400 ms   379 ms   379 ms  ae-0-0.bbr1.LosAngeles1.Level3.net [64.159.1.125]
 13   379 ms   380 ms   389 ms  so-0-0-0.gar2.LosAngeles1.Level3.net [4.68.96.82]
 14   410 ms   419 ms   400 ms  unknown.Level3.net [63.209.82.186]
 15   400 ms   429 ms   409 ms  laxeq-cr1.ge-3-0-0.ix.singtel.com [203.208.182.4
5]
 16   400 ms   409 ms   409 ms  so-1-1-0.plapx-cr2.ix.singtel.com [203.208.168.229]
 17   590 ms   580 ms   570 ms  203.208.148.58
 18   570 ms   570 ms   590 ms  ge3-1.52gdc76f02.optus.net.au [203.202.36.21]
 19   580 ms   570 ms   570 ms  203.202.25.131
Trace complete.
 
Last edited:
Unfortunately still no change this morning from DBN side I still get 280ms local and 569ms to google. Something fishy with the DBN line? I don't know the answer just asking the question, I'll talk to WebAfrica this morning and see if they can prod UUnet for me :)

Regards
Hellhound a.k.a Cerberus
 
And yet another side: Denmark
Code: 
Pinging bzflag0.gamesunited.de [212.6.108.237] with 32 bytes of data:
Reply from 212.6.108.237: bytes=32 time=450ms TTL=43
Reply from 212.6.108.237: bytes=32 time=440ms TTL=43
Reply from 212.6.108.237: bytes=32 time=460ms TTL=43
Reply from 212.6.108.237: bytes=32 time=460ms TTL=43
Ping statistics for 212.6.108.237:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 440ms, Maximum = 460ms, Average = 452ms
Code: 
Tracing route to bzflag0.gamesunited.de [212.6.108.237]
over a maximum of 30 hops:
  1     *        *        *     Request timed out.
  2    54 ms    59 ms    59 ms  atm4-0-0sub106.gw11.jnb6.alter.net [196.7.196.21]
  3    59 ms    59 ms    59 ms  pos8-1-0.gw11.jnb6.alter.net [196.30.121.157]
  4   330 ms   309 ms   309 ms  atm1-1-0sub902.ir2.mia16.alter.net [196.30.229.209]
  5   310 ms   319 ms   319 ms  POS0-1-0.IH4.MIA4.ALTER.NET [152.63.86.145]
  6   310 ms   309 ms   338 ms  202.at-6-1-0.XR2.MIA4.ALTER.NET [152.63.7.186]
  7   310 ms   319 ms   329 ms  0.so-4-2-0.XL2.MIA4.ALTER.NET [152.63.101.46]
  8   329 ms   329 ms   329 ms  0.so-4-2-0.XL2.ATL5.ALTER.NET [152.63.81.81]
  9   340 ms   329 ms   329 ms  0.so-7-0-0.BR3.ATL5.ALTER.NET [152.63.87.93]
 10   330 ms   329 ms   329 ms  so-1-1-0.gar2.Atlanta1.Level3.net [4.68.127.177]
 11   320 ms   329 ms   329 ms  so-3-3-0.bbr1.Atlanta1.Level3.net [4.68.96.13]
 12   359 ms   339 ms   339 ms  as-3-0.bbr2.Washington1.Level3.net [64.159.1.2]
 13   450 ms   419 ms   430 ms  as-0-0.bbr1.London2.Level3.net [4.68.128.101]
 14   410 ms   409 ms   419 ms  ae-1-0.bbr2.London1.Level3.net [212.187.128.57]
 15   420 ms   409 ms   410 ms  ge-10-0.ipcolo1.London1.Level3.net [212.187.131.7]
 16   430 ms   419 ms   429 ms  unknown.Level3.net [212.187.151.26]
 17   430 ms   439 ms   430 ms  bbrt.ol-1-so-0-0-0.ewe-ip-backbone.de [80.228.109.49]
 18   450 ms   449 ms   439 ms  212.6.108.237
Trace complete.
They don't have landing points in AU or DE anymore. Going through Atlanta. Sigh.
 
I second all of your stuff.
Have uncapped adsl uunet and its bad. The UUNET tech people know my voice already.
Claiming to be upgrading every day. Some one in the forum wrote that UUNET uncapped were unshaped WRONG, they shape it for business, thus meaning all port we like to use are shaped.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X