Status Page

Operational
SIGN DE API V2
SIGN DE API V1 (deprecated)
DSFinV-K API
SIGN AT API (RKSV)
SIGN ES API
Management API
Dashboard
Authentication Server
fiskalcheck
eReceipt API
eReceipt Web
eReceipt Dashboard

Latest Incidents

  • 1 day since last incident

  • No incidents reported.
  • No incidents reported.
  • Under Maintenance

    After the 1.25.0 release, we have introduced a minor fix which added a validation step that prevents the request bodies from having unicode characters, which made any Cash Point Closing containing a unicode character fail with a validation error.

    2024-07-25T10:32:20.056Z
    The problem is resolved 🎉

    We are happy to announce that the recent issue causing the Cash Point Closing validation error has been resolved by reverting the changes made to the mentioned validation step.

    We apologize for the inconvenience.

  • No incidents reported.
  • SIGN DE V1 - TLS certificate update

    SIGN DE API V1 (deprecated)
     -  (UTC)

    On 24 July 2024 between 17:00 CEST (15:00 UTC) and 17:30 CEST (15:30 UTC) the TLS certificates for www.kassensichv.io of SIGN DE V1 will be updated.

    There is no need for action as a result of the update for operating systems that are kept up to date.

    If your system has problems connecting to SIGN DE V1 via www.kassensichv.io, it may be necessary to upload the certificates manually.

    Please find the relevant instruction article on our support page.

    Please note, the update of the TLS certificate only relates to SIGN DE V1. SIGN DE V2 is not affected by this update.

    2024-07-24T15:12:07.755Z
    TLS certificate update completed 🚀

    Our TLS certificate update for www.kassensichv.io is completed. In case of issues please refer to the information stated above.

  • TLS certificate update

    SIGN DE API V2 DSFinV-K API Management API Authentication Server
     -  (UTC)

    On 24.07.2024, between 7:00 CEST (5:00 UTC) and 8:00 CEST (6: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 which 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 24.07.2024, between 7:00 CEST (5:00 UTC) and 8:00 CEST (6: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.
    2024-07-24T05:15:29.278Z
    TLS certificate update completed 🚀

    Our TLS certificate update for *.fiskaly.com is completed. In case of issues please refer to the information stated above.

    fiskaly services not affected by CrowdStrike outage

    SIGN DE API V2 SIGN DE API V1 (deprecated) DSFinV-K API SIGN AT API (RKSV) SIGN ES API Management API Dashboard Authentication Server fiskalcheck eReceipt API eReceipt Web eReceipt Dashboard
     -  (UTC)

    fiskaly has not been affected by the global CrowdStrike outage. Our systems remain fully operational, and there is no impact on their performance or availability.

    SIGN DE API V2
    Major Outage

    Due to a failed update, the system experienced extensive disruption between 09:09 CEST (07:09 UTC) and 09:18 CEST (07:19 UTC). The update was rolled back, and the system returned to normal operation.

    The team is investigating the cause of the update failure.

  • No incidents reported.
  • No incidents reported.