This incident has been resolved.

We've implemented a workaround. Things are working as expected and we continue to monitor the situation.

We were able to restore access to content hosted via stonly.com and it's subdomains. We're still evaluating how to restore access to knowledge bases hosted under custom domains.

We're rolling back the workaround, restoring our services one after another

While we're working on resolving the underlying issue, we're actively working on implementing a workaround that should bring us back in the next 20 minutes

The issue seems to be our cloud provider network problem. We've escalated the issue to their support and are trying to build a temporary workaround to restore services in parallel.

We're currently investing an issue with Stonly not loading and returning 504 Gateway Timeout error.