Assitance Needed re Current Service Levels

[regardtv]

Hi all iBursters

I'm having a go at iBurst for the current state of their network and need to know if I'm the only one currently experiencing the following...

Background ... can be ignored:
Since the storm on the 23rd I have had huge packet loss and pathetic service in general. I connect the the Randpark Ridge tower. I am continually told that I'm the only one having problems and I must check my firmware, MTU etc etc.

We all know the checks above are standard delay tactics since Ive had decent connectivity since the launch of the Randpark Ridge tower ... SO

The actual questions, please respond:
Is the service working WELL for you at the moment? If not, what is wrong and WHERE are you based?
Have you experienced any problems in the past 72 hours, if so what?

Please help me in this.

R

 

[regardtv]

Related threads:

http://myadsl.co.za/vb/showthread.php?t=32515

http://myadsl.co.za/vb/showthread.php?t=32550

http://myadsl.co.za/vb/showthread.php?t=32567

http://myadsl.co.za/vb/showthread.php?t=32533

 

[P0tenc]

I have had just over 15% downtime this month. 10% of that was "death by cap related".

For 2 weeks now latency has been all over the place with packet loss. but aspecially to the US. Local latency will come right some times and then get worse again.This is by far the worst month I have been on iBurst ever!

I wonder if the fact that one of their main administrators are on leave for health reasons have anything to do with the pathetic state the network is in this month.

 

[Glipsie]

Trying to download the new zonealarm. Currently going at 0.7Kb/s. Web sites seem to load fairly quickly, even though I'm supposedly capped. Disconnects every 30 mins or so. Unfortunately I can't say if this is just another Northcliff tower day or if its related to your situation

Cheers
Glipsie

 

[RVFmal]

According to iBurst there are no problems.

However it has taken over 3 hours to upload ClientExec's just over 9megs to my server (and there is still 1 meg to go), it took 3.5 minutes to open this page so that I could reply, it takes 6 minutes to download my mail (and that is without actually downloading anything - just checking)..........

Yep, there is no problem.

 

[regardtv]

I wonder if the fact that one of their main administrators are on leave for health reasons have anything to do with the pathetic state the network is in this month.

I have been wondering the same thing but have been repeatedly assured that there are many competent ppl in their technical team.......

I personally will be a happy man come next week when the "unnamed administrator" (hehe) returns...

IMO He's the 1 aspect of WBS that does not leave a bitter taste.

 

[Thorin]

I'm on the RandParkridge tower and yesterday was almost imposible to do anything. Extreemly high packet loss / disconnects all the time etc. Prior to 24th, everything was really good!

I'm currently connected from work so I don't know if they have now fixed the problem. I sure hope so!

 

[noemfie]

This month have been good for me , apart form the last 3 days when towers went down for a few hours at a time , I cannot comment on day time performance , but at night I was flying , local latency also seemed fine .

I'm on the Centurion Tower


The problem I had with WBS is that their towers go down , and they just keep quite about it till its back up hoping no one will notice

 

[ClockworkOrange]

Just to recap again from my other thread:

I'm 300m away from Olivedale tower, direct LOS, always have 5 LEDs on.

Since the evening of 23rd the service was practically unusable. Huge packet loss, terrible latency with ping timeouts every 5-6 pings, both local and internation browsing are practically useless. Download speeds are between 0.5 and 4 kbytes/s

 

[Kei]

I do not have any problems. The last time I had problems with iBurst was 2-3 months ago.

The thing falls over with the bad weather sometimes yes. Yesterday I had to restart the UTD and it came right, I am not surprised, the lightning was terrible yesterday. I am sure the UTD hung up or something.

My service is slowly improving...

 

[regardtv]

Clockwork ... we were on the "downed" towers mentioned on their status support page... just sad that those same towers are one again down ...

 

[ClockworkOrange]

Well, the connectivity is back up now. The latency had improved to previous levels - 62-75ms, but still getting very frequent ping timeouts.

It's somewhat better, but still not as good as it were before the 23rd.

 

[Roman4604]

It's somewhat better, but still not as good as it were before the 23rd.

Ya not as bad as at its worst (i.e. < 64kbps), but nowhere near what it should be. Getting ave. ~200 Kbps while my norm is usually 800-1024kbps

BTW on Kyalami

 

[GRES]

Packet loss with Randpark (2km only!!!) and full speed with Roodeport (9,5km)!

 

[Mercury]

Here is my usual package of international, local and WBS ping tests plus the Telkom speed test, repeated three times at different times today.

----83.138.189.100 PING Statistics----
66 packets transmitted, 51 packets received, 22% packet loss
round-trip (ms) min/avg/max = 300/453/920

----196.4.160.2 PING Statistics----
66 packets transmitted, 54 packets received, 18% packet loss
round-trip (ms) min/avg/max = 50/88/240

----196.30.31.120 PING Statistics----
66 packets transmitted, 47 packets received, 28% packet loss
round-trip (ms) min/avg/max = 50/79/190

Download time: 126.378 seconds
Size of file: 500 KiloBytes
Estimated line speed: 32.3 (kilobits/second)
Estimated line speed: 4 (kiloBytes/second)

----83.138.189.100 PING Statistics----
66 packets transmitted, 46 packets received, 30% packet loss
round-trip (ms) min/avg/max = 310/346/470

----196.4.160.2 PING Statistics----
66 packets transmitted, 55 packets received, 16% packet loss
round-trip (ms) min/avg/max = 50/96/200

----196.30.31.120 PING Statistics----
66 packets transmitted, 60 packets received, 9% packet loss
round-trip (ms) min/avg/max = 40/87/360

Download time: 11.171 seconds
Size of file: 500 KiloBytes
Estimated line speed: 365.2 (kilobits/second)
Estimated line speed: 44.8 (kiloBytes/second)

----83.138.189.100 PING Statistics----
66 packets transmitted, 18 packets received, 72% packet loss
round-trip (ms) min/avg/max = 330/350/400

----196.4.160.2 PING Statistics----
66 packets transmitted, 46 packets received, 30% packet loss
round-trip (ms) min/avg/max = 40/92/290

----196.30.31.120 PING Statistics----
66 packets transmitted, 45 packets received, 31% packet loss
round-trip (ms) min/avg/max = 50/74/150

Download time: 18.977 seconds
Size of file: 500 KiloBytes
Estimated line speed: 215 (kilobits/second)
Estimated line speed: 26.3 (kiloBytes/second)

 

[Roman4604]

Packet loss with Randpark (2km only!!!) and full speed with Roodeport (9,5km)!

GRES any chance you can do a traceroute to say ftp.uunet.co.za from each of the towers. Here is mine from Kyalami ...

C:\>tracert ftp.uunet.co.za

Tracing route to ftp.uunet.co.za [196.7.0.133]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.88.1
2 84 ms 47 ms 45 ms wbs-196-2-100-1.wbs.co.za [196.2.100.1]
3 * 75 ms 48 ms 192.168.0.97
4 135 ms 45 ms 51 ms ge0-2.gw10.jnb6.alter.net [66.8.42.21]
5 110 ms 73 ms * srp1-0-0.gw3.cpt1.alter.net [196.31.249.71]
6 100 ms 118 ms 76 ms prism.ops.uunet.co.za [196.7.0.133]

Trace complete.

The LNS Router (ppp termination) has changed again to 196.2.100.1. Before these problems it was 196.2.97.1 (and before that 196.30.31.100).

Am trying to figure out if WBS just keep reinstalling/moving the routers for fun, or are they routing different towers to different routers in times of failure.

Note: still getting sporadic packet loss

 

[Unchained]

From Wonderboom, Pta (if this helps, I've been connected for 2d 20h 55m 5s so it might have changed):

Get continuous timeouts from prism.ops.uunet.co.za via iBurst, fine from dialup.

traceroute to ftp.uunet.co.za (196.7.0.133), 30 hops max, 38 byte packets
1 192.168.0.4 (192.168.0.4) 0.703 ms 0.460 ms 0.465 ms
2 wbs-196-2-120-1.wbs.co.za (196.2.120.1) 137.502 ms 108.740 ms 46.377 ms
3 192.168.0.97 (192.168.0.97) 43.602 ms 52.852 ms 41.349 ms
4 ge0-2.gw10.jnb6.alter.net (66.8.42.21) 200.766 ms 93.240 ms 145.955 ms
5 srp1-0-0.gw3.cpt1.alter.net (196.31.249.71) 129.463 ms 73.739 ms 74.925 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
...I

 

[P0tenc]

Tracing route to ftp.uunet.co.za [196.7.0.133]
over a maximum of 30 hops:

1 124 ms 55 ms 54 ms wbs-196-2-120-1.wbs.co.za [196.2.120.1]
2 142 ms 80 ms 48 ms 192.168.0.97
3 66 ms 106 ms 55 ms ge0-2.gw10.jnb6.alter.net [66.8.42.21]
4 104 ms 75 ms 77 ms srp1-0-0.gw3.cpt1.alter.net [196.31.249.71]
5 180 ms 176 ms 164 ms prism.ops.uunet.co.za [196.7.0.133]

 

[regardtv]

Guys... our traceroutes would be basically the same since we all get terminated at an LNS server inside the Gallo Manor PoP. The link errors happen "out of band" between towers.

====

By getting some decent feedback it seems that a backhaul on one of their primary towers (bryanston) is repeatedly running errors. Shortly after being fixed the errors have returned.

The backup/redundant links are also running errors.

I find it truly unacceptable that iBurst has not released an official statement concerning this.

I have now opened a ticket with their accounts department for a refund due to the pathetic service this month ... I suggest you ALL do the same... Ticket has been open for 24 hours without even a basic response.

The only way they'll get moving is when they see an impact with tickets and public perception.

 

[8321]

Menlo Park Pretoria down again

Blackout in Menlo Park (CSIR) for at least 3 hours this afternoon. Anyone with precise start/end times?

No incident report.