Tracked subprocessors 0 Subprocessor of 0 Third parties loaded 3 Loaded by 0
+ − ⟲
No tracked subprocessors.
Not listed by any tracked vendor.
Not loaded by any published homepage.
Subprocessors None extracted.
Visma's homepage made 43 requests to 6 domains, and 3 services controlled by another company.
Cookie compliance (1): OneTrust CDN (1): jsDelivr Other (1): JavaScript libraries: Webflow 3 third parties by category: 1 1 1
Third parties 3 · 38 requests
Webflow Webflow 1.6.0 jQuery 3.5.1 58% of the page's requests 25 OneTrust OneTrust 26% of the page's requests 11 jsDelivr jsDelivr 5% of the page's requests 2 First party 1 · 5 requests
Visma Cloudflare GSAP 3.15.0 HSTS Open Graph Webflow Ecommerce Webpack 12% of the page's requests 5
3 tracked companies loaded by the homepage are not in Visma's subprocessor list. A website can use a service without it processing customer data.
Aug 15: 3 incidents (3 major) Aug 16: 2 incidents (2 major) Aug 17: no incident reported Aug 18: 1 incident (1 major) Aug 19: 1 incident (1 major) Aug 20: no incident reported Aug 21: no incident reported Aug 22: no incident reported Aug 23: no incident reported Aug 24: 1 incident (1 minor) Aug 25: no incident reported Aug 26: 4 incidents (1 critical, 1 minor, 2 no impact stated) Aug 27: 1 incident (1 minor) Aug 28: no incident reported Aug 29: no incident reported Aug 30: 9 incidents (9 major) Aug 31: 2 incidents (1 minor, 1 no impact stated) Sep 1: 1 incident (1 major) 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 minor) Sep 12: no incident reported Sep 13: no incident reported Sep 14: 3 incidents (3 major) Sep 15: no incident reported Sep 16: no incident reported Sep 17: 1 incident (1 minor) Sep 18: no incident reported Sep 19: no incident reported Sep 20: no incident reported Sep 21: 1 incident (1 critical) Sep 22: 3 incidents (3 major) Sep 23: 6 incidents (6 major) Sep 24: no incident reported Sep 25: 1 incident (1 minor) Sep 26: no incident reported Sep 27: no incident reported Sep 28: no incident reported Sep 29: 1 incident (1 major) Sep 30: no incident reported Oct 1: 5 incidents (3 major, 1 minor, 1 no impact stated) Oct 2: no incident reported Oct 3: no incident reported Oct 4: no incident reported Oct 5: 2 incidents (2 major) Oct 6: 1 incident (1 minor) Oct 7: 2 incidents (1 minor, 1 no impact stated) Oct 8: 1 incident (1 major) Oct 9: no incident reported Oct 10: no incident reported Oct 11: no incident reported Oct 12: 3 incidents (2 major, 1 minor) Oct 13: 1 incident (1 no impact stated) Oct 14: no incident reported Oct 15: no incident reported Oct 16: 1 incident (1 major) Oct 17: no incident reported Oct 18: no incident reported Oct 19: no incident reported Oct 20: no incident reported Oct 21: 1 incident (1 no impact stated) Oct 22: no incident reported Oct 23: no incident reported Oct 24: 1 incident (1 major) Oct 25: 6 incidents (6 major) Oct 26: no incident reported Oct 27: 1 incident (1 major) Oct 28: 1 incident (1 minor) Oct 29: no incident reported Oct 30: 1 incident (1 minor) Oct 31: 14 incidents (1 critical, 13 major) Nov 1: no incident reported Nov 2: 4 incidents (1 critical, 3 minor) Nov 3: no incident reported Nov 4: 1 incident (1 minor) Nov 5: 2 incidents (1 critical, 1 minor) Nov 6: no incident reported Nov 7: no incident reported Nov 8: no incident reported Nov 9: 2 incidents (1 major, 1 minor) Nov 10: 1 incident (1 major) Nov 11: 2 incidents (2 minor) Nov 12: no incident reported 90 days ago today
97 incidents in 90 days69 major or critical31 min typical time to resolve6 days longest majorIncidents per month 0 25 50 Dec 2025: 30 incidents (3 critical, 9 major, 14 minor, 4 no impact stated) · typical time to resolve 2 h 56 min Jan 2026: 11 incidents (2 critical, 5 major, 2 minor, 2 no impact stated) · typical time to resolve 3 h 58 min Feb 2026: 12 incidents (2 critical, 1 major, 7 minor, 2 no impact stated) · typical time to resolve 1 h 48 min Mar 2026: 30 incidents (4 critical, 12 major, 8 minor, 6 no impact stated) · typical time to resolve 3 h 59 min Apr 2026: 19 incidents (1 critical, 7 major, 10 minor, 1 no impact stated) · typical time to resolve 2 h 5 min May 2026: 18 incidents (1 critical, 8 major, 7 minor, 2 no impact stated) · typical time to resolve 1 h 34 min Jun 2026: 18 incidents (3 major, 13 minor, 2 no impact stated) · typical time to resolve 5 h 44 min Jul 2026: 14 incidents (1 critical, 12 major, 1 minor) · typical time to resolve 25 min Aug 2026: 44 incidents (1 critical, 33 major, 6 minor, 4 no impact stated) · typical time to resolve 11 min Sep 2026: 20 incidents (2 critical, 15 major, 3 minor) · typical time to resolve 10 min Oct 2026: 41 incidents (1 critical, 30 major, 6 minor, 4 no impact stated) · typical time to resolve 31 min Nov 2026: 12 incidents (2 critical, 2 major, 8 minor) · typical time to resolve 2 h 25 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 Archive 5 Visma.net Payroll Norway 5 Billing 4 Interco 4 Stability 4 Visma Net 4 Integretionmicrosoft365 3 Marketplace 3
As Visma's status page reports its own incidents (scheduled maintenance left out), read every few hours since Oct 1, 2025 (evidence )
None since tracking began.
Visma