Skyvera incident

DNS Issue Affecting CloudSense

Critical Resolved View vendor source →

Skyvera experienced a critical incident on July 17, 2025 affecting CloudSense, lasting 6d 14h. The incident has been resolved; the full update timeline is below.

Started
Jul 17, 2025, 01:37 AM UTC
Resolved
Jul 23, 2025, 03:48 PM UTC
Duration
6d 14h
Detected by Pingoru
Jul 17, 2025, 01:37 AM UTC

Affected components

CloudSense

Update timeline

  1. investigating Jul 17, 2025, 01:37 AM UTC

    We're investigating an issue with DNS resolution for cloudsense.com following a name server misconfiguration. Some users may see errors or failures when generating or loading data.

  2. investigating Jul 17, 2025, 04:26 AM UTC

    We would like to update you that our teams are continuing to actively investigate this issue related to the DNS resolution.

  3. investigating Jul 17, 2025, 05:57 AM UTC

    Our teams are diligently looking into the DNS resolution issue. We appreciate your patience as we work towards a solution.

  4. investigating Jul 17, 2025, 07:16 AM UTC

    DNS propagation is still in progress . We recommend adding Google’s DNS server 8.8.8.8 as a secondary resolver in your network or system settings to help mitigate resolution issues while global DNS propagation completes. This is a temporary workaround and can be removed once propagation stabilizes.

  5. investigating Jul 17, 2025, 07:16 AM UTC

    DNS propagation is still in progress . We recommend adding Google’s DNS server 8.8.8.8 as a secondary resolver in your network or system settings to help mitigate resolution issues while global DNS propagation completes. This is a temporary workaround and can be removed once propagation stabilizes.

  6. identified Jul 17, 2025, 09:42 AM UTC

    We have determined that the issue is related to the Dispatcher URL. A temporary workaround has been identified and is currently available while we continue working on a full resolution.

  7. monitoring Jul 17, 2025, 11:17 AM UTC

    Fixes are being implemented and we are monitoring the results.

  8. monitoring Jul 17, 2025, 11:29 AM UTC

    We are continuing to monitor for any further issues.

  9. monitoring Jul 17, 2025, 02:40 PM UTC

    As a workaround for the reported issue, we have drafted a detailed article to help you, in case you are affected by this issue. Please review the enclosed article for the full context of the situation, as well as the workaround to be applied: https://cloudsense.kayako.com/article/128098-temporary-endpoint-update-required-due-to-dns-resolution-issue We appreciate your patience and understanding!

  10. resolved Jul 23, 2025, 03:48 PM UTC

    We’re pleased to confirm that the previously reported issue has now been fully resolved. DNS resolution is functioning as expected, and all related systems are operating normally. We appreciate your patience and understanding while we worked to resolve this, and we’re here if you have any further questions or concerns.