Is Visma down?

Last checked 11m ago
Current status
Visma is having a partial outage

6 active incidents: Investigating an issue in Visma Directe Bankkoppeling, Investigating an issue in AccountView.Net · +4 more

Get alerts when Visma breaks →

Free · no credit card

Official status page: https://status.visma.com · Polled every 5 minutes · 386 components tracked

Real-time Visma status, recent outages, and incident history — pulled directly from Visma's official status page at https://status.visma.com every 5 minutes. Pingoru tracks 386 Visma services and has captured 50 incidents in the last 90 days (99.71% uptime). Get email, Slack, Discord, or webhook alerts the moment Visma reports a new incident — free for 5 monitors, no credit card.

Users who monitor Visma also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Visma uptime 99.71% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Investigating an issue in Visma Directe Bankkoppeling
    Ongoing ● 3h 23m
    Started Apr 29, 2026, 03:07 PM UTC
    CS - Visma Directe bankkoppeling
    1 update · show timeline
    • identified · Apr 29, 2026, 03:07 PM UTC

      We are currently experiencing issues while retrieving data from the Chamber of Commerce. Customer who try to connect bank accounts of PSD2-connections will notice errors about the Chamber of Commerce being unavailable. There is no impact to any of the already connected bank accounts. We are working with the Chamber of Commerce to resolve the problem

    Latest: We are currently experiencing issues while retrieving data from the Chamber of Commerce. Customer who try to connect bank accounts of PSD2-connections will notice errors about the …

  2. Investigating an issue in AccountView.Net
    Ongoing ● 3h 26m
    Started Apr 29, 2026, 03:04 PM UTC
    CS - AccountView.Net
    1 update · show timeline
    • identified · Apr 29, 2026, 03:04 PM UTC

      Customers trying to search in the Chamber of Commerce will notice errors. We are working with the Chamber of Commerce to resolve the problem

    Latest: Customers trying to search in the Chamber of Commerce will notice errors. We are working with the Chamber of Commerce to resolve the problem

  3. Degraded performance in Visma net
    Resolved 17h 14m
    Started Apr 28, 2026, 08:43 PM UTC · Resolved Apr 29, 2026, 01:57 PM UTC
    Visma NetVisma Net API
    10 updates · show timeline
    • investigating · Apr 28, 2026, 08:43 PM UTC

      We are currently investigating this issue.

    • monitoring · Apr 29, 2026, 02:34 AM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · Apr 29, 2026, 05:21 AM UTC

      We are continuing to monitor for any further issues.

    • monitoring · Apr 29, 2026, 06:41 AM UTC

      We are continuing to monitor for any further issues.

    • investigating · Apr 29, 2026, 07:17 AM UTC

      We are currently investigating this issue.

    • identified · Apr 29, 2026, 08:02 AM UTC

      The issue has been identified and a fix is being implemented.

    • identified · Apr 29, 2026, 09:11 AM UTC

      We are continuing to work on a fix for this issue.

    • monitoring · Apr 29, 2026, 10:07 AM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · Apr 29, 2026, 10:39 AM UTC

      We are continuing to monitor for any further issues.

    • resolved · Apr 29, 2026, 01:57 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Degraded performance on API
    Resolved 1h 39m
    Started Apr 28, 2026, 01:30 PM UTC · Resolved Apr 28, 2026, 03:10 PM UTC
    Visma Net API
    3 updates · show timeline
    • investigating · Apr 28, 2026, 01:30 PM UTC

      We are currently investigating this issue.

    • identified · Apr 28, 2026, 02:11 PM UTC

      The issue has been identified and a fix is being implemented.

    • resolved · Apr 28, 2026, 03:10 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Flyt Common solutions having performance issues
    Resolved 2d 20h
    Started Apr 24, 2026, 10:25 AM UTC · Resolved Apr 27, 2026, 06:50 AM UTC
    Visma Flyt PPTVisma Flyt BVVVisma Flyt HelseVisma Flyt Sikker SakFlyt Barnevern
    7 updates · show timeline
    • investigating · Apr 24, 2026, 10:25 AM UTC

      We are experiencing performance problems and errors. We are investigating

    • investigating · Apr 24, 2026, 10:29 AM UTC

      We are continuing to investigate this issue.

    • identified · Apr 24, 2026, 11:23 AM UTC

      We might have encounter what the root cause is, we're looking for possibilities how to resolve it right now

    • identified · Apr 24, 2026, 11:50 AM UTC

      We're going to make an Emergency Change today at 15:00 NO time in order to resolve the degraded performance of all Flyt Common Applications. There is still on-going discussion of how change will be implemented. For now, the change will cause a downtime of ~30minutes on all FLYT Applications

    • identified · Apr 24, 2026, 01:06 PM UTC

      The fix is going to implemented. The fix will generate a total downtime of less than 5 minutes and emergency maintenance will be done in about 30 minutes, ending at around 15:30.

    • monitoring · Apr 24, 2026, 01:29 PM UTC

      Change has been implemented, we're monitoring the results

    • resolved · Apr 27, 2026, 06:50 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Visma outage history

31 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 22 incidents
  • Investigating an issue in Visma Directe Bankkoppeling Ongoing
    Started Apr 29, 2026, 03:07 PM UTC · ● 3h 23m
  • Investigating an issue in AccountView.Net Ongoing
    Started Apr 29, 2026, 03:04 PM UTC · ● 3h 26m
  • Degraded performance in Visma net Resolved
    Started Apr 28, 2026, 08:43 PM UTC · Resolved Apr 29, 2026, 01:57 PM UTC · 17h 14m
  • Degraded performance on API Resolved
    Started Apr 28, 2026, 01:30 PM UTC · Resolved Apr 28, 2026, 03:10 PM UTC · 1h 39m
  • Flyt Common solutions having performance issues Resolved
    Started Apr 24, 2026, 10:25 AM UTC · Resolved Apr 27, 2026, 06:50 AM UTC · 2d 20h
  • Issue submitting (bulk) payments to the rabobank via Visma Directe bankkoppeling Resolved
    Started Apr 24, 2026, 09:31 AM UTC · Resolved Apr 24, 2026, 10:38 AM UTC · 1h 7m
  • Problems reaching some parts of our service Resolved
    Started Apr 24, 2026, 08:50 AM UTC · Resolved Apr 24, 2026, 09:30 AM UTC · 40m
  • Text in Test of Controls page not visible in Sticos Descartes Resolved
    Started Apr 20, 2026, 09:35 AM UTC · Resolved Apr 10, 2026, 12:30 AM UTC · —

See Visma in your Pingoru dashboard

Monitor Visma alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Visma to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Visma incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Visma or see every provider at once.

Maintenance calendar

Scheduled Visma maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Visma status change, one inbox

Pingoru watches Visma's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Visma reports on 386 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Visma alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Visma maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Visma services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Visma from the same account, with per-user notification preferences for any monitor.

Get notified on Visma status changes

Pingoru watches Visma's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Visma free

Monitor Visma along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Visma and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Visma uptime & incident history

See 90 days of Visma uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Visma uptime history

Frequently asked questions

What is Visma's uptime?
Over the last 90 days, Visma reported 99.71% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.visma.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Visma's uptime history rolling forward in real time.
Has Visma had outages in 2026?
Yes — Visma has had 41 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Visma outage?
The most recent Visma incident was "Degraded performance in Visma net", which started on April 28, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.visma.com. See the full incident card above for affected components and the update timeline.
How often does Visma have outages?
Based on the last 90 days, Visma averages 13.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Visma's status page?
Visma's official status page is https://status.visma.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Visma down right now?
Visma is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment Visma reports a change. Current status is based on 386 tracked services.
How does Pingoru know if Visma is down?
We read https://status.visma.com directly, using Visma's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Visma has an outage?
Create a free Pingoru account and add Visma as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Visma's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Visma incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Visma issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Visma status?
We use Visma's own status page at https://status.visma.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Partial Outage" mean?
Visma has a partial outage — one or more components are down, but the rest of the service is operational.

Stop finding out from your users.

We watch Visma's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Visma free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →