Outage in Fiskaly
Authentication Server high CPU load
Resolved MinorIncident Report
The last Authentication Server Maintenance has caused a high CPU load which effects all services besides the authentication service itself.
Need to monitor Fiskaly outages?
- Monitor all your external dependencies in one place
- Get instant alerts when outages are detected
- Be the first to know if service is down
- Show real-time status on private or public status page
- Keep your team informed
Latest Updates ( sorted recent to last )
RESOLVED
3 months ago - at 11/10/2025 01:46PM
The issue was a unexpected high CPU load after a configuration change on the authentication server side.
As a result, affected clients may receive 401 Unauthorized responses.
In such cases, please generate a new token using your API key and API secret.
We appreciate your understanding and apologize for any inconvenience caused.
INVESTIGATING
3 months ago - at 11/10/2025 12:55PM
The last Authentication Server Maintenance has caused a high CPU load which effects all services besides the authentication service itself.
Latest Fiskaly outages
SIGN IT - Increased 500 and timeout errors - about 7 hours ago
SIGN DE v2 degraded performance on signing requests - 3 months ago
SIGN DE v2 degraded performance on signing requests - 3 months ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 5850 services available
Integrations with
