Tracked subprocessors 0 Subprocessor of 1 Third parties loaded 3 Loaded by 0
+ − ⟲
No tracked subprocessors.
Not loaded by any published homepage.
Subprocessors None extracted.
Fortnox's homepage made 48 requests to 4 domains, and 3 services controlled by another company.
Analytics (2): Piwik PRO, Google Cloud Other (1): reviewed as CMS: Storyblok 3 third parties by category: Analytics 2 Other 1
Third parties 3 · 15 requests
Storyblok storyblok.com 23% of the page's requests 11 Piwik PRO Piwik PRO Core 6% of the page's requests 3
Google Cloud Google Analytics Google Tag Manager 2% of the page's requests 1 First party 1 · 33 requests
Fortnox Font Awesome GSAP HSTS Next.js 16.3.8 Next.js App Router Open Graph PWA Priority Hints React Storyblok Turbopack Vimeo Webpack 69% of the page's requests 33
2 tracked companies loaded by the homepage are not in Fortnox's subprocessor list. A website can use a service without it processing customer data.
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 critical) 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: 2 incidents (1 major, 1 no impact stated) 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: 2 incidents (1 major, 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: 1 incident (1 major) Sep 26: no incident reported Sep 27: no incident reported Sep 28: 1 incident (1 major) Sep 29: no incident reported Sep 30: 1 incident (1 major) Oct 1: 1 incident (1 minor) Oct 2: 1 incident (1 major) 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: no incident reported Oct 9: no incident reported Oct 10: no incident reported Oct 11: no incident reported Oct 12: no incident reported Oct 13: no incident reported Oct 14: no incident reported Oct 15: 1 incident (1 critical) Oct 16: no incident reported Oct 17: no incident reported Oct 18: no incident reported Oct 19: 1 incident (1 minor) Oct 20: no incident reported Oct 21: no incident reported Oct 22: no incident reported Oct 23: no incident reported Oct 24: no incident reported Oct 25: no incident reported Oct 26: 1 incident (1 major) Oct 27: no incident reported Oct 28: no incident reported 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: 1 incident (1 critical) Nov 14: no incident reported Nov 15: no incident reported Nov 16: no incident reported Nov 17: no incident reported Nov 18: no incident reported Nov 19: no incident reported Nov 20: no incident reported Nov 21: no incident reported 90 days ago today
15 incidents in 90 days10 major or critical3 h 53 min typical time to resolve3 days longest majorIncidents per month 0 5 10 Dec 2025: 9 incidents (1 critical, 4 major, 2 minor, 2 no impact stated) · typical time to resolve 3 h 56 min Jan 2026: 4 incidents (2 minor, 2 no impact stated) · typical time to resolve 3 h 5 min Feb 2026: 3 incidents (3 no impact stated) · typical time to resolve 2 h 14 min Mar 2026: 10 incidents (1 critical, 4 major, 1 minor, 4 no impact stated) · typical time to resolve 2 h 41 min Apr 2026: 2 incidents (2 major) · typical time to resolve 4 h 31 min May 2026: 5 incidents (2 critical, 3 minor) · typical time to resolve 3 h 12 min Jun 2026: 2 incidents (1 major, 1 no impact stated) · typical time to resolve 5 h 14 min Jul 2026: 1 incident (1 no impact stated) · typical time to resolve 21 h 34 min Aug 2026: 1 incident (1 critical) · typical time to resolve 4 h 19 min Sep 2026: 8 incidents (1 critical, 5 major, 1 minor, 1 no impact stated) · typical time to resolve 7 h 42 min Oct 2026: 5 incidents (1 critical, 2 major, 2 minor) · typical time to resolve 3 h 47 min Nov 2026: 2 incidents (1 critical, 1 minor) · typical time to resolve 3 h 38 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 Fakturering 5 Bokföring 4 Fortnox inloggning 4 Lön 3 Fakturaköp 2 Fakturaservice 2 Fortnox ID 2 Leverantörsfakturaattest 2
As Fortnox's status page reports its own incidents (scheduled maintenance left out), read every few hours since Nov 3, 2025 (evidence )
None since tracking began.