Starting at 19:43 UTC on 02 May 2019, Azure customers experienced intermittent connectivity issues with Azure and other Microsoft services (including M365, Dynamics, DevOps, etc).EDQ applications hosted at Azure experienced higher than usual response times.Microsoft Engineers had identified the underlying root cause as an incorrect name server delegation issue affecting DNS resolution, network connectivity, and downstream impact to Compute, Storage, App Service, AAD, and SQL Database resources. Mitigation had been applied by Microsoft, and the majority of Azure and other Microsoft services have recovered at approx. 23:08 UTC. Response times for all EDQ SaaS Applications is now back to normal.
Posted 5 months ago. May 03, 2019 - 00:14 UTC
This incident affected: EDQ for Salesforce (EDQ for Salesforce - V3, EDQ for Salesforce - V4, EDQ for Salesforce - V5), Address Validate (REST) v1, Address Validate (REST) v2, Address Validate (SOAP), Aperture Email Validation, Email Validate - Real Time, Email Validate - Batch, Aperture Phone Validation, Global Mobile Validate, Capture Application, Clean Application, Clean Web Services, QAS for MSDCRM, QAS for Oracle, Aperture Enrichment, Prospect IQ, Intelligent Search, IST Watch, EDQ.com, Self Service Portal, Electronic Updates, and Phone Validate USA (Phone Validate V1, Phone Validate V2).