Update - We are monitoring the situation and still investigating the root cause resulting in temporary errors.
Feb 26, 2026 - 19:47 CET
Update - We are currently still investigating the root cause resulting in temporary errors and will provide further updates shortly.
Feb 26, 2026 - 15:33 CET
Monitoring - 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.
Feb 26, 2026 - 13:40 CET
On 05.03.2026, between 07:45 CET (06:45 UTC) and 08:00 CET (07:00 UTC), the TLS certificate for *.fiskaly.com will be updated.
This update is a routine process and should not cause any disruptions or issues for your fiskaly services.
The intermediate certificate in the chain will change this time, but because of no changes in the root certificate, no additional action should be needed.
The following article lists all root certificates that must be added in case of a manual update:
Date and Time: The TLS certificate update is scheduled for 05.03.2026, between 07:45 CET (06:45 UTC) and 08:00 CET (07:00 UTC).
No Action Required: For the majority of systems using fiskaly services, no action is required in response to this update. Your TLS certificate will automatically renew and update itself without any intervention on your part.
Minor Service Disruption: We have taken measures to ensure that your fiskaly services will continue to function seamlessly. However, short service disruptions during or after the update may occur.
Verification: After the update, we recommend verifying the TLS certificate configuration for your fiskaly services to ensure that everything is in order. If you require assistance with this, we are happy to assist you.
Posted on
Dec 11, 2025 - 08:06 CET
Past Incidents
Feb 26, 2026
Unresolved incident: SIGN DE - Increased error rate.
Completed -
The scheduled maintenance has been completed.
Feb 25, 17:00 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 25, 13:00 CET
Scheduled -
Due to a necessary infrastructure update, some services of the SIGN DE API v2 TEST environment may temporarily not be available within the maintenance window. The maintenance window is scheduled for Wednesday, 25.02.2026 from 13:00 CET (12:00 UTC) to 17:00 CET (16:00 UTC).
Feb 20, 12:35 CET
Completed -
The scheduled maintenance has been completed.
Feb 21, 19:00 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 21, 08:00 CET
Scheduled -
Due to a necessary maintenance announced by Araba, there can be temporary disruptions in the transmission of TicketBAI Files from SIGN ES to the servers of this province.
The maintenance window is scheduled for Saturday, February 21st, 2026, from 8:00 CET (7:00 UTC) to 19:00 CET (18:00 UTC).
Feb 20, 08:37 CET
Completed -
The maintenance was finished successfully at 16:00 CET (15:00 UTC).
Feb 18, 16:00 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 18, 13:00 CET
Scheduled -
Due to a necessary infrastructure update, some services of the SIGN DE API v2 TEST environment may temporarily not be available within the maintenance window. The maintenance window is scheduled for Wednesday, 18.02.2026 from 13:00 CET (12:00 UTC) to 17:00 CET (16:00 UTC).
Feb 12, 09:14 CET
Completed -
The maintenance was finished successfully at 22:35 CET (21:35 UTC). There was no service interruption during this period.
Feb 17, 22:38 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 17, 22:00 CET
Scheduled -
Today, 17 February 2026, from 22:00 to 23:00 CET (21:00 to 22:00 UTC), technical maintenance is required. Due to technical reasons, this activity has become necessary at short notice and could not be scheduled in advance.
No customer impact is expected. However, there is a low risk of a temporary outage during this time. We will closely monitor the system throughout the maintenance window and keep you updated.
Thank you for your understanding.
Feb 17, 17:41 CET
Resolved -
This incident has been resolved.
Feb 17, 18:40 CET
Monitoring -
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.
Feb 17, 10:31 CET
Resolved -
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.
Feb 17, 14:14 CET
Monitoring -
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.
Completed -
The scheduled maintenance has been completed.
Feb 15, 21:25 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 15, 21:15 CET
Scheduled -
Due to a necessary maintenance announced by Gipuzkoa, there can be temporary disruptions in the transmission of TicketBAI Files from SIGN ES to the servers of this province.
The maintenance window is scheduled for Sunday, February 15th, 2026, from 21:15 CET (20:15 UTC) to 21:25 CET (20:25 UTC).
Feb 13, 11:17 CET
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.
Feb 14, 18:53 CET
Investigating -
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.
Feb 14, 17:57 CET
Completed -
The scheduled maintenance has been completed.
Feb 14, 16:30 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 14, 15:30 CET
Scheduled -
Due to a necessary maintenance announced by Gipuzkoa, there can be temporary disruptions in the transmission of TicketBAI Files from SIGN ES to the servers of this province.
The maintenance window is scheduled for Saturday, February 14th, 2026, from 15:30 CET (14:30 UTC) to 16:30 CET (15:30 UTC).
Feb 13, 11:13 CET
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.
Feb 13, 21:05 CET
Update -
Our team continues to actively work on and monitor the situation regarding increased 500 and timeout errors in SIGN IT.
The measures implemented earlier today have led to improvements. While the issue is not yet fully resolved, overall stability has improved. We are continuing to implement further optimizations while closely observing system behavior.
We will provide additional updates if necessary.
Feb 13, 18:25 CET
Update -
Our team remains fully engaged in resolving the incident affecting SIGN IT. We continue to investigate the root cause of the increased 500 and timeout errors while actively implementing measures to stabilize the system.
Mitigation steps are in place, and we are closely monitoring the situation to restore normal service quality as quickly as possible.
We understand the impact this may have and appreciate your patience. Further updates will follow once new information becomes available.
Feb 13, 14:17 CET
Investigating -
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 an update as soon as more information is available.