cant seem to get chat to work today

[slave alexander]

it just goes to the loading/ connecting bit but never gets any further might be me maybe but thought i'd just put a post up in case its something you may be able to sort/ or if there's something else i could try

i will keep trying obviously and appreciate all your work here admin guy and gals / milovana team so thanks in advance

[slave alexander]

ah cool well thanks for your thanks Mr Jp & Mr Indigo

[slave alexander]

opps ur rite sorry about that ! very much MR Serap0x / Mr Bossman

[seraph0x]

Chat back up, thanks to everybody involved in getting the report up the chain.

[slave alexander]

thanks for fixing it Mr Bossman

[green]

Seems like the server is malfunctioning again .

Now where am I supposed to idle ?!?!?!?

~green~

[seraph0x]

Seems like the server is malfunctioning again .

Now where am I supposed to idle ?!?!?!?

~green~

Appears this was an issue with the guys who are hosting our chat server:

On April 22, 2009 @ 6:00 AM PDT our network engineers noticed a drop within our connectivity to the outside world. The dropped was alerted via external monitoring system where we quickly identified the issue and try isolating the issue as quickly as possible. Within a few minutes onsites our engineers noticed our link lights were down which we quickly notified building engineers of the physical connection issue. Once the building engineers were onsite they noticed a cut across multiple fibers. It appears the conduit that housed multiple fibers were cut. Many providers that carried physical transit through the same conduit were affected. Within 1 hour our building engineers were able to spliced the fiber and bring everything online. The fiber that connects to another secondary router that housed multiple carriers was unreachable during this time. Although we have provider redundancy our physical fiber transit were not redundant.

As of now we are in discussions with our building engineers to use other conduits to avoid issues like this again. This will allow us to achieve higher uptimes and avoid any physical issues that may occur within our datacenter.

[green]

That was a year ago though xD.. Maye a phenomena which occurs yearly

[seraph0x]

That was a year ago though xD.. Maye a phenomena which occurs yearly

They just made a typo, the subject of the message read "Network Outage - 04/22/2010", the message was sent out on April 23rd and the Chinese translation in the email also has the correct date:

在2010年4月22號 美國西岸6點左右 我們的網路專員發現機房對外的連線明顯的問題. 網路專員了解到這個線路的問題後馬上開始做些測試想要發現問題的來源.

幾分鐘內我們的技術發現網路交換器上的燈顯是沒有連線就馬上通知建築工程師看看是否在網路線上有問題建築工程師馬上重我們的交換器開始檢查所有的網路光纖線 在檢查的過程當中建築工程師發現光纖線的導管有斷裂的情況裡面的多條光纖也有斷裂的現象(當然也包況我們跟Xeex的直接光纖)Xeex也馬上通知建築工程師做搶救出現錯誤後Xeex想要重另外的一個光籤導管傳輸給我們也沒有辦法做到 所以變成只好等待建築工程師來換新的光纖線



發生事情後我們有跟建築工程師研究過另外給我們另外獨立的光纖導管 所以在類似的情況發生 的話我們比較有辦法在更短的時間內恢復