Wyng incident

Wyng platform and campaigns may not be accessible to some users

Minor Resolved View vendor source →

Wyng experienced a minor incident on April 24, 2018, lasting 7m. The incident has been resolved; the full update timeline is below.

Started
Apr 24, 2018, 12:51 PM UTC
Resolved
Apr 24, 2018, 12:58 PM UTC
Duration
7m
Detected by Pingoru
Apr 24, 2018, 12:51 PM UTC

Update timeline

  1. identified Apr 24, 2018, 12:51 PM UTC

    Wyng platform and campaigns may not be accessible to some users, due to an DNS related problem that Amazon Web Services (AWS) is having right now. We partner with AWS to host our servers. This is affecting many AWS clients. Here is the detail posted by AWS on http://status.aws.amazon.com/: 5:19 AM PDT We are investigating reports of problems resolving some DNS records hosted on Route53 using the third party DNS resolvers 8.8.8.8 and 8.8.4.4 . DNS resolution using other third-party DNS resolvers or DNS resolution from within EC2 instances using the default EC2 resolvers are not affected at this time.

  2. monitoring Apr 24, 2018, 12:54 PM UTC

    AWS posted the following update on the issue: 5:49 AM PDT We have identified the cause for an elevation in DNS resolution errors using third party DNS resolvers 8.8.8.8 / 8.8.4.4 and are working towards resolution. DNS resolution using other third-party DNS resolvers or DNS resolution from within EC2 instances using the default EC2 resolvers continues to work normally.

  3. resolved Apr 24, 2018, 12:58 PM UTC

    The issue is resolved.