Issue is now fixed. Thanks for the heads-up, guys.