IBurst - Network News & Whispers 21st Jan

hArTh

Expert Member
Joined
Feb 13, 2004
Messages
1,114
hehe

Replace iBurst with Sentech and this is deja vu from 6 months ago ...

;)
 

LoneGunman

Expert Member
Joined
Sep 23, 2003
Messages
4,552
The biggest thing in users favour, is the fact that IBurst knows it MUST stabilize and make its network consistent - or else 99% of everyone who signed up on the 30 day notice contract, will simply walk away, chuck their modems in the cupboard, and spread the word that it sucks.

Unlike the months of patience that everyone gave Sentech at first - this time round IBurst I think is starting to become aware of the fact that they have very little 'wiggle room' before the word goes out, and they lose all the potential goodwill, customers and companies who'd otherwise use their service..

I think the folks experiencing serious disruption, need to speak directly to sassan/thami and bypass the help centre phone answerers, so that the top of the company get a firsthand taste of the sound of customers who are about to walk away.

Even though IBurst havent launched yet, and this is still early days - there's nothing more fun and educational than making direct contact with people who desperately want your money, and making them see that unless things improve, they aren't going to get it..

(Time wasted being patient with Sentech = 9 months
Time I'm willing to be patient with IBurst = not long at all..

I have Thami Mtshali's (IBurst Chief Operating Officer ) business card in front of me, with his cell phone number, direct number and email address.. it's only a matter of time before these and other numbers get posted, as a public service, to help IBurst's executives discover that this new generation of customers are not the passive consumers that Sentech has enjoyed abusing..

*makes Dr.Evil gesture*
 

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,710
While we are collecting business cards like we were back in school falling for the latest "collect one of these in each week's edition of ...", what points do we allocate to each card.

I am willing to virtually to trade Tseliso Phomane's (M.D.) card for ... what is your card worth in the bush?
 

native

Expert Member
Joined
Dec 30, 2004
Messages
1,527
I know this cause, when roodepoort = working the signal = 90% or higher.
When my signal drops to between 40% and 10% I am connected to Soweto'
Crash Soweto coverage doesnt reach Roodeport
 

guest2013-1

guest
Joined
Aug 22, 2003
Messages
19,808
LoneGunman said:
The biggest thing in users favour, is the fact that IBurst knows it MUST stabilize and make its network consistent - or else 99% of everyone who signed up on the 30 day notice contract, will simply walk away, chuck their modems in the cupboard, and spread the word that it sucks.

Unlike the months of patience that everyone gave Sentech at first - this time round IBurst I think is starting to become aware of the fact that they have very little 'wiggle room' before the word goes out, and they lose all the potential goodwill, customers and companies who'd otherwise use their service..

I think the folks experiencing serious disruption, need to speak directly to sassan/thami and bypass the help centre phone answerers, so that the top of the company get a firsthand taste of the sound of customers who are about to walk away.

Even though IBurst havent launched yet, and this is still early days - there's nothing more fun and educational than making direct contact with people who desperately want your money, and making them see that unless things improve, they aren't going to get it..

(Time wasted being patient with Sentech = 9 months
Time I'm willing to be patient with IBurst = not long at all..

I have Thami Mtshali's (IBurst Chief Operating Officer ) business card in front of me, with his cell phone number, direct number and email address.. it's only a matter of time before these and other numbers get posted, as a public service, to help IBurst's executives discover that this new generation of customers are not the passive consumers that Sentech has enjoyed abusing..

*makes Dr.Evil gesture*
Yep, the other day I had the CFO of the company call me to apologize and explain the billing issue they are having. And when I got my modem, because I had to wait for over 30 minutes at Security for clearance to take the damn thing out (SABC sucks) I heard there was quite a stir about it when I went back up to their offices to go fetch the clearance myself....

Now, LoneGunMan, you should be well aware how hard we struggled just to get Sentech to notice us, there I was, minding my own business waiting patiently for a security clearance, and they took it very seriously.

That is why I will give iburst the benefit of doubt, unlike Sentech who continiously screw it's customers....

BTW, I'm still waiting for these idiots to pick up their modem
 

LoneGunman

Expert Member
Joined
Sep 23, 2003
Messages
4,552
Yeah, I've also had Thami phone me in the past, which was kind've cool to have that sort of personal treatment from a company.. I'm willing to give IBurst a chance, dont get me wrong - but the first sign of Sentech-style treatment, I'm gone. I just think they need to be firmly reminded that they're consistently 30 days away from having no customers - in order to keep them friendly, obliging and providing the service we all want..

re the security clearance, I have an SABC security card so have walked straight into both the 15th & 21st floor offices a couple of times, and scared everyone by just 'appearing'.. :p

11.27pm friday - signal seems to have stopped 'dropping' - but the night aint over yet.
 
Last edited:

Ravilj

Well-Known Member
Joined
Jan 21, 2005
Messages
220
Well as I said I called uunet. The lady I spoke to wouldnt give me Luie (sp) mobile number so I asked her to leave a message for him with my details. Well I got a call from him, which I was well impressed about. So big up to that.

It seems there are two isolated problems here:
1. International bandwidth - This is an issue on uunet's side. You local bandwidth should be unaffected by this. So you should still have high local bandwidth.

2. Unkown Error with Basesatations - This is responsible for the low local and internation bandwidth even with 100% (high) signal strength. This is a WBS problem which they are addressing, the cause of the problem is unknown but they have flown in engineers from Japan to help solve the problem. This is only occuring on some of the towers, not all of them. I do know there are definately 3 towers experiencing this problem but I cant remember the exact ones :(.

So if you fall into category 1, be thankful because you should be up and running back to normal soon.

If you are in category 2, well like me we will have to be a bit more patient and hopefully things will be back to normal by halfway through next week.

I really think Iburst needs to look at being more informative with their customers instead of us having to track down the information. The support/call answers need to be given uptodate and detailed info on the problem so that customers feel a little more at ease with the problem rather than leaving us in the dark.

I do however have faith in iburst and wbs to get these problems sorted out, I think it must be noted that this is the pre-launch so they are trying to iron out any kinks and glitches in the system before it goes live. I suppose this is the price we pay for a non-capped 1Mb connection (when it works :/).
 

alchamy

Expert Member
Joined
Nov 14, 2004
Messages
1,636
OK Firstly, I am obviously in the same boat. Dont waste your time escalating to Dylan, he is not interested. Here is a section from a brief IRC chat with him earlier, after calling the helpdesk without any answers at the time.

[07:46pm] »» join14 sihen[wrk] (Dylan@ethereal.0x280dfc7d.0x58020ec1.0xba427bb1) [Unknown]
[07:46pm] »» op14 ChanServ ops sihen[wrk] in #iburst
[07:46pm] slimothy sihen
[07:46pm] slimothy iburst
[07:46pm] slimothy fix
[07:46pm] slimothy now
[07:46pm] slimothy kthx
[07:46pm] Ravilj sihen
[07:46pm] sihen[wrk] sorry bbl. im busy... putting in new pabx
[07:47pm] Ravilj and who's sorting out our connection?
[07:47pm] Alchamy sihen, downtime should be more important than the pabx
[07:48pm] • Alchamy copies and pastes
[07:49pm] slimothy hehehe
[07:49pm] slimothy customer shoudl always be right.. and if he isn't, we will phone wbs and act liek pricks
[07:49pm] sihen[wrk] Alchamy. i do not handle downtime, all i know if there is a problem on uunets side, luis is there looking into it.
[07:49pm] sihen[wrk] bbl.
[07:49pm] Alchamy sihen, fair enough. Any form of eta?
[07:49pm] Ravilj there has been a problem for the last week than!

This is unaccetable, sihen we get along fine but I am still your client and deserve information on the status of my connection. Being in charge of the helpdesk means that downtime is your problem, perhaps not to solve but definately to be aware of it and have eta for resolution. If an eta cannot be provided for any reason this should be explained. It is not sufficient to merely say "its being looked at" You are in charge of the helpdesk it is your responsibility to ensure that the information is available to callers. You should find out what is going on and ensure that the agents on duty convey that information to users.

The forum has been posting speed related issues/queries for over 2 weeks now. Yet they have not received any feedback. Now that things have gotten out of hand (even if UUNET is the culprit) suddenly its public knowledge that the experts are back in town. Should this not have been mentioned earlier. WBS is making a habit of leaving things until they explode. You need to be proactive in solving matters & relaying this feedback to users.

I could have let all this slide, however when I called the helpdesk I got the standard, "I will have to call you back" complained about this last week and still seems to be the norm. Its now after midnight and still no call. IE you & your helpdesk could not care to inform me of whats going on.

All Dylan needed to do was take 5 minutes of his time to say the following.

1. Unfortunately we are experiencing problems with UUNET
2. Luis is currently at their offices trying to find the root of the problem.
3. The last time I spoke to him was at *time* and he said *info*
4. Once again I apologize for the inconvience & assure you that we are doing our best to resolve the issue.

Instead I got, sorry I am too busy for a little user like you.

I have mailed Thami with regard to this evenings terrible service during the downtime.

This may seem like an over reaction, but it just been one issue after the other. If I keep quiet I will never get the service I pay for.
 

Mayh3m

Active Member
Joined
Dec 20, 2004
Messages
66
This evening (around 8pm) I had no signal whatsoever. Having heard the rumours about the Japanese technicians being here to sort problems out, I contacted the helpdesk to find out if this was was what was going on. Thato said that it was, and that they would be finished with the upgrade/repair later tonight.
I now check - I have signal, but it is way worse. Before UTD never dropped below 4 indicators. Now it seems to be sitting at 3 and going up to 4 occasionally.
This is the result of my bandwidth test:

MyADSL Local (South African) Speed Test


Your current bandwidth reading is:

20.70kbps

which means you can download at 2.59 KB/sec. from our servers.

20.7 kbps YOU
28.8 kbps dial-up
33.6 kbps dial-up
53.3 kbps dial-up
56 kbps ISDN
128 kbps ISDN
384 kbps DSL
768 kbps DSL
1000 kbps DSL
1500 kbps DSL/T1/Cable Modem

So as you can see - they have made some MAJOR improvements!!! PLEASE!!! This is ridiculous - where do I go from here? This is costing me a lot of time on telephone bills which is getting me nowhere, not to mention the taxing cost on my sanity which is wearing way thin.
 

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,710
Mayh3m welcome to my world for the past week - if this doesn't get fixed soon I be forced to call Tara & get a straight-jacket for myself.
 

ghoti

Karmic Sangoma
Joined
Jan 17, 2005
Messages
46,836
Broadband In Da South...Aaai!

Heya all, thought I wuld just drop a (so far) success story. About two weeks ago, my tower did the upidy downy thingy. I had the pcmcia card. It was really really really annoying.

I phoned constently (like every 30min), and bashed their orcs about a bit on the phone. I did this for the whole weekend. Man I must have been annoying.

Anyways I was informed by the narfs on chat that the pcmcia card is dodgy and underpowered. So on the monday, I swopped it for the desktop modem.

While waiting the pescribed 20 minutes in the "loungey" thing for them to swop out the modem, I heard some indian chap in a suit chatting to some boerewors oke about the number of subscribers. He mentioned 12 000 on iBursts network.

Anyways. I get home, plug in modem, and get speed results of 900kbs+, this was a week ago, and still going strong!!! Wooohooo, last night I got 941kbs. Screenshots on request :p

So yeah, things look like they have come right my side!
 

LoneGunman

Expert Member
Joined
Sep 23, 2003
Messages
4,552
----------------------->SATURDAY 22ND JAN 10.15AM

Luis is apparently on his way into the office, the long suffering Thato is on duty, and answering the phone slightly faster than yesterday - he seems to turn into an Orc after a few hundred angry customer calls, but for now he's responsive, at the start of his shift..
(The joys of the net also means we can do our best to not only keep tabs on the state of IBurst, but also the movements of IBursts one and only Jedi-Level Technician.

Getting irregular signal allowing for maybe 3 -5 k d.l (ie: Sentech's 'broadband' speeds)

Can anyone equal or better these amazingly fast ping results to IBurst? taken at 10.15am saturday. via Rosebank tower. Cant wait to do lots of first person gaming, with these low pings.

Pinging www.iburst.co.za [196.30.192.182] with 32 bytes of data:

Reply from 196.30.192.182: bytes=32 time=3407ms TTL=123
Reply from 196.30.192.182: bytes=32 time=2700ms TTL=123
Reply from 196.30.192.182: bytes=32 time=1811ms TTL=123
Request timed out.
Reply from 196.30.192.182: bytes=32 time=1796ms TTL=123
Request timed out.
Request timed out.
Request timed out.
Reply from 196.30.192.182: bytes=32 time=1420ms TTL=123
Reply from 196.30.192.182: bytes=32 time=3498ms TTL=123
Reply from 196.30.192.182: bytes=32 time=2762ms TTL=123
Reply from 196.30.192.182: bytes=32 time=1842ms TTL=123
Reply from 196.30.192.182: bytes=32 time=4342ms TTL=123
Request timed out.
Reply from 196.30.192.182: bytes=32 time=3968ms TTL=123
Request timed out.
Reply from 196.30.192.182: bytes=32 time=4171ms TTL=123
Request timed out.
Reply from 196.30.192.182: bytes=32 time=3561ms TTL=123
Reply from 196.30.192.182: bytes=32 time=4121ms TTL=123
Request timed out.
Reply from 196.30.192.182: bytes=32 time=2843ms TTL=123
Reply from 196.30.192.182: bytes=32 time=2232ms TTL=123
Reply from 196.30.192.182: bytes=32 time=3811ms TTL=123
Reply from 196.30.192.182: bytes=32 time=3889ms TTL=123

Ping statistics for 196.30.192.182:
Packets: Sent = 25, Received = 17, Lost = 8 (32% loss),
Approximate round trip times in milli-seconds:
Minimum = 1420ms, Maximum = 4342ms, Average = 3069ms
 

torgo

Senior Member
Joined
Jan 11, 2005
Messages
868
11am on 22 Jan:

Local:
Your current bandwidth reading is:

229.60kbps

which means you can download at 28.7 KB/sec. from our servers.

Internat:
TCP/Web100 Network Diagnostic Tool v5.2.1e
click START to begin
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 81.62Kb/s
running 10s inbound test (server to client) . . . . . . 180.34kb/s
Your PC is connected to a Cable/DSL modem

click START to re-test
 

ghostim

Expert Member
Joined
Dec 27, 2004
Messages
1,819
Reply from 196.30.31.100: bytes=32 time=1119ms TTL=255
Reply from 196.30.31.100: bytes=32 time=1344ms TTL=255
Reply from 196.30.31.100: bytes=32 time=2188ms TTL=255
Reply from 196.30.31.100: bytes=32 time=2444ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 196.30.31.100: bytes=32 time=2222ms TTL=255
Reply from 196.30.31.100: bytes=32 time=874ms TTL=255
Reply from 196.30.31.100: bytes=32 time=1412ms TTL=255
Reply from 196.30.31.100: bytes=32 time=1260ms TTL=255
Reply from 196.30.31.100: bytes=32 time=1518ms TTL=255
Reply from 196.30.31.100: bytes=32 time=2080ms TTL=255
Reply from 196.30.31.100: bytes=32 time=3668ms TTL=255
Reply from 196.30.31.100: bytes=32 time=2569ms TTL=255
Reply from 196.30.31.100: bytes=32 time=3391ms TTL=255
Reply from 196.30.31.100: bytes=32 time=3761ms TTL=255
Reply from 196.30.31.100: bytes=32 time=2521ms TTL=255
Reply from 196.30.31.100: bytes=32 time=2657ms TTL=255
Reply from 196.30.31.100: bytes=32 time=1455ms TTL=255
Reply from 196.30.31.100: bytes=32 time=1009ms TTL=255
Reply from 196.30.31.100: bytes=32 time=2531ms TTL=255
Reply from 196.30.31.100: bytes=32 time=976ms TTL=255

and i get a whopping 3 kbs download speed
 

Ravilj

Well-Known Member
Joined
Jan 21, 2005
Messages
220
ping www.iburst.co.za

Reply from 196.30.192.182: bytes=32 time=73ms TTL=123
Request timed out.
Reply from 196.30.192.182: bytes=32 time=1275ms TTL=123
Reply from 196.30.192.182: bytes=32 time=148ms TTL=123
Request timed out.
Reply from 196.30.192.182: bytes=32 time=1019ms TTL=123
Reply from 196.30.192.182: bytes=32 time=309ms TTL=123
Reply from 196.30.192.182: bytes=32 time=274ms TTL=123
:(
 
Last edited:

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,710
Yes, well I decided last night to put the ping thing into a .cmd file, so I have some summary results, there is no doubt that everytime I get a bunch of Request Timed out it is due to signal that has gone AWOL [obvious I know]. As you will see, things go from bad to worse, to better to worse again, and inbetween I have these lekker disconnections.
Code:
Ping statistics for 196.30.192.182:
    Packets: Sent = 5000, Received = 2033, Lost = 2967 (59% loss),
Approximate round trip times in milli-seconds:
    Minimum = 201ms, Maximum =  1493ms, Average =  288ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 5000, Received = 2569, Lost = 2431 (48% loss),
Approximate round trip times in milli-seconds:
    Minimum = 190ms, Maximum =  1472ms, Average =  358ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 5000, Received = 2085, Lost = 2915 (58% loss),
Approximate round trip times in milli-seconds:
    Minimum = 280ms, Maximum =  1472ms, Average =  282ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 5000, Received = 115, Lost = 4885 (97% loss),
Approximate round trip times in milli-seconds:
    Minimum = 270ms, Maximum =  1402ms, Average =  14ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 685, Lost = 315 (31% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  961ms, Average =  125ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 979, Lost = 21 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum =  1402ms, Average =  176ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 952, Lost = 48 (4% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1202ms, Average =  172ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 851, Lost = 149 (14% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1322ms, Average =  170ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 998, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1061ms, Average =  189ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 834, Lost = 166 (16% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1091ms, Average =  182ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 731, Received = 0, Lost = 731 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum =  0ms, Average =  0ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 899, Lost = 101 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1361ms, Average =  172ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 853, Lost = 147 (14% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1352ms, Average =  141ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 985, Lost = 15 (1% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum =  1362ms, Average =  158ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 878, Lost = 122 (12% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  972ms, Average =  156ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 969, Lost = 31 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1232ms, Average =  166ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 988, Lost = 12 (1% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1282ms, Average =  166ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 869, Lost = 131 (13% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1382ms, Average =  224ms
Just when I think things are getting better signal disappears altogether.
 

Ravilj

Well-Known Member
Joined
Jan 21, 2005
Messages
220
ic said:
Just when I think things are getting better signal disappears altogether.
Lol my thoughts exactly, just when things start looking up I loose all connectivity :/
 

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,710
Just a bit more to chew on:
Code:
Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 794, Lost = 206 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1422ms, Average =  217ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 883, Lost = 117 (11% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1463ms, Average =  215ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 813, Lost = 187 (18% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1302ms, Average =  176ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 801, Lost = 199 (19% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1412ms, Average =  185ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 847, Lost = 153 (15% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1382ms, Average =  173ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 902, Lost = 98 (9% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum =  1452ms, Average =  196ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 33, Lost = 967 (96% loss),
Approximate round trip times in milli-seconds:
    Minimum = 60ms, Maximum =  952ms, Average =  14ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 779, Lost = 221 (22% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  982ms, Average =  181ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 736, Lost = 264 (26% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  941ms, Average =  165ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 356, Lost = 644 (64% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum =  971ms, Average =  88ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 70, Lost = 930 (93% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  961ms, Average =  18ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 642, Lost = 358 (35% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum =  1202ms, Average =  158ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 505, Lost = 495 (49% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum =  1372ms, Average =  135ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 157, Lost = 843 (84% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  821ms, Average =  36ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 23, Lost = 977 (97% loss),
Approximate round trip times in milli-seconds:
    Minimum = 80ms, Maximum =  711ms, Average =  5ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 945, Lost = 55 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1402ms, Average =  185ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 567, Lost = 433 (43% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum =  1362ms, Average =  114ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 948, Lost = 52 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum =  1222ms, Average =  163ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 767, Lost = 233 (23% loss),
Approximate round trip times in milli-seconds:
    Minimum = 60ms, Maximum =  1392ms, Average =  314ms

Ping statistics for 196.30.192.182:
    Packets: Sent = 1000, Received = 545, Lost = 455 (45% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum =  1392ms, Average =  171ms
 
Top