Vendor Status Watch

← all vendors

Visma status history

Current state: partial outage — “Partial System Outage” per https://status.visma.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

26incidents, last 30 days
55incidents, last 90 days
55incidents on record
Incidents per week, last 12 weeks:

How long do Visma incidents last?

11 minmedian incident duration55 measured
8.7 h90th percentile1 in 10 ran longer
11 minmedian, major/critical only44 incidents

From 55 incidents with a vendor-posted start and resolve time. Longest on record: Maventa: Problems with Peppol sends and lookups in Norway — 47.1 h (2026-08-03 06:46 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (55)

StartedIncidentStatusImpactDuration
2026-09-14 09:44 UTC[Auto] Inqom Api availability degradedresolvedmajor9 min
2026-09-14 09:35 UTC[Auto] Accounting availability degradedresolvedmajor17 min
2026-09-14 09:22 UTC[Auto] Inqom Api availability degradedresolvedmajor19 min
2026-09-11 09:18 UTC[Auto] Fscp availability degradedresolvedmajor11 min
2026-09-11 05:26 UTCDashboard component causing errors or not openingresolvedminor3 h 32 min
2026-09-03 07:48 UTCWinvoice Downpostmortemcritical0 min
2026-09-01 20:21 UTC[Auto] Accounting documents availability degradedresolvedmajor7 min
2026-08-31 19:58 UTCFlyt Inschool - Login with IdPorten and Feide is unavailableresolvednone38 min
2026-08-31 06:26 UTCDriftsavvik: Ustabilitet på Amazon WorkSpaces Applicationsresolvedminor6 h 18 min
2026-08-30 02:23 UTC[Auto] Stability availability degradedresolvedmajor8 min
2026-08-30 02:22 UTC[Auto] Marketplace availability degradedresolvedmajor9 min
2026-08-30 02:22 UTC[Auto] Integretionmicrosoft365 availability degradedresolvedmajor10 min
2026-08-30 02:22 UTC[Auto] Interco availability degradedresolvedmajor11 min
2026-08-30 02:22 UTC[Auto] Billing availability degradedresolvedmajor3 h 16 min
2026-08-30 02:21 UTC[Auto] Archive availability degradedresolvedmajor11 min
2026-08-30 02:21 UTC[Auto] Accounting availability degradedresolvedmajor1 h 12 min
2026-08-30 02:21 UTC[Auto] Inqom Api availability degradedresolvedmajor1 h 12 min
2026-08-30 02:21 UTC[Auto] Revision availability degradedresolvedmajor3 h 16 min
2026-08-27 14:53 UTCDegraded performance for Enterprise plusresolvedminor5 min
2026-08-26 10:03 UTCSmartscan - major outageresolvedcritical2 h 31 min
2026-08-26 08:53 UTCVisma Hop Authentication and DLP degraded performanceresolvedminor3 h 02 min
2026-08-26 07:30 UTCDegraded performance in Visma net after release of 11.0.9postmortemnone4 h 21 min
2026-08-26 06:38 UTCDriftsmelding: Vedvarende utfordringer med Id-Portenresolvednone28 h 45 min
2026-08-24 06:13 UTCMaventa: Problems with Peppol sends and lookups in Norwayresolvedminor3 h 52 min
2026-08-19 09:02 UTCIssue in Business NXTresolvedmajor3 h 06 min
2026-08-17 21:30 UTCInvestigating an incident on Networkresolvedmajor14 h 00 min
2026-08-16 02:14 UTC[Auto] Silae availability degradedresolvedmajor7 min
2026-08-16 02:11 UTC[Auto] Factofrance availability degradedresolvedmajor11 min
2026-08-15 02:15 UTC[Auto] Meg availability degradedresolvedmajor8 min
2026-08-15 02:13 UTC[Auto] Factofrance availability degradedresolvedmajor10 min
2026-08-15 02:13 UTC[Auto] Silae availability degradedresolvedmajor10 min
2026-08-11 12:52 UTCInvestigating an issue in InSchoolresolvedminor19 h 58 min
2026-08-10 09:30 UTCSite unavailable (invalid certificate)resolvedmajor0 min
2026-08-09 23:34 UTC[Auto] Inqom Api availability degradedresolvedmajor11 min
2026-08-09 23:33 UTC[Auto] Interco availability degradedresolvedmajor9 min
2026-08-09 23:33 UTC[Auto] Dashboard availability degradedresolvedmajor6 min
2026-08-09 23:32 UTC[Auto] Revision availability degradedresolvedmajor8 h 36 min
2026-08-09 23:32 UTC[Auto] Integretionmicrosoft365 availability degradedresolvedmajor9 min
2026-08-09 23:32 UTC[Auto] Marketplace availability degradedresolvedmajor9 min
2026-08-09 23:32 UTC[Auto] Billing availability degradedresolvedmajor8 h 39 min
2026-08-09 23:31 UTC[Auto] Archive availability degradedresolvedmajor11 min
2026-08-09 23:31 UTC[Auto] Accounting documents availability degradedresolvedmajor11 min
2026-08-08 02:27 UTC[Auto] Meg availability degradedresolvedmajor11 min
2026-08-08 02:11 UTC[Auto] Silae availability degradedresolvedmajor9 min
2026-08-08 02:10 UTC[Auto] Factofrance availability degradedresolvedmajor10 min
2026-08-08 02:10 UTC[Auto] Meg availability degradedresolvedmajor8 min
2026-08-05 02:13 UTC[Auto] Silae availability degradedresolvedmajor6 min
2026-08-05 02:10 UTC[Auto] Factofrance availability degradedresolvedmajor10 min
2026-08-05 02:10 UTC[Auto] Meg availability degradedresolvedmajor11 min
2026-08-03 08:58 UTCFlyt Inschool - ID-porten is unavailableresolvednone4 h 19 min
2026-08-03 06:46 UTCMaventa: Problems with Peppol sends and lookups in Norwayresolvedminor47 h 04 min
2026-07-31 02:11 UTC[Auto] Meg availability degradedresolvedmajor6 min
2026-07-31 02:11 UTC[Auto] Silae availability degradedresolvedmajor13 min
2026-07-31 02:09 UTC[Auto] Factofrance availability degradedresolvedmajor11 min
2026-07-30 11:52 UTCInvestigating an issue in Business NXTresolvedmajor18 h 42 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Visma with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "visma"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}