Pingen incident

Temporary outage acknowledgement on Tuesday 4th of June

Major Resolved View vendor source →

Pingen experienced a major incident on June 4, 2024, lasting 1h 5m. The incident has been resolved; the full update timeline is below.

Started
Jun 04, 2024, 07:45 PM UTC
Resolved
Jun 04, 2024, 08:50 PM UTC
Duration
1h 5m
Detected by Pingoru
Jun 04, 2024, 07:45 PM UTC

Update timeline

  1. resolved Jun 12, 2024, 08:45 AM UTC

    Both issues have been identified: following are the results of our analysis: **Long downtime:** The longer downtime during our routine weekly maintenance window was a result of a human error while trying to resolve an issue that arose during update. However it was forgotten to revert the change during analysis, which resulted in a downtime of over an hour while the problem was resolved. **API responding 500, instead of 503:** During planned maintenance or unplanned downtime, our systems are designed to respond with a 503 Service unavailable, which instructs most integrations to retry after a certain retry schedule. Due to a bug in our system which was introduced a few days prior, this mechanism did not work which resulted in a wrongly reported 500 Internal Server Error. This error has been fixed. We apologise for the inconveniences caused and we have taken appropriate measurements to avoid these situations in future.