Is Kaseya down?

Last checked 8m ago
Current status
Kaseya is having a partial outage

2 active incidents: Datto SaaS Protection - Backup performance degradation for…, VSA10 - Service Degradation for subset of VSA10-US customers

Get alerts when Kaseya breaks →

Free · no credit card

Official status page: https://status.kaseya.net · Polled every 5 minutes · 54 components tracked

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

Users who monitor Kaseya also follow these Monitoring services: NinjaOne LogicMonitor SolarWinds ControlUp xMatters Liongard AlertMedia GitHub Enterprise Cloud EU Meltwater StatusCake View all 6,000+ providers
Kaseya uptime 99.82% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Datto SaaS Protection - Backup performance degradation for M365 services on pod 'usw3-saas-p1'
    Ongoing ● 2h 51m
    Started Apr 29, 2026, 02:30 PM UTC
    2 updates · show timeline
    • identified · Apr 29, 2026, 02:30 PM UTC

      We are currently aware of a problem where some Datto SaaS Protection customers hosted on pod 'usw3-saas-p1' are experiencing degraded backup performance for some M365 services. The Kaseya R&D Team has identified the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    • monitoring · Apr 29, 2026, 04:37 PM UTC

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

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

  2. Datto RMM - Zinfandel - Agents going offline
    Resolved 10h 28m
    Started Apr 28, 2026, 09:47 PM UTC · Resolved Apr 29, 2026, 08:16 AM UTC
    3 updates · show timeline
    • investigating · Apr 28, 2026, 09:47 PM UTC

      We are aware of a problem where Datto RMM agents, within the Zinfandel platform going offline. The Kaseya R&D Team is aware and currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    • monitoring · Apr 28, 2026, 10:15 PM UTC

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

    • resolved · Apr 29, 2026, 08:16 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Datto RMM - Zinfandel: Delayed Jobs
    Resolved 1h 18m
    Started Apr 28, 2026, 04:12 PM UTC · Resolved Apr 28, 2026, 05:31 PM UTC
    3 updates · show timeline
    • investigating · Apr 28, 2026, 04:12 PM UTC

      We are aware of a problem where Jobs on Datto RMM's Zinfandel platform are delayed The Kaseya R&D Team is investigating the issue. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    • monitoring · Apr 28, 2026, 04:36 PM UTC

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

    • resolved · Apr 28, 2026, 05:31 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. VSA10 - Service Degradation for subset of VSA10-US customers
    Ongoing ● 1d 2h
    Started Apr 28, 2026, 03:10 PM UTC
    3 updates · show timeline
    • investigating · Apr 28, 2026, 03:10 PM UTC

      Subset of VSA10 US customers may be experiencing degraded performance intermittently, which may impact administrators ability to manage endpoints. We are aware of the issue and our team is actively working to resolve the same. We apologize for any inconvenience caused. - Cloud Operations Team

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

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

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

      We are continuing to monitor for any further issues.

    Latest: We are continuing to monitor for any further issues.

  5. Datto SaaS Protection - Service disruption for customers hosted on node 'gbe2-bfyii-327'
    Resolved 5d 1h
    Started Apr 24, 2026, 01:20 PM UTC · Resolved Apr 29, 2026, 02:36 PM UTC
    5 updates · show timeline
    • investigating · Apr 24, 2026, 01:20 PM UTC

      We are aware of a problem where customers hosted on node 'gbe2-bfyii-327' are experiencing a disruption to their SaaS Protection services. The Kaseya R&D Team has identified the issue and are actively working to resolve it. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    • identified · Apr 24, 2026, 02:15 PM UTC

      Our R&D team is continuing to address this issue.

    • identified · Apr 24, 2026, 07:30 PM UTC

      Our R&D team is performing maintenance on node 'gbe2-bfyii-327' over the weekend to repair a hardware issue that was identified. There is still currently no ETA on when services will be fully restored. We will provide more updates from the team as they become available.

    • identified · Apr 27, 2026, 12:45 PM UTC

      Maintenance on node 'gbe2-bfyii-327' is still in progress. We will continue to provide updates as they become available.

    • identified · Apr 29, 2026, 02:00 PM UTC

      Maintenance is still in progress to address a hardware issue found on node 'gbe2-bfyii-327'. We will continue to provide updates from the team as the maintenance progresses.

    Latest: Maintenance is still in progress to address a hardware issue found on node 'gbe2-bfyii-327'. We will continue to provide updates from the team as the maintenance progresses.

See the full Kaseya outage history

4 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 · 9 incidents
  • Datto SaaS Protection - Backup performance degradation for M365 services on pod 'usw3-saas-p1' Ongoing
    Started Apr 29, 2026, 02:30 PM UTC · ● 2h 51m
  • Datto RMM - Zinfandel - Agents going offline Resolved
    Started Apr 28, 2026, 09:47 PM UTC · Resolved Apr 29, 2026, 08:16 AM UTC · 10h 28m
  • Datto RMM - Zinfandel: Delayed Jobs Resolved
    Started Apr 28, 2026, 04:12 PM UTC · Resolved Apr 28, 2026, 05:31 PM UTC · 1h 18m
  • VSA10 - Service Degradation for subset of VSA10-US customers Ongoing
    Started Apr 28, 2026, 03:10 PM UTC · ● 1d 2h
  • Datto SaaS Protection - Service disruption for customers hosted on node 'gbe2-bfyii-327' Resolved
    Started Apr 24, 2026, 01:20 PM UTC · Resolved Apr 29, 2026, 02:36 PM UTC · 5d 1h
  • VSA9 - Partial Service Disruption - liveconnect.me Resolved
    Started Apr 23, 2026, 03:58 PM UTC · Resolved Apr 23, 2026, 08:54 PM UTC · 4h 55m
  • Datto AV - Agent is unable to perform actions on MacOS devices Resolved
    Started Apr 22, 2026, 03:34 PM UTC · Resolved Apr 24, 2026, 02:18 PM UTC · 1d 22h
  • Service Disruption - BMS US & UK Resolved
    Started Apr 20, 2026, 03:14 PM UTC · Resolved Apr 20, 2026, 05:20 PM UTC · 2h 6m

See Kaseya in your Pingoru dashboard

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

Every status page, one dashboard

Add Kaseya 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 Kaseya 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 Kaseya or see every provider at once.

Maintenance calendar

Scheduled Kaseya 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 Kaseya status change, one inbox

Pingoru watches Kaseya'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

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

Email + Slack + Discord + Teams

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

Maintenance, not surprises

Upcoming Kaseya 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 Kaseya services without silencing the monitor entirely.

Invite your team

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

Get notified on Kaseya status changes

Pingoru watches Kaseya'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 Kaseya free

Monitor Kaseya along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Kaseya 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 Kaseya uptime & incident history

See 90 days of Kaseya 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 Kaseya uptime history

Frequently asked questions

What is Kaseya's uptime?
Over the last 90 days, Kaseya reported 99.82% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.kaseya.net — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Kaseya's uptime history rolling forward in real time.
Has Kaseya had outages in 2026?
Yes — Kaseya has had 33 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 Kaseya outage?
The most recent Kaseya incident was "Datto RMM - Zinfandel - Agents going offline", which started on April 28, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.kaseya.net. See the full incident card above for affected components and the update timeline.
How often does Kaseya have outages?
Based on the last 90 days, Kaseya averages 11.0 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 Kaseya's status page?
Kaseya's official status page is https://status.kaseya.net. 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 Kaseya down right now?
Kaseya is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment Kaseya reports a change. Current status is based on 54 tracked services.
How does Pingoru know if Kaseya is down?
We read https://status.kaseya.net directly, using Kaseya'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 Kaseya has an outage?
Create a free Pingoru account and add Kaseya as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Kaseya's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Kaseya 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 Kaseya 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 Kaseya status?
We use Kaseya's own status page at https://status.kaseya.net. 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?
Kaseya 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 Kaseya'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 Kaseya free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →