Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

IT Glue Outage History

Every past IT Glue outage tracked by IsDown, with detection times, duration, and resolution details.

There were 140 IT Glue outages since March 2017. The 80 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major May 11, 2026

May 2026: Datto SaaS Protection - Service disruption for customers hosted on pod 'usw3-saas-p0'

Detected May 11, 2026 5:39 PM UTC · Resolved May 13, 2026 2:15 PM UTC · Duration 2 days

Customers hosted on pod 'usw3-saas-p0' experienced a major disruption to Datto SaaS Protection Backup and Recovery services for 44.6 hours. The Kaseya R&D team identified and resolved multiple issues affecting the service, with backup success rates returning to normal levels. The incident was fully resolved after continuous monitoring confirmed stable service operation.

Major May 11, 2026

May 2026: SaaS Alerts Microsoft Manage Service Interruption

Detected May 11, 2026 5:42 AM UTC · Resolved May 13, 2026 1:55 PM UTC · Duration 2 days

The SaaS Alerts Microsoft Manage Integration experienced a major service interruption lasting 56.2 hours due to an unstable Microsoft endpoint that was intermittently throwing errors. The team implemented retry functionality and cleared all errors to stabilize the affected Microsoft connections. The incident was resolved once the Microsoft endpoint returned to normal performance.

Minor May 8, 2026

May 2026: Datto Workplace / Datto File Protection - US Cells - SSO login is currently unavailable for users based in the United States

Detected May 8, 2026 4:12 PM UTC · Resolved May 11, 2026 12:49 PM UTC · Duration 3 days

A subset of US-based Datto Workplace and Datto File Protection users experienced SSO login failures through the portal for 68.6 hours, while agent login and full service access remained functional. Users could work around the issue by specifying their regional URL when logging in directly (us.workplace.datto.com). The incident was resolved after Kaseya's R&D team implemented a fix and monitored the results.

Minor May 5, 2026

May 2026: Datto SaaS Protection - Backup performance degradation for SharePoint/Teams services on pod 'des1-saas-p0'

Detected May 5, 2026 2:57 PM UTC · Resolved May 8, 2026 12:33 PM UTC · Duration 3 days

Datto SaaS Protection customers on pod 'des1-saas-p0' experienced degraded backup performance for SharePoint and Teams services over a 69.6-hour period. The Kaseya R&D team implemented changes to address the performance issues and monitored backup success rate metrics as they gradually returned to normal. The incident was fully resolved after backup performance was restored to expected levels.

Major May 5, 2026

May 2026: Datto Workplace AU5 - Agents are unable to connect and sync data; files cannot be created and/or saved in Workplace Online

Detected May 5, 2026 8:27 AM UTC · Resolved May 6, 2026 12:45 PM UTC · Duration 1 day

Datto Workplace AU5 experienced a major outage lasting 28.3 hours where agents could not connect or sync data, and users encountered failures when creating, opening, or saving files through the online platform and integrations with Google Docs and Microsoft 365. The incident affected partners on the AU5 cell who saw server errors in Workplace Agent and 404 errors when attempting to create new files online. A fix was implemented and monitored before the incident was fully resolved.

Minor May 4, 2026

May 2026: Datto Networking - Intermittent Check‑In Failures Observed on Datto Networking D200 Devices

Detected May 4, 2026 5:24 PM UTC · Resolved May 5, 2026 7:35 PM UTC · Duration 1 day

Datto Networking D200 devices experienced intermittent check-in failures that triggered false-positive offline email alerts for users. The issue was cosmetic only and did not impact device functionality or performance. The problem was resolved after 26.2 hours with a fix implemented by the Kaseya R&D team.

Major May 4, 2026

May 2026: Datto SaaS Protection - Service disruption for customers hosted on node 'Gbe2-saas-p0-app-2'

Detected May 4, 2026 11:52 AM UTC · Resolved May 5, 2026 12:23 PM UTC · Duration 1 day

Customers hosted on node 'gbe2-bfyii-327' experienced a 24.5-hour service disruption where they could not access the Datto SaaS Protection platform, though backup operations continued to function normally. The Kaseya R&D team implemented fixes and monitored the system before fully resolving the incident.

Major April 30, 2026

April 2026: Datto SaaS Protection - Service disruption for customers hosted on pod 'cae1-saas-p1'

Detected Apr 30, 2026 10:31 PM UTC · Resolved May 1, 2026 3:27 PM UTC · Duration about 17 hours

Customers hosted on pod 'cae1-saas-p1' experienced a major disruption to their Datto SaaS Protection services, affecting backup operations and success rates. The R&D team performed maintenance and implemented a fix to resolve the underlying issue with the pod. The incident lasted 16.9 hours before backup success rates returned to normal and the service was fully restored.

Minor April 30, 2026

April 2026: Datto SaaS Protection - Backup performance and access issues for customers hosted on node 'gbe2-bfyii-1225'

Detected Apr 30, 2026 4:38 PM UTC · Resolved May 1, 2026 12:35 PM UTC · Duration about 20 hours

Customers hosted on node 'gbe2-bfyii-1225' experienced degraded backup performance for SharePoint/Teams services and received 504 errors when accessing their Datto SaaS Protection accounts. The Kaseya R&D team identified and implemented a fix to resolve the access issues, then monitored the system for stability. The incident was fully resolved after 20 hours.

Minor April 29, 2026

April 2026: Datto SaaS Protection - Backup performance degradation for M365 services on pod 'usw3-saas-p1'

Detected Apr 29, 2026 2:30 PM UTC · Resolved Apr 30, 2026 1:00 PM UTC · Duration about 23 hours

Datto SaaS Protection customers on pod 'usw3-saas-p1' experienced degraded backup performance for Microsoft 365 services over a 22.5-hour period. The Kaseya R&D team identified the root cause and implemented a fix, followed by monitoring to ensure resolution. The incident was fully resolved after the fix proved effective.