UUNet: Whats going on?

stoke said:
So - what u're all saying is so-far so good with UUNet ?
i.e. Initial hiccups are gone and all is good ?
Click to expand...
I only started with UUnet at the beginning of the month and I have to admit that in the beginning I had some doubt whether or not I had gone the right route for me. However, speeds have since picked up in pretty much every area. There is still some room for improvement but I’m happy for now.

They’ll get another month of my business.
 
bwana said:
I installed BWmeter on ONE of the machines behind my router on the 7th of this month. Today an alert I had set popped up on the screen - Total traffic to date - 30.2gb. No more doubts in my mind what was the right choice for ME.
Click to expand...

same applies to me...!!!
 
I dont mind an hiccup once a week, 4 times a month.. as long as it gets fixed.

All over its a great package.
 
Since the upgrades seem to have affected only locally can Stoke, Celemasiko [1 of you] ping these addresses.

karoo.mweb.co.za

games.saix.net

thx ;)
 
Doesn't look too good....

Pinging games.saix.net [196.4.79.14] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 196.4.79.14:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=360ms TTL=115
Reply from 196.2.128.100: bytes=32 time=424ms TTL=115
Reply from 196.2.128.100: bytes=32 time=400ms TTL=115
Reply from 196.2.128.100: bytes=32 time=375ms TTL=115

Ping statistics for 196.2.128.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 360ms, Maximum = 424ms, Average = 389ms
 
That is bad - real bad...I'm shocked at how high local pings are. Oh well I better wait for them to do some upgrades until I part with some money with them.
 
it has a little bit improved this morning, but not on the saix...

Pinging games.saix.net [196.4.79.14] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 196.4.79.14:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=86ms TTL=115
Reply from 196.2.128.100: bytes=32 time=83ms TTL=115
Reply from 196.2.128.100: bytes=32 time=103ms TTL=115
Reply from 196.2.128.100: bytes=32 time=131ms TTL=115

Ping statistics for 196.2.128.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 131ms, Average = 100ms
 
games.saix.net does not return ICMP packets.
use www.saix.co.za.
This is AYCE ... (08H41 on a saturday morning)
Pinging www.saix.co.za [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=36ms TTL=249
Reply from 196.25.1.200: bytes=32 time=36ms TTL=249
Reply from 196.25.1.200: bytes=32 time=37ms TTL=249
Reply from 196.25.1.200: bytes=32 time=37ms TTL=249
Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 37ms, Average = 36ms

and karoo.mweb.co.za

Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:
Reply from 196.2.128.100: bytes=32 time=37ms TTL=117
Reply from 196.2.128.100: bytes=32 time=38ms TTL=117
Reply from 196.2.128.100: bytes=32 time=38ms TTL=117
Reply from 196.2.128.100: bytes=32 time=38ms TTL=117
Ping statistics for 196.2.128.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 38ms, Average = 37ms
 
ok, here it is...

Pinging saix.co.za [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=68ms TTL=245
Reply from 196.25.1.200: bytes=32 time=60ms TTL=245
Reply from 196.25.1.200: bytes=32 time=71ms TTL=245
Reply from 196.25.1.200: bytes=32 time=58ms TTL=245

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 71ms, Average = 64ms


Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=55ms TTL=115
Reply from 196.2.128.100: bytes=32 time=86ms TTL=115
Reply from 196.2.128.100: bytes=32 time=57ms TTL=115
Reply from 196.2.128.100: bytes=32 time=124ms TTL=115

Ping statistics for 196.2.128.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 124ms, Average = 80ms
 
no problerm, I just pinged two internationals...


Pinging google.com [216.239.57.99] with 32 bytes of data:

Reply from 216.239.57.99: bytes=32 time=564ms TTL=237
Reply from 216.239.57.99: bytes=32 time=499ms TTL=237
Reply from 216.239.57.99: bytes=32 time=571ms TTL=237
Reply from 216.239.57.99: bytes=32 time=537ms TTL=237

Ping statistics for 216.239.57.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 499ms, Maximum = 571ms, Average = 542ms


Pinging rtl.de [81.173.245.18] with 32 bytes of data:

Reply from 81.173.245.18: bytes=32 time=566ms TTL=41
Reply from 81.173.245.18: bytes=32 time=637ms TTL=41
Reply from 81.173.245.18: bytes=32 time=632ms TTL=41
Reply from 81.173.245.18: bytes=32 time=439ms TTL=41

Ping statistics for 81.173.245.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 439ms, Maximum = 637ms, Average = 568ms
 
AYCE-Pinging google.com [216.239.37.99] with 32 bytes of data:
Reply from 216.239.37.99: bytes=32 time=337ms TTL=240
Reply from 216.239.37.99: bytes=32 time=338ms TTL=240
Reply from 216.239.37.99: bytes=32 time=339ms TTL=240
Reply from 216.239.37.99: bytes=32 time=340ms TTL=240
Ping statistics for 216.239.37.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 337ms, Maximum = 340ms, Average = 338ms

AYCE-Pinging rtl.de [81.173.245.18] with 32 bytes of data:
Reply from 81.173.245.18: bytes=32 time=487ms TTL=48
Reply from 81.173.245.18: bytes=32 time=487ms TTL=48
Reply from 81.173.245.18: bytes=32 time=488ms TTL=48
Reply from 81.173.245.18: bytes=32 time=488ms TTL=48
Ping statistics for 81.173.245.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 487ms, Maximum = 488ms, Average = 487ms

Sheesh - unbelievable - when I first got UUNET - their pings to bzflag0.gamesunited.de were sub 270ms, now look where they r. *CRY*.
<EDIT>Spoze thats why i stopped using them - but they have the potential to be back up there.
 
Celemasiko said:
they willl upgrade according to my reseller this morning...
Click to expand...
Not intening to be obtuse but do you mean they're doing the upgrading this morning or that you learnt this morning about a upgrade to be done at some yet-to-be-determined time? Either way improvements to any service are always welcomed here :o
 
Last edited:
Well, they've been upgrading for the last month - I'm primarily going to use this for gaming but I'm willing to give them a chance.

At least the local pings look quite good.
 
improvement of international pings according to yesterday...


Pinging google.com [216.239.39.99] with 32 bytes of data:

Reply from 216.239.39.99: bytes=32 time=353ms TTL=238
Reply from 216.239.39.99: bytes=32 time=313ms TTL=238
Reply from 216.239.39.99: bytes=32 time=379ms TTL=238
Reply from 216.239.39.99: bytes=32 time=372ms TTL=238

Ping statistics for 216.239.39.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 313ms, Maximum = 379ms, Average = 354ms

Pinging rtl.de [81.173.245.18] with 32 bytes of data:

Reply from 81.173.245.18: bytes=32 time=331ms TTL=41
Reply from 81.173.245.18: bytes=32 time=350ms TTL=41
Reply from 81.173.245.18: bytes=32 time=365ms TTL=41
Reply from 81.173.245.18: bytes=32 time=379ms TTL=41

Ping statistics for 81.173.245.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 331ms, Maximum = 379ms, Average = 356ms
 
Last edited:
UUNET pings have improuved....national and international


Pinging saix.co.za [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=55ms TTL=245
Reply from 196.25.1.200: bytes=32 time=62ms TTL=245
Reply from 196.25.1.200: bytes=32 time=55ms TTL=245
Reply from 196.25.1.200: bytes=32 time=55ms TTL=245

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 62ms, Average = 56ms


Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=74ms TTL=115
Reply from 196.2.128.100: bytes=32 time=62ms TTL=115
Reply from 196.2.128.100: bytes=32 time=59ms TTL=115
Reply from 196.2.128.100: bytes=32 time=70ms TTL=115

Ping statistics for 196.2.128.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 74ms, Average = 66ms


Pinging google.com [216.239.37.99] with 32 bytes of data:

Reply from 216.239.37.99: bytes=32 time=309ms TTL=237
Reply from 216.239.37.99: bytes=32 time=308ms TTL=237
Reply from 216.239.37.99: bytes=32 time=311ms TTL=237
Reply from 216.239.37.99: bytes=32 time=337ms TTL=237

Ping statistics for 216.239.37.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 308ms, Maximum = 337ms, Average = 316ms


Pinging rtl.de [81.173.245.18] with 32 bytes of data:

Reply from 81.173.245.18: bytes=32 time=316ms TTL=41
Reply from 81.173.245.18: bytes=32 time=334ms TTL=41
Reply from 81.173.245.18: bytes=32 time=330ms TTL=41
Reply from 81.173.245.18: bytes=32 time=317ms TTL=41

Ping statistics for 81.173.245.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 316ms, Maximum = 334ms, Average = 324ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X