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 May 03, 2019 - 00:14 UTC
This incident affected: Other (IST Watch, EDQ.com, Self Service Portal, Electronic Updates), Phone Solutions (Phone Validation, Experian Phone Validation, Phone Validation (North America v1)), Integrations (EDQ for Salesforce (v3), EDQ for Salesforce (v4), EDQ for Salesforce (v5), EDQ for MS Dynamics, EDQ for Oracle), Email Solutions (Email Validation, Experian Email Validation, Automated Batch Email Validation), Enrichment Solutions (Experian Enrichment, Prospect IQ), and Address Solutions (Address Validation (REST v1), Address Validation (REST v2), Address Validation (SOAP), Capture Application, Clean Application, Clean API).