Kickserv incident

kck.sv links are not resolving

Minor Resolved View vendor source →

Kickserv experienced a minor incident on February 18, 2022 affecting Web Application (app.kickserv.com) and Customer Center and 1 more component, lasting 23d 17h. The incident has been resolved; the full update timeline is below.

Started
Feb 18, 2022, 09:26 PM UTC
Resolved
Mar 14, 2022, 03:24 PM UTC
Duration
23d 17h
Detected by Pingoru
Feb 18, 2022, 09:26 PM UTC

Affected components

Web Application (app.kickserv.com)Customer CenterText Notifications

Update timeline

  1. investigating Feb 18, 2022, 09:26 PM UTC

    We are seeing DNS problems resolving web URLs created by our link shortening service. These URLs start with kck.sv and are used by our text messaging service and a few other areas of our web application. We are investigating now. In the meantime, if your customers are having problems viewing payment requests, you can send them a link to the Customer Center by visiting the customer's screen in Kickserv, selecting the Overview tab, and scrolling to the Customer Center section. Thanks for bearing with us while we sort this out.

  2. investigating Feb 22, 2022, 07:43 PM UTC

    Due to severe technical limitations at the registrar for our kck.sv domain, we will switching to kck.im for our text message links. We'll update this incident when that's done. Any payment requests will need to be resent, as the old kck.sv links will no longer work. Note that you can always send your customer a link to their Customer Center--where they can view and pay invoices and requests--by visiting the customer's screen in Kickserv, selecting the Overview tab, and scrolling to the Customer Center section.

  3. identified Feb 22, 2022, 07:44 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Feb 24, 2022, 06:47 PM UTC

    Service has been restored for the domain kck.sv, so existing short links for payment requests and to the Customer Center are once again working. As previously mentioned, though, we will be switching to kck.im very soon to guard against reoccurrence of the issue. We hope to switch back to kck.sv at some point in the future, if and when it becomes possible.

  5. resolved Mar 14, 2022, 03:24 PM UTC

    This incident has been resolved.