Bite my ear!

[jmn]

When I'm being f%cked around, I prefer it with passion!

A serious case of premature cappulation!

According to my calculations I'm still about 100 MB away from being capped, the WBS site states 167 MB, but:

FTP transfer @ 800 Bps

Firefox can only open a page in one tab at a time...

http://www.telkom.co.za/minisites/dsl/speed1.html :
* Download time: 601.255 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 6.8 (kilobits/second)
* Estimated line speed: 0.8 (kiloBytes/second)

http://www.telkomsa.net/adsl/downloadTest.jsp :
* Download time: 598.601 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 6.8 (kilobits/second)
* Estimated line speed: 0.8 (kiloBytes/second)

 

[Darke]

Something is not right with Brynston, Kyalami and Olivedale BS's. Since UUNET had that international problem, I have experienced problems with IRC, high lag while browsing (refreshing) and especially with MSN. Below are pings of a NY site and WBS, normally I get a constant 40-80ms ping to WBS and a 300-320ms for NY, now it is irregular with masses of disconections, unknown host (DNS?), request timeouts.



Pinging 196.30.31.100 with 4 bytes of data:

Reply from 196.30.31.100: bytes=4 time=90ms TTL=255
Reply from 196.30.31.100: bytes=4 time=40ms TTL=255
Reply from 196.30.31.100: bytes=4 time=150ms TTL=255
Reply from 196.30.31.100: bytes=4 time=40ms TTL=255
Reply from 196.30.31.100: bytes=4 time=70ms TTL=255
Reply from 196.30.31.100: bytes=4 time=70ms TTL=255
Reply from 196.30.31.100: bytes=4 time=70ms TTL=255
Reply from 196.30.31.100: bytes=4 time=581ms TTL=255
Reply from 196.30.31.100: bytes=4 time=90ms TTL=255
Reply from 196.30.31.100: bytes=4 time=50ms TTL=255

Pinging wraith.tdzk.net [216.128.73.12] with 4 bytes of data:

Reply from 216.128.73.12: bytes=4 time=341ms TTL=51
Reply from 216.128.73.12: bytes=4 time=400ms TTL=51
Reply from 216.128.73.12: bytes=4 time=361ms TTL=51
Reply from 216.128.73.12: bytes=4 time=330ms TTL=51
Reply from 216.128.73.12: bytes=4 time=561ms TTL=51
Reply from 216.128.73.12: bytes=4 time=350ms TTL=51
Reply from 216.128.73.12: bytes=4 time=350ms TTL=51
Reply from 216.128.73.12: bytes=4 time=331ms TTL=51

 

[jmn]

I'm in Pretoria, pings are fine, even 1kB ones, early this morning everything seemed to be fine and degraded severely especially during the afternoon...

 

[nocilah]

Something is not right with Brynston, Kyalami and Olivedale BS's. Since UUNET had that international problem, I have experienced problems with IRC, high lag while browsing (refreshing) and especially with MSN. Below are pings of a NY site and WBS, normally I get a constant 40-80ms ping to WBS and a 300-320ms for NY, now it is irregular with masses of disconections, unknown host (DNS?), request timeouts.

i use kyalami and couldnt agree more with the uunet thing. ever since their mass outage about 3 weeks ago the tower has been dropping, latency is high and throuput up and down.

tonight kyalami died for about 10 minutes and came back up but with pretty much the same results. my local is good, but international is sad.

i wrote to a techie because helpdesk are utterly useless. this was the reply about the probelms mentioned by darke and myself:

There were some issues on international peering experienced over the last two weeks, on about three occasions, by two of our upstream providers. These were reported at http://www.iburst.co.za/networkstatus2.php. There was a minor international outage on 20/6/2005. However, this lasted only 5 minutes and was not reported on the incidents page.

they think everything is fine and dandy.

 

[Darke]

they think everything is fine and dandy.

I got that tonight from Helpdesk, "We have no problems, it is stable, have you reset your PC, Modem, checked your ...." until I said I am not an idiot (debatable), with the obligatory explanation of WHY and what evidence I had as to why I am not an idiot, then I got that the towers (3 above) had "some" problems and were being worked on.

 

[ic]

"Bite my ear!"?...well I've decided to allow TelkoDemonopoly into my bed, to WBS I say "pull my finger"...

 

[TheRoDent]

Sentech helpdesk excuse number 21:
"There is no problem with the network -
and you are the only caller who has a problem on your Tower."

Starting to sound extremely familiar.

 

[seburn]

Yes very familiar apparently I am one of 5 customers with disconnection problems