Maintenance 20/4

[BigAl-sa]

By accident I found out from the incident report (strange place to put it) that they're going to be doing core maintenance at midnite tonite...

 

[Ekhaatvensters]

Aah, thats when I use my internet, is it affecting the whole network? Not just JHB or CPT?

EDIT: Not sure why I'm being lazy and asking, it affects all iBurst subscribers and should last two hours, which means it will be down until Sunday.

 

[native]

, which means it will be down until Sunday.

WOW - have the whole network ever being down for more than a day?

 

[who.is.michael]

For the past three f***ing weeks in Cape Town...

 

[stoke]

I did not get a notification.
They do have my email address.

Are they to damn lazy to send out a notification?

Service levels of suxxorz!

Thanks for the warning BigAl-sa, I hope they're paying you well for this service.

 

[Ekhaatvensters]

Um.. I was joking about until Sunday.. its two hours, it should only last until 2am Saturday. Its just that they usually get their estimated resolution times pretty off, but with maintenance this should be fine.

 

[fishfly]

man iburst is full of ****... they just do maintainance and tell the people to check the status report... half the time that stupid report is never updated in time for their MAINTAINANCE! WTF

 

[MrH]

As long as their maintenance does not change whatever they did to get the CT network as it is now since this is the best it's been for ages.

So iBurst, LEAVE CT network alone and don't fiddle as you'll only screw it up again.

 

[Ekhaatvensters]

As long as their maintenance does not change whatever they did to get the CT network as it is now since this is the best it's been for ages.

So iBurst, LEAVE CT network alone and don't fiddle as you'll only screw it up again.

Is that the iBurst you know and love?

Of course they'll change everything

 

[MrH]

It's been flying since yesterday, even Michael's connection seemed a lot better, I shudder to think what would happen to it if iBurst start playing around with it while it's working as well as it is right now.

 

[Ekhaatvensters]

Well.. its 12:11, they havent started yet, in CPT at least.

I did notice that I changed or lost my IP and I'm now back on 500ms+ international with the old CPT local pings, I'd much rather have the lowered international latency though, but none of the IPs give me that anymore.

 

[who.is.michael]

Local & Intl changes...

Yip, it seems they did the changes late this afternoon, not only local but the SP connection in the USA that has changed as well:

iBurst Cape Town now connects internationally via Mauritius, Germany, then the UK and lands in the USA at San Antonio, Texas. This morning it was still Mauritius, New York.

Local pings down by 60ms and international up by 200ms, however I am not complaining, international speed is up from 300kbps to 500kbps and no sign of packet loss anywhere!


Speed test statistics
---------------------
Download speed: 519336 bps
Upload speed: 273304 bps
Quality of service: 39 %
Download test type: socket
Upload test type: socket
Maximum download pause: 660 ms
Average download pause: 27 ms
Minimum round trip time to server: 356 ms
Average round trip time to server: 368 ms

VoIP test statistics
--------------------
Jitter: you --> server: 5.6 ms
Jitter: server --> you: 4.6 ms
Packet loss: you --> server: 0.0 %
Packet loss: server --> you: 0.0 %
Packet discards: 0.0 %
Packets out of order: 0.0 %
Number of supported VoIP lines: 4
Estimated MOS score: 4.0


Local
Ping statistics for 196.40.97.13:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 124ms, Average = 63ms

Intl
Ping statistics for 216.239.37.104:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 501ms, Maximum = 648ms, Average = 541ms

Ping statistics for 206.82.202.46:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 580ms, Maximum = 618ms, Average = 600ms


Tracing route to www.l.google.com [216.239.37.104]
over a maximum of 30 hops:

1 5 ms 9 ms 8 ms 192.168.1.1
2 65 ms 44 ms 44 ms wbs-41-208-232-1.wbs.co.za [41.208.232.1]
3 78 ms 48 ms 49 ms 192.168.2.1
4 62 ms 48 ms 49 ms 192.168.4.34
5 61 ms 44 ms 44 ms fe2-1-0sub513.gw1.cpt1.alter.net [196.7.3.101]
6 261 ms 239 ms 249 ms so1-0-3.cr1.lnd19.alter.net [196.30.229.173]
7 282 ms 249 ms 244 ms so0-0-0.ir1.lnd19.alter.net [196.30.229.182]
8 269 ms 249 ms 252 ms so-3-0-1.IH2.LND9.ALTER.NET [146.188.3.49]
9 278 ms 266 ms 262 ms so-2-0-2.TR1.LND9.ALTER.NET [146.188.2.45]
10 279 ms 262 ms 249 ms POS1-0.BR1.LND9.ALTER.NET [146.188.7.242]
11 436 ms 544 ms 429 ms 146.188.35.138
12 436 ms 424 ms 414 ms sl-bb23-lon-3-0.sprintlink.net [213.206.129.151]
13 461 ms 429 ms 489 ms sl-gw23-lon-15-0.sprintlink.net [213.206.128.63]
14 446 ms 434 ms 444 ms sle-eurogoogle-1-0.sprintlink.net [82.195.189.186]
15 456 ms 429 ms 432 ms 66.249.95.130
16 554 ms 496 ms 512 ms 66.249.95.146
17 552 ms 522 ms 494 ms 66.249.94.235
18 556 ms 519 ms 512 ms 66.249.95.127
19 538 ms 494 ms 519 ms 66.249.95.126
20 556 ms 524 ms 519 ms 72.14.232.106
21 540 ms 539 ms 738 ms 72.14.232.108
22 537 ms 519 ms 539 ms va-in-f104.google.com [216.239.37.104]

 

[MrH]

So far it's still cruising.

EDIT: well done to whoever at iBurst got CT running smoothly, now PLEASE do NOT touch the system while it's working as well as it is.

 

[WebhostingTalk]

Beter yet send him to JHB