Is Fiskaly down?
Last checked 6m agoNo incidents right now.
Fiskaly is operational right now. Last checked 6m ago; the most recent incident resolved 4d ago.
Real-time Fiskaly status, recent outages, and incident history — pulled directly from Fiskaly's official status page at https://status.fiskaly.com every 5 minutes. Pingoru tracks 15 Fiskaly services and has captured 17 incidents in the last 90 days (99.41% uptime). Get email, Slack, Discord, or webhook alerts the moment Fiskaly reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- SIGN IT
Timeline · 3 updates
- investigating · Jun 09, 2026, 03:18 PM UTC
We are currently observing increased timeouts on the SIGN IT service. Our team is actively investigating the root cause. We will keep you updated on our progress. We appreciate your patience.
- monitoring · Jun 09, 2026, 03:31 PM UTC
The increased timeouts have been resolved and all systems are operational again. Our team continues to investigate the root cause. All systems remain under close monitoring.
- resolved · Jun 09, 2026, 03:46 PM UTC
The incident has been resolved and all systems on SIGN IT are fully operational. We will continue to monitor closely and take measures to prevent a recurrence. We apologize for the disruption caused.
Latest: The incident has been resolved and all systems on SIGN IT are fully operational. We will continue to monitor closely and take measures to prevent a recurrence. We apologize for the…
-
- SIGN DE
Timeline · 10 updates
- investigating · May 24, 2026, 09:01 AM UTC
We are currently experiencing degraded performance affecting signing transactions. We are investigating the issue and will provide further updates.
- identified · May 24, 2026, 10:19 AM UTC
Due to issues after today's maintenance operation some TSS instances still experience degraded signing performance. We are currently working on a solution to mitigate this issue.
- identified · May 24, 2026, 11:40 AM UTC
A subset of TSS instances is still experiencing degraded performance resulting in 502 errors. If affected, please make sure not to block the till and print "TSS not available" on the receipts. Our team is actively working on resolving this issue. We apologize for the disruption.
- identified · May 24, 2026, 06:28 PM UTC
A subset of TSS instances continues to experience degraded performance resulting in 502 errors which is expected to persist overnight. If affected, please ensure not to block the till and print "TSS not available" on the receipts. Our team is actively working on resolving the issue. Further updates will follow in the morning. We apologize for the disruption.
- identified · May 25, 2026, 06:30 AM UTC
A subset of TSS instances continues to experience degraded performance resulting in 502 errors. We have identified the root cause and are fully focused on restoring the affected instances as quickly as possible. If affected, please ensure not to block the till and print "TSS not available" on the receipts. Further updates will follow. We apologize for the disruption.
- identified · May 25, 2026, 09:26 AM UTC
A subset of TSS instances continues to experience degraded performance resulting in 502 errors. Our team is actively working on resolving the issue. Between approximately 11:30 CEST and 12:00 CEST, temporary disruptions and slower response times may occur as part of the ongoing resolution process. We appreciate your patience and understanding.
- identified · May 25, 2026, 01:17 PM UTC
We are continuing to work on resolving the degraded performance affecting a subset of TSS instances. Progress is being made and further updates will follow. If affected, please ensure not to block the till and print "TSS not available" on the receipts. We appreciate your continued patience.
- identified · May 26, 2026, 09:04 AM UTC
Following a thorough analysis, some TSS instances could not be recovered and had 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. We apologize for the inconvenience.
- identified · May 26, 2026, 04:01 PM UTC
We are actively contacting all affected customers directly. Our team continues to work on fully restoring the system. We appreciate your patience.
- resolved · May 27, 2026, 10:00 AM UTC
This incident has now been resolved and response times are back to their normal levels. All systems are now working as expected. Following the required maintenance update on 24 May 2026, a subset of TSS instances could not be recovered and had to be set to DEFECTIVE. We are actively reaching out to affected customers with further guidance. We sincerely apologize for the disruption caused and thank you for your patience throughout this incident.
Latest: This incident has now been resolved and response times are back to their normal levels. All systems are now working as expected. Following the required maintenance update on 24 May…
-
- SUBMIT DE
Timeline · 2 updates
- investigating · May 18, 2026, 02:45 PM UTC
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.
- resolved · May 18, 2026, 03:43 PM UTC
The incident has been resolved. Please re-trigger failed transmissions.
Latest: The incident has been resolved. Please re-trigger failed transmissions.
-
- SUBMIT DE
Timeline · 2 updates
- identified · Apr 14, 2026, 06:55 AM UTC
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.
- resolved · Apr 14, 2026, 08:23 AM UTC
The issue was resolved with 09:45 CEST (07:45 UTC).
Latest: The issue was resolved with 09:45 CEST (07:45 UTC).
-
- SIGN DE
Timeline · 1 update
- resolved · Apr 09, 2026, 03:25 PM 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.
Latest: 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…
-
See the full Fiskaly outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Fiskaly outage history →Or sign up free to get alerts when Fiskaly breaks · 10 free monitors · No credit card
- SIGN IT - Increased Timeouts ResolvedStarted Jun 09, 2026, 03:18 PM UTC · Resolved Jun 09, 2026, 03:46 PM UTC · 28m
- SIGN DE v2 - Degraded performance ResolvedStarted May 24, 2026, 09:01 AM UTC · Resolved May 27, 2026, 10:00 AM UTC · 3d
- Started May 18, 2026, 02:45 PM UTC · Resolved May 18, 2026, 03:43 PM UTC · 58m
- Started Apr 14, 2026, 06:55 AM UTC · Resolved Apr 14, 2026, 08:23 AM UTC · 1h 27m
- Started Apr 09, 2026, 03:25 PM UTC · Resolved Apr 09, 2026, 03:25 PM UTC · —
- Started Mar 31, 2026, 11:28 AM UTC · Resolved Mar 31, 2026, 11:28 AM UTC · —
- Started Mar 22, 2026, 07:08 PM UTC · Resolved Mar 22, 2026, 08:39 PM UTC · 1h 30m