Fiskaly had 39 outages in the last 2 years totaling 613h 56m of downtime — averaging 1.6 incidents per month.
There were 39 Fiskaly outages since January 14, 2025 totaling 613h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
Due to an unforeseen change in ELSTER, the final Transmission to the portal has been impaired since today around 10:35 CEST (08:45 UTC). The issue is ongoing. The team is currently working on a solution. We apologize for any inconvenience and will keep you updated.
The incident has been resolved. Please re-trigger failed transmissions.
Since ~11:55 CEST (09:55 UTC) on 13.04.2026 SUBMIT DE shows a increased number of timeouts and errors for some customers then creating a submission in TEST or LIVE environment. The reason is identified and we are working on a solution.
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.
Today, 31.03.2026, the AdE portal returned a temporary error (“Authentication error: The ADE portal is temporarily unavailable.”) between 12:13 CEST (10:13 UTC) and 12:47 CEST (10:47 UTC). The issue has been resolved on their side, and the service is now operating normally. Thank you for your understanding. You may resend the affected records using a new idempotency key. For more details on handling errors, please refer to this FAQ.
Following the completion of the scheduled maintenance, some authentication flows are currently experiencing degraded performance in rare cases. We are actively investigating the issue and will provide updates as soon as more information becomes available.
The issue affecting some authentication flows has been resolved. Systems are operating normally again. We will continue to monitor the situation to ensure stability.
We have temporarily experienced increased error rates yesterday between 18:00 CET (17:00 UTC) and 22:00 CET (21:00 UTC) and today between 12:38 CET (11:38 UTC) and 12:48 CET (11:48 UTC). We are currently investigating possible root causes and are also actively monitoring the system.
We are currently still investigating the root cause resulting in temporary errors and will provide further updates shortly.
We are monitoring the situation and still investigating the root cause resulting in temporary errors.
We experience increased error rates again starting with 12:12 CET (11:12 UTC) up to 12:32 CET (11:32 UTC). We are currently investigating possible root causes.
The experienced increased error rates happened not any more since Saturday, 28.02.2026 10:25 CET (09:25 UTC) to 10:35 CET (09:35 UTC). We are actively monitoring the system still, but since the last occurrence all services were available and processing as expected.
After comprehensive monitoring, we confirm that the incident has been resolved and all services are operating as expected.
SIGN IT temporarily experienced 500 and timeout errors. Error rates are returning to normal levels. Our engineering team is taking care of the situation and continues to monitor the system. Thank you for your patience.
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.
Between 10:20 CET (09:20 UTC) and 10:25 CET (09:25 UTC) operations experienced timeouts or high latency. The issue was identified and resolved.
This incident has been resolved.
We are currently experiencing increased 500 and timeout errors in SIGN IT. This may result in degraded performance and delayed responses for some requests. Our team is investigating the issue with high priority. We will provide further updates as soon as more information becomes available. Thank you for your patience and understanding.
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.
We are currently experiencing decreased performance in creating digital receipt PDF files. The team is investigating the issue. We apologize for the inconvenience.
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.
We are currently experiencing disruptions affecting the transmission of some receipts from SIGN IT to the "Fatture e Corrispettivi" Web Portal. Our team is actively investigating the root cause and working on a hot-fix release. We apologize for any inconvenience and will provide updates as soon as more information becomes available.
This incident has been resolved.
Due to an incident signature service requests cannot be processed since 12:34 CET (11:34 UTC). We're investigating the issue.
We are observing higher latency and increased 500 errors on SIGN DE V2. Analysis is ongoing, and we will post an update as soon as more information is available.
The incident has been resolved. Transaction rates and response times have recovered, and timeouts are no longer being observed. The team is currently analyzing the root cause and implementing measures to prevent recurrence.
This incident has been resolved.
The last Authentication Server Maintenance has caused a high CPU load which effects all services besides the authentication service itself.
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.
Following yesterday's TSS update, some TSS instances currently experience degraded signing performance. We are working on a solution to mitigate this issue.
The root cause was identified and response times are recovering. We are currently closely monitoring system performance in order to ensure stability.
After comprehensive monitoring, we confirm that the incident has been resolved and all services are operating as expected.
Following the completion of today's TSS update, we detected an unexpected behavior affecting a subset of TSS instances. The listTss and retrieveTss endpoints, as well as exports are currently returning outdated version information. Signing transactions is not affected. We are currently analyzing this behavior in order to determine the root cause and implement a fix. We apologize for the inconvenience.
The root cause of the issue has been identified and resolved. All version data is now returned accurately. We are closely monitoring system performance to ensure stability and confirm that all services are operating as expected.
After comprehensive monitoring, we confirm that the incident has been resolved and all services are operating as expected.
We are currently experiencing unplanned restarts of our authentication service. As a result, refresh tokens are invalidated and can not be used for re-authenticating. In this case please authenticate with API Secret and API Secret instead. We apologize for the inconvenience.
A reason for the unexpected restarts was identified and mitigated, we still are monitoring the current behavior.
After extensive monitoring phase the authentication service has not caused any issues or restarts, so it is marked as fully operational again.
Since yesterday around 21:00 CEST (19:00 UTC), we experienced a degraded performance in export processing. The root cause has been identified and export processing performance has returned to normal at 10:15 CEST (08:15 UTC). We are actively monitoring the system to ensure continued stability.
Export processing performance has stabilized. We will keep monitoring the system.
The external service FinanzOnline is currently not available. The following SIGN AT processes may be affected: Update a Signature Creation Unit Update a Cash Register Validate a Receipt
The external service FinanzOnline is available again.
Updating the first batch of TSSs to version 1.0.15-1.5.0 has been completed. Unfortunately, unforeseen issues during the update prevented some TSS instances from being restored, requiring them to be set to DEFECTIVE. Affected customers will be proactively contacted by us shortly. If affected, please create a new TSS and Client for the DEFECTIVE TSS instance.