← HonkWatch.com

Is Visma down in Belgium?

Planned maintenance at Visma

People in Belgium: 0 reports in the last hour Official page: Planned maintenance, checked 6 min ago Our checks: loads from 35 of 35 places
Visma has planned maintenance. Maintenance on Enterprise Plus / Enterprise Plus, Flyt Welfare & Health / Flyt PPT, Flyt Welfare & Health / Flyt Barnevernvakt and 3 more. Updated 7 Nov, 22:41 UTC, 6 min ago · Official status page
Report a problem
Change country

Known issues (from Visma Cloud Services's status page)

Maintenance

  • Enterprise Plus - Scheduled Infrastructure Security Upgrade (under way) 7 Nov, 19:00 UTC to 8 Nov, 00:00 UTC. Affects Enterprise Plus · Details Latest update (7 Nov, 19:01 UTC): Scheduled maintenance is currently in progress. We will provide updates as necessary.
  • Scheduled Maintenance - Flyt Common MariaDB Database Upgrade - 2 (under way) 7 Nov, 19:00 UTC to 8 Nov, 00:00 UTC. Affects Flyt PPT, Flyt Barnevernvakt, Flyt Helse, Flyt Sikker Sak and 1 more · Details Latest update (7 Nov, 19:00 UTC): Scheduled maintenance is currently in progress. We will provide updates as necessary.
  • Scheduled maintenance for Visma Scanner Backend (planned) 10 Nov, 06:00 UTC to 10 Nov, 12:00 UTC. Affects Visma Scanner · Details Latest update (2 Nov, 13:58 UTC): We will be undergoing scheduled maintenance for the Azure SQL Database during this time. Expected downtime is 30 seconds.
Show 3 more maintenance windows
  • Scheduled maintenance for Payroll Norway (planned) 10 Nov, 19:00 UTC to 10 Nov, 23:00 UTC. Affects Visma.net Payroll Norway · Details Latest update (29 Oct, 07:27 UTC): We will be undergoing scheduled maintenance during this time, the system might be somewhat slower than usual. (xco)
  • Scheduled maintenance for Visma Connect (planned) 18 Nov, 00:00 UTC to 18 Nov, 02:00 UTC. Affects CP - Visma Connect · Details Latest update (5 Nov, 11:53 UTC): We will perform database changes where we expect 2 minutes of downtime. Signin with Visma Net, Visma Online, Visma Severa, Visma Community, e-conomic and others will be affected.
  • Scheduled maintenance for Visma Connect (planned) 16 Dec 2026, 00:00 UTC to 16 Dec 2026, 03:00 UTC. Affects CP - Visma Connect · Details Latest update (5 Nov, 10:01 UTC): We will perform database changes where we expect 10 minutes of downtime. Signin with Visma Net, Visma Online, Visma Severa, Visma Community, e-conomic and others will be affected.

In Visma Cloud Services's own words, as we read them every 7.5 minutes, last 6 min ago. Read Visma Cloud Services's status page

Reports from people in Belgium

Last 24 hours · Belgium · times in UTC

0 reports

No community reports in the last 24 hours from Belgium. Having trouble? Add your report.

Status page: maintenance, 08:01 to 10:00 UTCStatus page: maintenance, 19:07 to now 024 00:0006:0012:0018:00 23:00-23:05 UTC: 35 of 35 places loaded it, typical 199 ms23:05-23:10 UTC: 34 of 34 places loaded it, typical 180 ms23:10-23:15 UTC: 35 of 35 places loaded it, typical 206 ms23:15-23:20 UTC: 34 of 34 places loaded it, typical 178 ms23:20-00:15 UTC: 35 of 35 places loaded it, typical 182 to 254 ms00:15-00:20 UTC: 34 of 34 places loaded it, typical 200 ms00:20-01:45 UTC: 35 of 35 places loaded it, typical 174 to 210 ms01:45-01:50 UTC: 34 of 34 places loaded it, typical 186 ms01:50-03:35 UTC: 35 of 35 places loaded it, typical 183 to 271 ms03:35-03:40 UTC: 34 of 34 places loaded it, typical 197 ms03:40-05:00 UTC: 35 of 35 places loaded it, typical 184 to 278 ms05:00-05:05 UTC: 34 of 34 places loaded it, typical 192 ms05:05-06:00 UTC: 35 of 35 places loaded it, typical 179 to 239 ms06:00-06:05 UTC: 34 of 34 places loaded it, typical 189 ms06:05-07:25 UTC: 35 of 35 places loaded it, typical 180 to 212 ms07:25-07:30 UTC: 34 of 34 places loaded it, typical 186 ms07:30-08:30 UTC: 35 of 35 places loaded it, typical 183 to 238 ms08:30-08:35 UTC: 34 of 34 places loaded it, typical 199 ms08:35-09:15 UTC: 35 of 35 places loaded it, typical 193 to 226 ms09:15-09:20 UTC: 34 of 34 places loaded it, typical 200 ms09:20-10:00 UTC: 35 of 35 places loaded it, typical 189 to 224 ms10:00-10:05 UTC: 34 of 34 places loaded it, typical 186 ms10:05-10:55 UTC: 35 of 35 places loaded it, typical 183 to 212 ms10:55-11:00 UTC: 34 of 34 places loaded it, typical 220 ms11:00-11:30 UTC: 35 of 35 places loaded it, typical 190 to 202 ms11:30-11:35 UTC: 34 of 34 places loaded it, typical 186 ms11:35-12:15 UTC: 35 of 35 places loaded it, typical 186 to 224 ms12:15-12:20 UTC: 34 of 34 places loaded it, typical 203 ms12:20-12:50 UTC: 35 of 35 places loaded it, typical 193 to 218 ms12:50-12:55 UTC: 34 of 34 places loaded it, typical 199 ms12:55-13:15 UTC: 35 of 35 places loaded it, typical 196 to 219 ms13:15-13:20 UTC: 34 of 34 places loaded it, typical 216 ms13:20-13:45 UTC: 35 of 35 places loaded it, typical 186 to 236 ms13:45-13:50 UTC: 34 of 34 places loaded it, typical 230 ms13:50-14:40 UTC: 35 of 35 places loaded it, typical 189 to 225 ms14:40-14:45 UTC: 34 of 34 places loaded it, typical 208 ms14:45-15:45 UTC: 35 of 35 places loaded it, typical 190 to 233 ms15:45-15:50 UTC: 34 of 34 places loaded it, typical 244 ms15:50-17:05 UTC: 35 of 35 places loaded it, typical 206 to 241 ms17:05-17:10 UTC: 34 of 34 places loaded it, typical 213 ms17:10-18:15 UTC: 35 of 35 places loaded it, typical 200 to 240 ms18:15-18:20 UTC: 34 of 34 places loaded it, typical 200 ms18:20-18:50 UTC: 35 of 35 places loaded it, typical 190 to 229 ms18:50-18:55 UTC: 34 of 34 places loaded it, typical 215 ms18:55-19:05 UTC: 35 of 35 places loaded it, typical 214 to 220 ms19:05-19:10 UTC: 34 of 34 places loaded it, typical 212 ms19:10-19:30 UTC: 35 of 35 places loaded it, typical 198 to 223 ms19:30-19:35 UTC: 34 of 34 places loaded it, typical 202 ms19:35-20:15 UTC: 35 of 35 places loaded it, typical 191 to 236 ms20:15-20:20 UTC: 34 of 34 places loaded it, typical 211 ms20:20-20:40 UTC: 35 of 35 places loaded it, typical 194 to 201 ms20:40-20:45 UTC: 34 of 34 places loaded it, typical 216 ms20:45-21:30 UTC: 35 of 35 places loaded it, typical 185 to 213 ms21:30-21:35 UTC: 34 of 34 places loaded it, typical 202 ms21:35-22:35 UTC: 35 of 35 places loaded it, typical 183 to 241 ms22:35-22:40 UTC: 34 of 34 places loaded it, typical 189 ms22:40-22:45 UTC: 35 of 35 places loaded it, typical 190 ms22:45-22:50 UTC: 30 of 30 places loaded it, typical 177 ms Typical response time of the places that loaded it, at most 278 ms

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Tinted columns: when Visma's status page showed a partial outage, a major outage or maintenance, as we read it every 7.5 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded visma.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Belgium only.

Latest checks, 22:45-22:50 UTC: 30 of 30 places loaded it, typical 177 ms.

Report totals as of 7 Nov, 22:46 UTC

Report a problem with Visma

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Belgium

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Belgium. The report chart above is filtered to Belgium.

Our own checks of visma.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Dallas: loaded in 262 ms Sydney: loaded in 336 ms Santiago: loaded in 150 ms Port Louis: loaded in 231 ms Tokyo: loaded in 166 ms Frankfurt: loaded in 179 ms Melbourne: loaded in 313 ms Jakarta: loaded in 268 ms Los Angeles: loaded in 395 ms Atlanta: loaded in 149 ms Warsaw: loaded in 154 ms Madrid: loaded in 156 ms Toronto: loaded in 168 ms Delhi: loaded in 149 ms Bangalore: loaded in 228 ms Hong Kong: loaded in 150 ms Mumbai: loaded in 176 ms Osaka: loaded in 166 ms Johannesburg: loaded in 156 ms São Paulo: loaded in 180 ms Doha: loaded in 920 ms Seattle: loaded in 175 ms Querétaro: loaded in 169 ms London: loaded in 193 ms Lauterbourg: loaded in 176 ms Seoul: loaded in 231 ms Amsterdam: loaded in 162 ms Cape Town: loaded in 202 ms Hamina: loaded in 198 ms St. Louis: loaded in 313 ms Tel Aviv: loaded in 474 ms Portsmouth: loaded in 251 ms New Jersey: loaded in 396 ms New York: loaded in 165 ms Singapore: loaded in 177 ms
  • DallasReachable262 ms, just now
  • SydneyReachable336 ms, just now
  • SantiagoReachable150 ms, just now
  • Port LouisReachable231 ms, just now
  • TokyoReachable166 ms, just now
  • FrankfurtReachable179 ms, just now
  • MelbourneReachable313 ms, just now
  • JakartaReachable268 ms, just now
  • Los AngelesReachable395 ms, just now
  • AtlantaReachable149 ms, just now
  • WarsawReachable154 ms, just now
  • MadridReachable156 ms, just now
  • TorontoReachable168 ms, just now
  • DelhiReachable149 ms, just now
  • BangaloreReachable228 ms, just now
  • Hong KongReachable150 ms, just now
  • MumbaiReachable176 ms, just now
  • OsakaReachable166 ms, just now
  • JohannesburgReachable156 ms, 1 min ago
  • São PauloReachable180 ms, 1 min ago
  • DohaReachable920 ms, 1 min ago
  • SeattleReachable175 ms, 1 min ago
  • QuerétaroReachable169 ms, 1 min ago
  • LondonReachable193 ms, 1 min ago
  • LauterbourgReachable176 ms, 1 min ago
  • SeoulReachable231 ms, 1 min ago
  • AmsterdamReachable162 ms, 1 min ago
  • Cape TownReachable202 ms, 2 min ago
  • HaminaReachable198 ms, 2 min ago
  • St. LouisReachable313 ms, 2 min ago
  • Tel AvivReachable474 ms, 5 min ago
  • PortsmouthReachable251 ms, 5 min ago
  • New JerseyReachable396 ms, 5 min ago
  • New YorkReachable165 ms, 5 min ago
  • SingaporeReachable177 ms, 5 min ago

This is separate from the status page: we request visma.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Visma

Visma Cloud Services

Enterprise Plus

  • Enterprise PlusMaintenance

Flyt Welfare & Health

  • Flyt PPTMaintenance
  • Flyt BarnevernvaktMaintenance
  • Flyt HelseMaintenance
  • Flyt Sikker SakMaintenance
  • Flyt BarnevernMaintenance

384 other parts are working.

Incidents and maintenance

Maintenance

  • Enterprise Plus - Scheduled Infrastructure Security Upgrade (now) 7 Nov, 19:00 UTC to 8 Nov, 00:00 UTC. Affects Enterprise Plus · Details
  • Scheduled Maintenance - Flyt Common MariaDB Database Upgrade - 2 (now) 7 Nov, 19:00 UTC to 8 Nov, 00:00 UTC. Affects Flyt PPT, Flyt Barnevernvakt, Flyt Helse, Flyt Sikker Sak and 1 more · Details
  • Scheduled maintenance for Visma Scanner Backend (planned) 10 Nov, 06:00 UTC to 10 Nov, 12:00 UTC. Affects Visma Scanner · Details
  • Scheduled maintenance for Payroll Norway (planned) 10 Nov, 19:00 UTC to 10 Nov, 23:00 UTC. Affects Visma.net Payroll Norway · Details
  • Scheduled maintenance for Visma Connect (planned) 18 Nov, 00:00 UTC to 18 Nov, 02:00 UTC. Affects CP - Visma Connect · Details
  • Scheduled maintenance for Visma Connect (planned) 16 Dec 2026, 00:00 UTC to 16 Dec 2026, 03:00 UTC. Affects CP - Visma Connect · Details
Outage history

Last problem: 5 Nov, 14:21 UTC, partial outage for 5 h 9 min (Open incident: Investigating issue on Flyt Skole production).

Last 9030 days

56.98% of the time without a reported outage, since 2 Nov

Of the last 90 days, 4 had a partial or major outage, 2 had maintenance only and 84 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Recent problems

5 Nov, 14:21 UTCPartial outage5 h 9 minOpen incident: Investigating issue on Flyt Skole production
5 Nov, 10:17 UTCPartial outage2 h 25 minOpen incident: Degraded performance in Business NXT migration
4 Nov, 09:12 UTCPartial outage23 hOpen incident: Degraded performance in Flyt Foresatt
2 Nov, 13:35 UTCPartial outage1 d1 of 390 parts affected: Visma Net / Visma Net
What can I try?

Having trouble with Visma?

  1. Compare reports from Belgium and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Visma down, or is it just me?

Visma is doing planned maintenance, so some parts may not work right now. It is probably not just you.

How do we know?

We read the official Visma status page and load visma.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 7.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Other services in Finance and accounting

Each card shows that service's own status, not Visma's. A problem listed here does not mean Visma has one.

See the live outage feed for Belgium · Find another service