Is Kaseya down?

Last checked 3m ago
Current status
Kaseya is up

No active incidents. All 48 components operational.

  • Official status page: status.kaseya.net
  • Checked every 5 minutes
  • 48 components tracked

Kaseya is operational right now. Last checked 3m ago; the most recent incident resolved 3h ago.

Real-time Kaseya status, recent outages, and incident history: pulled directly from Kaseya's official status page at status.kaseya.net every 5 minutes. Pingoru tracks 48 Kaseya services and has captured 84 incidents in the last 90 days (97.01% uptime). Get email, Slack, Discord, or webhook alerts the moment Kaseya reports a new incident, free for 3 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 8,000+ providers
Kaseya uptime 97.01% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Recent outages & incidents

Past 90 days
  1. Resolved –
    Started Nov 02, 2026, 05:00 PM UTC · Resolved Nov 02, 2026, 05:00 PM UTC
    Timeline · 1 update
    • resolved · Nov 02, 2026, 05:00 PM UTC

      The Kaseya Engineering Team resolved a problem where Batch Generating Invoices failed due to a "Failed to generate... Could not load file or assembly" error. If you are still experiencing this issue or need any assistance, please contact our support team for assistance through our helpdesk at: https://helpdesk.kaseya.com/hc/en-gb#/contact To receive notifications about future maintenance events and service updates, subscribe to https://status.kaseya.com/

    Latest: The Kaseya Engineering Team resolved a problem where Batch Generating Invoices failed due to a "Failed to generate... Could not load file or assembly" error. If you are still exper…

  2. Resolved 3h 22m
    Started Nov 02, 2026, 04:58 PM UTC · Resolved Nov 02, 2026, 08:20 PM UTC
    Timeline · 3 updates
    • identified · Nov 02, 2026, 04:58 PM UTC

      We are aware of a problem where emails sent from Autotask PSA are delayed. The Kaseya Engineering Team has identified the issue and are working on a fix. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    • monitoring · Nov 02, 2026, 07:32 PM UTC

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

    • resolved · Nov 02, 2026, 08:20 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved –
    Started Nov 02, 2026, 02:30 PM UTC · Resolved Nov 02, 2026, 02:30 PM UTC
    Timeline · 1 update
    • resolved · Nov 02, 2026, 02:30 PM UTC

      The Kaseya Engineering Team resolved a problem where pages were failing to load with an error message: "Something went wrong! Please contact the system admin." If you are still experiencing this issue or need any assistance, please contact our support team for assistance through our helpdesk at: https://helpdesk.kaseya.com/hc/en-gb#/contact To receive notifications about future maintenance events and service updates, subscribe to https://status.kaseya.com/

    Latest: The Kaseya Engineering Team resolved a problem where pages were failing to load with an error message: "Something went wrong! Please contact the system admin." If you are still exp…

  4. Resolved 3d 18h
    Started Oct 29, 2026, 07:57 PM UTC · Resolved Nov 02, 2026, 02:31 PM UTC
    Timeline · 1 update
    • investigating · Oct 29, 2026, 07:57 PM UTC

      We are aware of a problem where Datto BCDR users in the UK region may experience degraded offsite performance, potentially impacting synchronization operations. The Kaseya Engineering Team is investigating the issue and working towards a resolution. Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    Latest: We are aware of a problem where Datto BCDR users in the UK region may experience degraded offsite performance, potentially impacting synchronization operations. The Kaseya Engineer…

  5. Resolved 23h 43m
    Started Oct 28, 2026, 06:50 PM UTC · Resolved Oct 29, 2026, 06:33 PM UTC
    Datto AV
    Timeline · 2 updates
    • investigating · Oct 28, 2026, 06:50 PM UTC

      We are aware of a problem where Datto AV is incorrectly flagging newly created .pdf files as PHISH/PDF, causing the files to be quarantined. The Kaseya R&D Team is currently investigating this issue. In the meantime our Support team has been supplied with a workaround and can assist you with implementing it. If you would like to have the workaround applied, please create a ticket with our Support team or contact them at 833-863-2237. To work around this issue: Adding exclusions for the affected folders and files. Then restoring the affected files. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    • monitoring · Oct 29, 2026, 03:13 PM UTC

      Our engineering team has identified the issue and is monitoring the fix. Some PDF files, were incorrectly flagged as PHISH/PDF.Agent. A specific detection rule has been disabled in VDF 8.21.8.130, deployed October 28, 2026. The rest of the PHISH detection category remains active. We are monitoring to confirm new false positives have stopped. Files that have already been quarantined must be restored manually.

    Latest: Our engineering team has identified the issue and is monitoring the fix. Some PDF files, were incorrectly flagged as PHISH/PDF.Agent. A specific detection rule has been disabled in…

See the full Kaseya outage history

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

Browse Kaseya outage history →

Or sign up free to get alerts when Kaseya breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Statuspage by Atlassian · 48 components checked every 5 minutes
165incidents recorded
163last 12 months
84last 90 days
4 daystypical duration, 12 months

The longest incident in the last year, Datto SaaS Protection - Backup performance degradation for some SharePoint/Teams services on pod 'des1-saas-p1' on March 10, 2026, ran for 127 days. 723 maintenance windows announced in the same period.

Most affected components, last 12 months

  • KaseyaOne5
  • Kaseya Store4
  • Datto AV3
  • Uniview Unified Backup Portal1
  • Vorex1

Latest incidents

Outage history

Past 90 days · 84 incidents· showing the latest 44 View full outage history →