Fiskaly Outage History

Further analysis showed that integrators were not impacted during the given period. We are closing this incident.

This incident has been resolved. Initializing SCUs works as expected again. We apologize for the inconvenience.

After close monitoring, we can confirm the service has been operating normally for the past hour. The AdE downtime is now resolved. We apologize for any inconvenience this may have caused. For more details on handling errors, please refer to our FAQ: https://support.fiskaly.com/hc/en-001/articles/26104165291932-SIGN-IT-Error-Handling-Guide

The issue affecting the SIGN DE v2 TEST system has been resolved. The root cause has been identified and fixed, and we do not expect a recurrence of this behaviour. Requests to the TEST environment are processing normally again. The LIVE (productive) environment and live signing operations were not affected at any point. We apologise for the inconvenience caused during integration testing.

Service performance has returned to normal levels. We will continue to monitor the situation closely to ensure ongoing stability. We apologize for any inconvenience this may have caused.

Today, 14.07.2026, from 10:44 to 10:50 CEST (08:44 to 08:50 UTC), some TSS instances experienced increased response times. We apologize for any inconvenience this may have caused.

The performance issues affecting the fiskaly HUB have been resolved. The HUB is fully operational again, with normal response times and loading behavior. The fiskaly APIs were not affected at any time, signing and processing continued to work normally throughout. Thank you for your patience.

This incident has been resolved.

Between 10:22 and 10:55 CEST, we observed increased timeouts on the SIGN IT service. All systems are now fully operational. We apologize for the disruption caused and will continue to monitor closely to prevent a recurrence.

The incident has been resolved. Please re-trigger failed transmissions.

The issue was resolved with 09:45 CEST (07:45 UTC).

On Saturday, 04.04.2026, some TSS instances experienced increased timeouts during the following periods: 12:14-12:27 CEST (10:14-10:27 UTC) 12:50-12:56 CEST (10:50-10:56 UTC) 13:52-13:56 CEST (11:52-11:56 UTC) 15:30-15:34 CEST (13:30-13:34 UTC) We apologize for any inconvenience this may have caused.

The issue affecting some authentication flows has been resolved. Systems are operating normally again. We will continue to monitor the situation to ensure stability.

After comprehensive monitoring, we confirm that the incident has been resolved and all services are operating as expected.

A hot-fix mitigation has been successfully deployed, and error rates have stabilized. No further 500 errors have been observed since 11:03 CET (10:03 UTC). Our engineering team continues to monitor the system and will ship additional hot-fix improvements throughout the day to ensure continued stability.

This incident has been resolved.

The previously observed increase in 500 and timeout errors in SIGN IT has been resolved. Service performance has returned to normal levels, and all systems are operating as expected. We will continue to monitor the situation closely to ensure ongoing stability and consistent service quality. Thank you for your patience and understanding.

The incident has been resolved. The underlying issue has been addressed, and receipt PDF generation is now operating as expected.

The latency of the signing requests for some TSSs was significantly increased between 13:50 CET (12:50 UTC) and 14:00 CET (13:00 UTC). The service recovered and latency is back to normal.

This incident has been resolved.

This incident has been resolved.

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.

We experienced an internal issue that temporarily affected all transmissions through SIGN IT. The disruption occurred on 07.11.2025, between 11:00 CET (10:00 UTC) and 13:00 CET (12:00 UTC). The issue has been identified and is currently under investigation. Services are now fully operational again. We apologize for any inconvenience this may have caused.

On October 29th, we experienced an unexpected unavailability of the external service "Fatture e Corrispettivi" portal, which affected transmissions through SIGN IT. The disruption occurred approximately between 09:40 and 11:40, and again between 21:40 and 23:40. We apologize for any inconvenience this may have caused.

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.