Fiskaly incident

Authentication Server Restart

Resolved after 1 day 12 hours, affecting Authentication Server, on October 30, 2025.

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.

Started: Oct 30, 2025, 09:20 AM UTC
Resolved: Oct 31, 2025, 09:48 PM UTC
Duration: 1d 12h
Detected by Pingoru: Oct 30, 2025, 09:20 AM UTC

Affected components

Authentication Server

Update timeline

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.

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.