1pm UTC 3/27/2017
Our operations team was able to identify that the participant failures was a result of an Azure issue. This has since been corrected and we are seeing and receiving reports of participants running correctly. Any failed participants during this time period would need to be re-run through a campaign in order to progress. Our apologies for any disruption this may have caused. We are committed to working with Microsoft to ensure a full postmortem is performed.
8pm UTC 3/24/2017
We are receiving reports of an error (The remote server returned an error: (503) Server Unavailable.) being returned on participants running in Campaign Automations. This may appear at various steps in an automation. Our operations team is investigating the root cause to find a fix as an urgent item. We apologize for any inconvenience this may be causing and will report back here as we know more.