Live  /  Providers  /  Visma Cloud Services

Visma Cloud Services

visma.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Visma Cloud Services. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks Visma Cloud Services’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Visma Cloud Services is reporting

Current & recent incidents

Resolved

[Auto] Archive availability degraded

Major impact · 2026-09-24 01:31 UTC

Resolved

[Auto] Interco availability degraded

Major impact · 2026-09-23 20:45 UTC

Resolved

[Auto] Integretionmicrosoft365 availability degraded

Major impact · 2026-09-23 20:45 UTC

Resolved

[Auto] Thirdpartyreference availability degraded

Major impact · 2026-09-22 19:14 UTC

Resolved

[Auto] Stability availability degraded

Major impact · 2026-09-22 19:13 UTC

Resolved

[Auto] Research availability degraded

Major impact · 2026-09-22 19:13 UTC

Resolved

Numo outage

Critical impact · 2026-09-21 08:12 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Visma Cloud Services has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Visma Cloud Services runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Visma Cloud Services is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Visma Cloud Services.