Palisis incident

Partial downtime affecting some users

Notice Resolved View vendor source →

Palisis experienced a notice incident on January 24, 2022 affecting Palisis Backend and Palisis Webshops and 1 more component, lasting 43m. The incident has been resolved; the full update timeline is below.

Started
Jan 24, 2022, 04:22 PM UTC
Resolved
Jan 24, 2022, 05:06 PM UTC
Duration
43m
Detected by Pingoru
Jan 24, 2022, 04:22 PM UTC

Affected components

Palisis BackendPalisis WebshopsPalisis App and Terminals

Update timeline

  1. identified Jan 24, 2022, 04:22 PM UTC

    There is an issue with one of our application servers which is currently replaced. It should take just a few minutes for the system to return fully functional for all users.

  2. identified Jan 24, 2022, 04:23 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jan 24, 2022, 04:27 PM UTC

    All systems are fully operational again The faulty server has been removed from the cluster.

  4. resolved Jan 24, 2022, 05:06 PM UTC

    Only one application server was affected. When our monitoring alarmed about the feature we removed the server from the cluster and replaced it with a new server. We apologize to all users affected.