Update - 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.
May 25, 2026 - 15:17 CEST
If affected, please ensure not to block the till and print "TSS not available" on the receipts.
We appreciate your continued patience.
May 25, 2026 - 15:17 CEST
Update - 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 (09:30 UTC) and 12:00 CEST (10:00 UTC), temporary disruptions and slower response times may occur as part of the ongoing resolution process.
We appreciate your patience and understanding.
May 25, 2026 - 11:26 CEST
Between approximately 11:30 CEST (09:30 UTC) and 12:00 CEST (10:00 UTC), temporary disruptions and slower response times may occur as part of the ongoing resolution process.
We appreciate your patience and understanding.
May 25, 2026 - 11:26 CEST
Update - 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.
May 25, 2026 - 08:30 CEST
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.
May 25, 2026 - 08:30 CEST
Update - 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.
May 24, 2026 - 20:28 CEST
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.
May 24, 2026 - 20:28 CEST
Update - 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.
May 24, 2026 - 13:40 CEST
Our team is actively working on resolving this issue.
We apologize for the disruption.
May 24, 2026 - 13:40 CEST
Identified - 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.
May 24, 2026 - 12:19 CEST
We are currently working on a solution to mitigate this issue.
May 24, 2026 - 12:19 CEST
Investigating - We are currently experiencing degraded performance affecting signing transactions.
We are investigating the issue and will provide further updates.
May 24, 2026 - 11:01 CEST
We are investigating the issue and will provide further updates.
May 24, 2026 - 11:01 CEST
Global
Operational
Management API
Operational
fiskaly Dashboard
Operational
Authentication Server
Operational
SAFE
Operational
Germany
Degraded Performance
SIGN DE
Degraded Performance
DSFINVK DE
Operational
SUBMIT DE
Operational
fiskalcheck
Operational
Austria
Operational
SIGN AT
Operational
Spain
Operational
SIGN ES
Operational
Italy
Operational
SIGN IT
Operational
France
Operational
SIGN FR
Operational
RECEIPT
Operational
RECEIPT
Operational
RECEIPT Web
Operational
RECEIPT Dashboard
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
TLS certificate update May 28, 2026 07:45-08:00 CEST
On 28.05.2026, between 07:45 CEST (05:45 UTC) and 08:00 CEST (06:00 UTC), the TLS certificate for
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:
How do I manually add the latest TLS certificate for *.fiskaly.com?
Important information at a glance:
Posted on Mar 05, 2026 - 08:14 CET
*.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:
How do I manually add the latest TLS certificate for *.fiskaly.com?
Important information at a glance:
- Date and Time: The TLS certificate update is scheduled for 28.05.2026, between 07:45 CEST (05:45 UTC) and 08:00 CEST (06: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 Mar 05, 2026 - 08:14 CET