Fiskaly incident

Authentication Server Restart

Notice Resolved View vendor source →

Fiskaly experienced a notice incident on October 30, 2025 affecting Authentication Server, lasting —. The incident has been resolved; the full update timeline is below.

Started
Oct 30, 2025, 09:20 AM UTC
Resolved
Oct 30, 2025, 09:20 AM UTC
Duration
—
Detected by Pingoru
Oct 30, 2025, 09:20 AM UTC

Affected components

Authentication Server

Update timeline

  1. resolved Oct 30, 2025, 09:20 AM UTC

    Yesterday, 29.10.2025, at 22:48 CET (21:48 UTC), we experienced an unplanned restart of our authentication service. As a result, refresh tokens were invalidated and can not be used for re-authenticating. In this case, please authenticate using API Secret and API Secret instead. Please make sure your implementation uses ApiKeyAuthentication if RefreshTokenAuthentication fails with a 401 HTTP status code response. We apologize for the inconvenience.