fiskaly logo

Is fiskaly Down?

FinTech & PaymentsLive status, outages, and incident history

No. fiskaly is up right now.

Every monitored fiskaly system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment fiskaly breaks

fiskaly is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official fiskaly status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

fiskaly Status Summary

As of 16:27 UTC on 14 November 2026, fiskaly is operational. PulsAPI checked fiskaly's official status page and found 21 of 21 components operational, with no active incidents. The latest incident, "SIGN IT – AdE submissions timing out", was on Nov 2, 2026 and lasted 24h 29m.

Cite as: PulsAPI, “fiskaly status”, checked 14 November 2026, 16:27 UTC. https://www.pulsapi.com/services/fiskaly

fiskaly Component Status

The main fiskaly systems on this page. All 21 are operational right now.

21operational
Austria » SIGN AT
Operational
Belgium » E-INVOICE BE
Operational
France » SIGN FR
Operational

18 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Germany » DSFINVK DE, Germany » E-INVOICE DE, Germany » fiskalcheck, Germany » SIGN DE, Germany » SUBMIT DE, Global » Authentication Server, Global » fiskaly Dashboard, Global » fiskaly HUB, Global » Management API, Global » SAFE, Italy » E-INVOICE IT, Italy » SIGN IT, and 6 more.

See all of them free

Component statuses may change independently during partial outages.

Recent fiskaly Outages & Incidents

Incident history from the official fiskaly status page, including resolution updates.

SIGN IT – AdE submissions timing outResolved Nov 2, 2026 · 24h 29mResolved

This incident has been resolved. SIGN IT API response times have returned to normal following a period of close monitoring. --- [2026-11-02T15:44:23.716+01:00] (monitoring) After a temporary outage, the Agenzia delle Entrate (AdE) "Fatture e Corrispettivi" web portal is operational again. Receipt transmissions from SIGN IT have returned to normal levels. We will continue to monitor the situation closely. Thank you for your patience and understanding. --- [2026-11-02T15:07:03.450+01:00] (monitoring) After a brief recovery, the Agenzia delle Entrate (AdE) "Fatture e Corrispettivi" web portal has been unavailable again since 14:46 CET (13:46 UTC). Almost all receipt transmissions from SIGN IT are currently returning an HTTP 503 error. For more details on handling errors, please refer to our <a href="https://support.fiskaly.com/hc/en-001/articles/26104165291932-SIGN-IT-Error-Handling-Guide">Error Handling Guide</a>. We are continuing to monitor the situation and apologize for the inconvenience. --- [2026-11-02T14:36:22.489+01:00] (monitoring) Today, 02.11.2026, between 13:35 CET (12:35 UTC) and 14:17 CET (13:17 UTC), the Agenzia delle Entrate (AdE) "Fatture e Corrispettivi" web portal experienced degraded performance, causing receipt transmissions from SIGN IT to time out. Affected requests returned a Submission error or an Authentication error. The service has been operating normally since. Receipts that failed with a Submission error may still have been received by the AdE. To avoid duplicates, please check on the AdE portal whether they were registered before resubmitting them. Requests that failed with an Authentication error can be safely retried. For more details, please refer to our <a href="https://support.fiskaly.com/hc/en-001/articles/26104165291932-SIGN-IT-Error-Handling-Guide">Error Handling Guide</a>. We will continue to monitor the situation closely. We apologize for any inconvenience this may have caused.

SIGN IT - Degraded performanceResolved Oct 28, 2026 · 22h 36mResolved

The previously observed increase in SIGN IT API response times has been resolved. --- [2026-10-28T14:06:06.342+01:00] (monitoring) On Tuesday, 27.10.2026, between 18:17 CET (17:17 UTC) and 22:56 CET (21:56 UTC), SIGN IT experienced increased response times in the LIVE environment. During this period, some requests may have taken longer than usual to complete. The issue was caused by increased load on the platform. Response times are now back to normal, and no action is required on your side. We continue to monitor the service closely and are working on further improvements to platform stability. We apologize for any inconvenience this may have caused.

SIGN IT - Degraded performanceResolved Oct 26, 2026 · 15h 22mResolved

The previously observed increase in SIGN IT API response latencies has been resolved. --- [2026-10-26T18:30:03.505+01:00] (monitoring) From approximately 10:00 CEST (08:00 UTC) on Saturday, 24.10.2026, until 16:16 CET (15:16 UTC) on Sunday, 25.10.2026, SIGN IT experienced degraded API response latencies on the LIVE environment. The issue was caused by increased load on the platform. Our team deployed a fix, and API response times are now back to normal. We continue to monitor the service closely and are working on further improvements to the platform's stability. We apologize for any inconvenience this may have caused. If you have any questions, please contact dev-support@fiskaly.com.

Upcoming maintenance

Announced by fiskaly. Planned work, not an outage.

SIGN DE v2: Scheduled maintenanceScheduled for Nov 22, 2026 · 1h 0mScheduled

In order to improve the reliability of our services, some TSS instances may be temporarily unavailable during the following maintenance window: Sunday, 22.11.2026, 07:00 – 08:00 CET (06:00 – 07:00 UTC). Please note: If the SIGN DE v2 API malfunctions or is unreachable, tills must remain operational. Make sure that your integration does not block the checkout process. Setting correct timeouts (2-3 sec) is important. Details can be found here: <a href="https://workspace.fiskaly.com/countries/germany/guides/error-handling/">How to deal with timeouts</a> In case of questions, feel free to reach out to dev-support@fiskaly.com.

fiskaly Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a fiskaly incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live fiskaly Outage Reports

Problems reported by engineers using fiskaly. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No fiskaly problems reported yet.

Something wrong with fiskaly on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About fiskaly

fiskaly posts its status at status.fiskaly.com. The page covers 21 components, among them SIGN AT, E-INVOICE BE and SIGN FR. Past incidents and uptime for fiskaly stay on this page, which helps when you want to know how often it has trouble.

fiskaly Status FAQ

Is fiskaly down right now?

The verdict at the top of this page comes from the latest poll of the official fiskaly status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if fiskaly is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until fiskaly recovers.

How do I check fiskaly uptime history?

PulsAPI tracks fiskaly uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever fiskaly changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect fiskaly outages?

PulsAPI reads the official fiskaly status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual fiskaly components?

Yes. PulsAPI monitors 21 individual fiskaly components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when fiskaly goes down?

Yes. Create a free account and subscribe to fiskaly: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with fiskaly to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot fiskaly problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor fiskaly?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so fiskaly plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track fiskaly with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services