RMM - Concord - Sporadic 503 Errors When Connecting To A Device
Incident Report for Datto
Postmortem

On May 10th, 2022 at 14:20 UTC and on May 11th, 2022 at 13:35 UTC, Datto RMM Partners on the Concord platform experienced a service interruption which caused 503 errors when attempting to connect to a device.

The root cause for this service interruption was identified to be increased traffic through the instances responsible for agent connections that surpassed the available resources for those instances.

Our Engineering team has created new instances to handle the increased traffic, and the issue was confirmed to be resolved on May 11th, 2022 at 13:53 UTC.

Traffic will continue to be monitored, and additional time-based instances may be created for high traffic times.

Posted May 19, 2022 - 08:57 UTC

Resolved
This incident has been resolved.
Posted May 10, 2022 - 15:37 UTC
Monitoring
We have implemented a fix and are monitoring the results. While user may still experience some HTTP 503: Service Unavailable errors, they should be clearing up.

Thank you for your patience!
Posted May 10, 2022 - 14:56 UTC
This incident affected: Datto RMM (Concord (US East)).