Previous incidents

We are currently investigating an issue that caused a few of our endpoints to respond with 500 status codes. Service has been restored but we are still investigating the root cause.

The root cause was identified as a missing restart after setting a server key, causing our AWS instance to restart on its own which in turns cause services not to properly initiate.

We’ve identified a problem with our WAF provider that’s temporarily blocking some customers, resulting in a 403 status code message. We’re collaborating closely with the service provider to pinpoint the root cause and resolve the issue promptly.