One liner: Stuff went wrong at 2036, stuff was fixed at 2115.
Brief explanation (all times are UTC/GMT):
RMXP is hosted on Slacked's server, Slacked's server is on Awknet's network (they provide our connectivity to the rest of the world as well as the physical machine). Awknet itself has several "upstream" providers (upstream as in they are higher up the chain) which agree to pass on their traffic to the rest of the Internet, one of these upstream providers is GlobalCrossing.
At 2036 UTC a failure upstream in GlobalCrossing's network caused falcon to be unavailable. This meant that rmxp.org was inaccessible (you may also have experienced problems connecting to Slacked (IRC) during this time). The fault was rectified by 2115.
More technical explanation:
There was some confusion (see the status.s.o post over here) over whether the problem was due to a failed switch in Awknet's (our service provider) network or something else. This turned out to be partially true, however the main cause of the problem was within GlobalCrossing's network, specifically the route between GlobalCrossing and Internode.
If you had any problems after 2115 it was probably due to this:
It turned out that there was also a problem with one of the switches at Awknet which meant DNS resolution on falcon was not working, this was rectified by 2220.
There should be no residual problems. Everything should be fine. The sky is back up again. Thanks for your patience. :thumb:
Brief explanation (all times are UTC/GMT):
RMXP is hosted on Slacked's server, Slacked's server is on Awknet's network (they provide our connectivity to the rest of the world as well as the physical machine). Awknet itself has several "upstream" providers (upstream as in they are higher up the chain) which agree to pass on their traffic to the rest of the Internet, one of these upstream providers is GlobalCrossing.
At 2036 UTC a failure upstream in GlobalCrossing's network caused falcon to be unavailable. This meant that rmxp.org was inaccessible (you may also have experienced problems connecting to Slacked (IRC) during this time). The fault was rectified by 2115.
More technical explanation:
There was some confusion (see the status.s.o post over here) over whether the problem was due to a failed switch in Awknet's (our service provider) network or something else. This turned out to be partially true, however the main cause of the problem was within GlobalCrossing's network, specifically the route between GlobalCrossing and Internode.
If you had any problems after 2115 it was probably due to this:
It turned out that there was also a problem with one of the switches at Awknet which meant DNS resolution on falcon was not working, this was rectified by 2220.
There should be no residual problems. Everything should be fine. The sky is back up again. Thanks for your patience. :thumb:
