Tracked subprocessors 0 Subprocessor of 1 Third parties loaded 1 Loaded by 0
+ − ⟲
No tracked subprocessors.
Not loaded by any published homepage.
Subprocessors None extracted.
fiskaly's homepage made 55 requests to 2 domains, and 1 service controlled by another company.
Unclassified (1): no technology detected from them: Conversion Expert GmbH (ABlyft) 1 third party by category: Unclassified 1
Third parties 1 · 1 request
Conversion Expert GmbH (ABlyft) ablyft.com 2% of the page's requests 1
First party 1 · 54 requests
fiskaly ABLyft HSTS Headless UI Netlify Next.js 16.1.6 Open Graph PWA React Turbopack Webpack 98% of the page's requests 54
Aug 24: no incident reported Aug 25: no incident reported Aug 26: no incident reported Aug 27: no incident reported Aug 28: no incident reported Aug 29: no incident reported Aug 30: no incident reported Aug 31: no incident reported Sep 1: no incident reported Sep 2: no incident reported Sep 3: 1 incident (1 minor) Sep 4: no incident reported Sep 5: no incident reported Sep 6: no incident reported Sep 7: no incident reported Sep 8: no incident reported Sep 9: no incident reported Sep 10: no incident reported Sep 11: no incident reported Sep 12: no incident reported Sep 13: no incident reported Sep 14: no incident reported Sep 15: no incident reported Sep 16: no incident reported Sep 17: no incident reported Sep 18: 1 incident (1 minor) Sep 19: no incident reported Sep 20: no incident reported Sep 21: no incident reported Sep 22: no incident reported Sep 23: no incident reported Sep 24: no incident reported Sep 25: no incident reported Sep 26: no incident reported Sep 27: no incident reported Sep 28: no incident reported Sep 29: no incident reported Sep 30: no incident reported Oct 1: no incident reported Oct 2: no incident reported Oct 3: no incident reported Oct 4: no incident reported Oct 5: no incident reported Oct 6: no incident reported Oct 7: no incident reported Oct 8: 2 incidents (2 minor) Oct 9: 1 incident (1 minor) Oct 10: no incident reported Oct 11: 1 incident (1 minor) Oct 12: no incident reported Oct 13: no incident reported Oct 14: no incident reported Oct 15: no incident reported Oct 16: no incident reported Oct 17: no incident reported Oct 18: no incident reported Oct 19: no incident reported Oct 20: 1 incident (1 minor) Oct 21: no incident reported Oct 22: no incident reported Oct 23: 2 incidents (1 major, 1 no impact stated) Oct 24: no incident reported Oct 25: no incident reported Oct 26: 1 incident (1 no impact stated) Oct 27: no incident reported Oct 28: 1 incident (1 no impact stated) Oct 29: no incident reported Oct 30: no incident reported Oct 31: no incident reported Nov 1: no incident reported Nov 2: 1 incident (1 minor) Nov 3: no incident reported Nov 4: no incident reported Nov 5: no incident reported Nov 6: no incident reported Nov 7: no incident reported Nov 8: no incident reported Nov 9: no incident reported Nov 10: no incident reported Nov 11: no incident reported Nov 12: no incident reported Nov 13: no incident reported Nov 14: no incident reported Nov 15: no incident reported Nov 16: no incident reported Nov 17: no incident reported Nov 18: 2 incidents (2 no impact stated) Nov 19: 1 incident (1 minor) Nov 20: no incident reported Nov 21: no incident reported 90 days ago today
15 incidents in 90 days1 major or critical3 h 35 min typical time to resolve29 min longest majorIncidents per month 0 5 10 Dec 2025: 1 incident (1 no impact stated) Jan 2026: 1 incident (1 minor) · typical time to resolve 5 days Feb 2026: 5 incidents (4 minor, 1 no impact stated) · typical time to resolve 8 h 9 min Mar 2026: 2 incidents (1 minor, 1 no impact stated) · typical time to resolve 1 h 31 min Apr 2026: 2 incidents (1 minor, 1 no impact stated) · typical time to resolve 1 h 28 min May 2026: 2 incidents (2 minor) · typical time to resolve 3 days Jun 2026: 4 incidents (3 minor, 1 no impact stated) · typical time to resolve 43 min Jul 2026: 2 incidents (1 minor, 1 no impact stated) · typical time to resolve 1 h 41 min Aug 2026: 2 incidents (2 no impact stated) · typical time to resolve 6 h 58 min Sep 2026: 2 incidents (2 minor) · typical time to resolve 2 h 26 min Oct 2026: 9 incidents (1 major, 5 minor, 3 no impact stated) · typical time to resolve 3 h 35 min Nov 2026: 4 incidents (2 minor, 2 no impact stated) · typical time to resolve 24 h 29 min Dec 2025 Jan 2026 Feb Mar Apr May Jun Jul Aug Sep Oct Nov critical major minor no impact stated
Components affected Component Incidents Bar SIGN IT 7 SIGN DE 4 SIGN AT 1 SIGN ES 1 SIGN FR 1 SIGN PT 1
As fiskaly's status page reports its own incidents (scheduled maintenance left out), read every few hours since Oct 7, 2025 (evidence )
None since tracking began.