All services / AI

visma.com · AI

Is Visma down?

Something is off: the vendor reports a minor incident. Official status: Partially Degraded Service

What's broken? (optional)
Is it just me?
Degraded performance

What to try while Visma is having problems

Estimated fix: Not enough Visma history yet; similar AI outages lasted 18 min (median, typically 9 min–29 min; 8 outages).

  • Try the mobile app or a private window, or the API; another assistant can cover urgent work.

Official Visma status page

Live diagnosis

Is it just me?

Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.

Your browser → visma.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—

Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.

Checks by region

Reachable from all 4 regions we check from.

US East · ORDReachable54 ms · 7 min ago
US West · SJCReachable106 ms · 7 min ago
Europe · AMSReachable57 ms · 7 min ago
Asia-Pacific · KIXReachable36 ms · 7 min ago

Live outage map

No reports in the last 24 hours.

Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 64 ms · 8 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid10102 msMon 18Wed 12Fri 06Sat 23Mon 17
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
Mon 0300.050 ms0
Mon 0400.065 ms0
Mon 0500.070 ms0
Mon 0600.038 ms0
Mon 0700.070 ms0
Mon 0800.042 ms0
Mon 0900.0102 ms0
Mon 1000.046 ms0
Mon 1100.072 ms0
Mon 1200.054 ms0
Mon 1300.057 ms0
Mon 1400.071 ms0
Mon 1500.059 ms0
Mon 1600.064 ms0

Reliability

Score 99/100 · grade A

100%Uptime · 30 days
100%Uptime · 90 days
1 / 1Outages · 30 / 90 days
9 minAverage outage

90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.

Visma status badge Embed a live Visma status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

Visma status and 30-day uptime badge

Past outages

StartedPeakDurationStatusDetails
2026-11-02 07:29 UTCmajor outage9 minResolvedDetails →

All Visma outages · Every recent outage

Having trouble with Visma?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

Questions

Is Visma down right now?

Something is off: the vendor reports a minor incident. Official status: Partially Degraded Service

Visma not working for me but the status is fine. What now?

If Visma is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Visma's side.

How does Damn is it down decide Visma's status?

Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.

How often is Visma checked?

About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.