Previous incidents

All services are now fully operational again. We believe the underlying issues have been resolved and do not expect them to reoccur.

Our team will continue to monitor system performance closely to ensure ongoing stability, but for now, everything appears to be functioning as expected.

We attempted to implement a fix for the referrer and user agent inaccuracies; however, it requires that users explicitly provide the User-Agent and Referer headers to ensure correct logging. Without these headers, the User-Agent will appear as Unknown and the Referer as Direct. Aside from this, all other issues have been resolved, and the system appears to be fully operational.

All identified issues have been resolved, and we are observing signs of full recovery. We will continue to monitor the situation closely to ensure stability and prevent recurrence. Additionally, we have fixed a frontend error that caused the interface to crash when generating an API key. This has been addressed through improved fallbacks and enhanced error handling mechanisms.

The docs are back online. The US region of ApiDog also recovered slowly, so we can quickly transfer everything to the EU. Now everything runs on the EU edition of ApiDog, which remained online when our docs went offline. We hope that everything stays online now and that doesn't happen again.

This incident has been resolved.

All incidents are fully resolved, and sites are operating normally.

This incident has been resolved.

Issue's are resolved

Thanks to the quick support from our hosting provider, everything is back online. We hope this doesn't happen again, but for now all our services are operational again.

We have identified the root case and we have placed a fix in the code. We are currently monitoring whether the issue returns or not.

The issue is fixed, it responds instantly, only our status page for our crons still needs to be updated, but that updates itself, we have no control over that.