Fourth incident

P1 - Mobile PPnI Apps- Latency When Attempting to Open App

Critical Resolved View vendor source →

Fourth experienced a critical incident on March 20, 2024 affecting Fourth App, lasting 18h 53m. The incident has been resolved; the full update timeline is below.

Started
Mar 20, 2024, 02:31 PM UTC
Resolved
Mar 21, 2024, 09:24 AM UTC
Duration
18h 53m
Detected by Pingoru
Mar 20, 2024, 02:31 PM UTC

Affected components

Fourth App

Update timeline

  1. investigating Mar 20, 2024, 02:31 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  2. investigating Mar 20, 2024, 02:57 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  3. investigating Mar 20, 2024, 03:29 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are currently seeing a marked improvement in login rates. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  4. monitoring Mar 20, 2024, 03:43 PM UTC

    We are happy that the solution is now stable and are currently monitoring for completeness. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

  5. resolved Mar 21, 2024, 09:24 AM UTC

    We are confident that our solution has resolved this incident. This will conclude the updates to the status page regarding this outage however a formal Incident Report will be posted here with the next 5 business days. We greatly apologise for this disruption.