Is Datto down?

Last checked 9m ago
Current status
Datto has degraded performance

2 active incidents: VSA10 - Scheduled Maintenance - v10.28 Release - US, Datto SaaS Protection - Backup performance degradation for…

Official status page: https://status.datto.com · Polled every 5 minutes · 393 components tracked

Datto is reporting degraded performance right now (last checked 9m ago). Services are up but slower or partially failing.

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

Users who monitor Datto also follow these IT services: Jamf TeamViewer Cisco Meraki Workato GoToMyPC Ubiquiti Splashtop Cursor Auvik Samanage View all 6,000+ providers
Datto uptime 99.23% uptime · past 90 days
Mon Wed Fri
AprMayJunJul
Less More

Active incident 1

  1. Ongoing ● 1d 15h
    Started Jul 28, 2026, 12:47 PM UTC
    SaaS Protection Backups
    Timeline · 4 updates
    • identified · Jul 28, 2026, 12:47 PM UTC

      We are aware of a problem where some Datto SaaS Protection customers hosted on pod 'gbe2-saas-p2' may be experiencing backup performance degradation affecting some SharePoint/Teams services. The Kaseya Engineering 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 · Jul 28, 2026, 06:02 PM UTC

      Our R&D team has implemented changes on pod 'gbe2-saas-p2' to mitigate the backup performance issues affecting some SharePoint and Teams services.

    • monitoring · Jul 28, 2026, 08:07 PM UTC

      Backup success rates for SharePoint/Teams services on pod 'gbe2-saas-p2' are improving after the changes made on the pod earlier today. Our R&D team is continuing to monitor.

    • monitoring · Jul 29, 2026, 03:20 PM UTC

      Backup success rates for SharePoint/Teams services on pod 'gbe2-saas-p2' have returned to normal levels. Our R&D team is continuing to monitor.

    Latest: Backup success rates for SharePoint/Teams services on pod 'gbe2-saas-p2' have returned to normal levels. Our R&D team is continuing to monitor.

Recent outages & incidents

Past 90 days
  1. Resolved 9h 19m
    Started Jul 29, 2026, 10:55 AM UTC · Resolved Jul 29, 2026, 08:15 PM UTC
    SaaS Protection BackupsSaaS Protection Console LoginSaaS Protection Seat ManagementSaaS Protection Restores/Exports
    Timeline · 8 updates
    • identified · Jul 29, 2026, 10:55 AM UTC

      We are aware of an issue where Datto SaaS Protection customers hosted on pod gbe2-saas-p0 are experiencing a complete service disruption. The Kaseya Engineering Team has identified the issue and is actively working to restore service as quickly as possible. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    • identified · Jul 29, 2026, 10:56 AM UTC

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

    • identified · Jul 29, 2026, 12:23 PM UTC

      Our R&D team has applied a fix to address the issue and they are currently verifying restoration of all services on pod 'gbe2-saas-p0'.

    • identified · Jul 29, 2026, 01:45 PM UTC

      Our R&D team is continuing to address the issue and fully restore SaaS Protection services on pod 'gbe2-saas-p0'.

    • identified · Jul 29, 2026, 03:02 PM UTC

      Our R&D team has confirmed that backups are currently processing normally on pod 'gbe2-saas-p0' however they are continuing to address an issue affecting customer account access.

    • identified · Jul 29, 2026, 04:38 PM UTC

      Our R&D team is continuing to address the account access issues still affecting some SaaS Protection customers hosted on pod 'gbe2-saas-p0' as well as monitoring backup performance.

    • monitoring · Jul 29, 2026, 05:12 PM UTC

      Our R&D team has implemented additional changes to address the intermittent account access issues that were still affecting some customers hosted on pod 'gbe2-saas-p0' and backups for all services are continuing to process. We will be monitoring the pod closely for any other issues.

    • resolved · Jul 29, 2026, 08:15 PM UTC

      Backups continue to process and all customer accounts hosted on pod 'gbe2-saas-p0' are accessible and functioning normally. This incident is resolved.

    Latest: Backups continue to process and all customer accounts hosted on pod 'gbe2-saas-p0' are accessible and functioning normally. This incident is resolved.

  2. Resolved 13h 2m
    Started Jul 28, 2026, 06:01 PM UTC · Resolved Jul 29, 2026, 07:04 AM UTC
    Limited ReleaseAmerica EastAmerica East 2America East 3America WestAmerica West 2America West 3Australia / New ZealandAustralia / New Zealand 2Spanish (Español)
    Timeline · 3 updates
    • investigating · Jul 28, 2026, 06:01 PM UTC

      We are aware of a problem where tickets are not getting created from inbound emails. The Kaseya Engineering Team is investigating the issue. 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 · Jul 28, 2026, 06:06 PM UTC

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

    • resolved · Jul 29, 2026, 07:04 AM UTC

      This incident has been resolved. All inbound emails that occurred during the incident timeframe have been successfully reprocessed.

    Latest: This incident has been resolved. All inbound emails that occurred during the incident timeframe have been successfully reprocessed.

  3. Resolved 1d 11h
    Started Jul 28, 2026, 12:52 PM UTC · Resolved Jul 29, 2026, 11:59 PM UTC
    Backup
    Timeline · 4 updates
    • investigating · Jul 28, 2026, 12:52 PM UTC

      We are aware of a problem where Endpoint Backup v2 assets in UniView may incorrectly indicate backup failures despite successful backup completion, which can trigger unnecessary email notifications. The Kaseya R&D Team is investigating the issue and working towards a resolution. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    • investigating · Jul 28, 2026, 06:04 PM UTC

      We are continuing to investigate this issue.

    • monitoring · Jul 28, 2026, 11:59 PM UTC

      Our R&D team has implemented a fix, and we're seeing improved performance across the affected systems. We're continuing to monitor the environment to ensure the improvements are sustained.

    • resolved · Jul 29, 2026, 11:59 PM UTC

      This incident has been resolved. We will continue to monitor the environment to ensure ongoing stability. If you continue to experience any issues, please contact Kaseya Support. We sincerely apologize for the disruption and thank you for your patience while we worked to resolve this issue.

    Latest: This incident has been resolved. We will continue to monitor the environment to ensure ongoing stability. If you continue to experience any issues, please contact Kaseya Support. W…

  4. Resolved 2h 25m
    Started Jul 27, 2026, 05:35 PM UTC · Resolved Jul 27, 2026, 08:00 PM UTC
    SaaS Protection Backups
    Timeline · 4 updates
    • investigating · Jul 27, 2026, 05:35 PM UTC

      We are aware of a problem where Datto SaaS Protection customers hosted on node 'use1-bfyii-2901' are experiencing a disruption to SaaS Protection services. The Kaseya Engineering Team is currently investigating. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

    • identified · Jul 27, 2026, 06:16 PM UTC

      The issue has been identified and the R&D team is actively working to resolve it.

    • monitoring · Jul 27, 2026, 06:59 PM UTC

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

    • resolved · Jul 27, 2026, 08:00 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 7h 56m
    Started Jul 24, 2026, 01:27 PM UTC · Resolved Jul 24, 2026, 09:23 PM UTC
    APACEU
    Timeline · 4 updates
    • identified · Jul 24, 2026, 01:27 PM UTC

      We are aware of a problem where customers hosted on EMEA/APAC app servers may see intermediate service disruption, getting 500 - internal server error. The Kaseya Engineering Team has identified the issue and working towards 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/

    • identified · Jul 24, 2026, 03:46 PM UTC

      The Kaseya Engineering Team has developed a fix that will address this issue. The fix will be deployed after hours to our EMEA and APAC App Servers on the following schedule: 17:00 UTC APAC 20:00 UTC EMEA Those that are online during this change will need to login again as they will be kicked out the system. Should you have 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 · Jul 24, 2026, 08:25 PM UTC

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

    • resolved · Jul 24, 2026, 09:23 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Datto outage history

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

Browse Datto outage history →

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

Outage history

Past 90 days · 47 incidents View full outage history →