Hi yes I can confirm all went through and is good, however a suggestion from me would to update system status when issues happen just so nobody is unclear about any issues that are happening before an exchange.
They should have an
https://exch.cx/status page along with some software that monitors the RPC connections to their various full nodes as well as to their website and other systemd services, so that they can easily write [ONLINE] [OFFLINE] statuses, and a benefit of that would be no privacy-invading scripts or web services required.
I was a bit puzzled why eXch didn't quite update their status page during the last technical issues. Understandably some users with stuck transactions complained because likely they wouldn't have had initiated transactions knowing there have been pending issues.
It seems to me that eXch's status page isn't fully automatic and this is maybe for a good reason. If it were automatic, as also NotATether suggests, there would be an incentive for attackers or competitors to disrupt and exploit the automatism. It's simple, if you can easier trigger a less favourable service status of eXch for potential customers, those will likely hold or not do a transaction thus hampering eXch's business. I guess eXch has some human judgement involved for their service status page.
I know and understand, it's no funny experience when you start a transaction with eXch and things don't run as smoothly as usual. Good to read and see that reported issues here are properly resolved.