Wisembly incident

Site unreachable for some users. DNSSEC issue

Notice Resolved View vendor source →

Wisembly experienced a notice incident on March 3, 2022 affecting Wisembly application and Real time and 1 more component, lasting 27d 6h. The incident has been resolved; the full update timeline is below.

Started
Mar 03, 2022, 09:10 AM UTC
Resolved
Mar 30, 2022, 03:29 PM UTC
Duration
27d 6h
Detected by Pingoru
Mar 03, 2022, 09:10 AM UTC

Affected components

Wisembly applicationReal timeCDNDocuments processingWisembly Website

Update timeline

  1. identified Mar 03, 2022, 09:10 AM UTC

    We experience a DNSSEC problem in our DNS Zone. The *.wisembly.com DNS are not reachable for some of our users. We are currently investigating with our DNS provider OVH to fix this issue. We'll update this ticket when we have news from them.

  2. identified Mar 03, 2022, 09:36 AM UTC

    OVH has identified the root cause and escalated the issue to the right team. This hopefully should be fixed in the upcoming minutes...

  3. monitoring Mar 03, 2022, 10:24 AM UTC

    As our DNS provider OVH is investigating the problem, we decided 1h ago do disable DNSSEC validation of our domain to avoid this temporary issue. We observe the propagation of this setting on the ICANN registry and this should fix the problem for our users. Our Pingdom probes are green again. We'll keep this configuration until next Thursday to ensure OVH properly address the issue before enabling it back. Sorry again for the inconvenience

  4. resolved Jul 07, 2022, 03:29 PM UTC

    This incident has been resolved.