Management API intermittent timeouts and 401 errors

Between approximately 07:00 and 8:30 UTC on Thursday, Oct 23, 2025, some requests to our Public APIs experienced intermittent timeouts and later all requests resulted in 401 “invalid key/secret” responses.

Impact: All our public facing APIs (Management, Public, Reporting).

Unaffected: DNS resolution and security policy enforcement for end-users.

Root cause: A storage configuration issue during a host restart caused the APIs authentication component to start without access to the current credential dataset, leading to authentication failures.

Current status: The issue has been fully resolved, and the service is operating normally. No action is required on your side. If you retried requests during the window and saw authentication failures, those should now succeed.

We’re improving safeguards and monitoring around the authentication path to prevent a recurrence.
If you still observe any anomalies, please provide us with request and timestamps.

Sorry for the disruption, and thank you for your patience.

Best regards,
Whalebone Support