PreVeil incident

AWS outage

Notice Resolved View vendor source →

PreVeil experienced a notice incident on October 20, 2025 affecting Android App and Backend and 1 more component, lasting 8h 3m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 03:25 PM UTC
Resolved
Oct 20, 2025, 11:28 PM UTC
Duration
8h 3m
Detected by Pingoru
Oct 20, 2025, 03:25 PM UTC

Affected components

Android AppBackendAdmin ConsoleiOS AppDriveWeb PreVeilMail

Update timeline

  1. investigating Oct 20, 2025, 03:25 PM UTC

    :warning: Service Advisory: AWS Outage Causing Major Disruption to PreVeil Express As of October 20, 2025, PreVeil is experiencing significant service disruption due to a widespread outage in Amazon Web Services (AWS), specifically in the US-EAST-1 region. This incident is impacting numerous global platforms and has caused a major outage for PreVeil Express. Current Impact: - PreVeil Express is experiencing a full service outage. Users may be unable to access their accounts or send secure messages at this time. - Other internal services are also affected, resulting in intermittent slowness and degraded performance across the platform. What we know: AWS has attributed the issue to a DNS resolution failure affecting core infrastructure. While they are seeing signs of recovery, full restoration is still in progress. Our engineering team is actively monitoring the situation and working to mitigate downstream effects. We will continue to post updates here as the situation evolves. We appreciate your patience and understanding as we work through this third-party disruption. —The PreVeil Team

  2. investigating Oct 20, 2025, 04:37 PM UTC

    Failures cascaded down onto our Kubernetes cluster impacting our load balancer deployment. We are weighting options to make it work again by understanding what is failing from AWS.

  3. monitoring Oct 20, 2025, 09:20 PM UTC

    PreVeil services are now operational. Please let us know if you have any problems with accessing PreVeil.

  4. resolved Oct 20, 2025, 11:28 PM UTC

    This incident has been resolved.