Fiskaly incident

Authentication Server high CPU load

Resolved after 50 minutes, affecting SIGN DE and Management API and 1 more, on November 10, 2025.

resolved Nov 10, 2025, 01:46 PM UTC

The issue was a unexpected high CPU load after a configuration change on the authentication server side. As a result, affected clients may receive 401 Unauthorized responses. In such cases, please generate a new token using your API key and API secret. We appreciate your understanding and apologize for any inconvenience caused.

Started
Nov 10, 2025, 12:55 PM UTC
Resolved
Nov 10, 2025, 01:46 PM UTC
Duration
50m
Detected by Pingoru
Nov 10, 2025, 12:55 PM UTC

Affected components

SIGN DEManagement APISIGN ATSIGN ESSIGN ITDSFINVK DEfiskaly DashboardSUBMIT DEAuthentication ServerSAFE

Update timeline

  1. investigating Nov 10, 2025, 12:55 PM UTC

    The last Authentication Server Maintenance has caused a high CPU load which effects all services besides the authentication service itself.

  2. resolved Nov 10, 2025, 01:46 PM UTC

    The issue was a unexpected high CPU load after a configuration change on the authentication server side. As a result, affected clients may receive 401 Unauthorized responses. In such cases, please generate a new token using your API key and API secret. We appreciate your understanding and apologize for any inconvenience caused.

Your product runs on more than Fiskaly

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →