Epsilon3 incident

Errors accessing Fedramp environment

Critical Resolved View vendor source →

Epsilon3 experienced a critical incident on March 4, 2026 affecting Epsilon3 Fedramp production, lasting 13m. The incident has been resolved; the full update timeline is below.

Started
Mar 04, 2026, 05:46 PM UTC
Resolved
Mar 04, 2026, 06:00 PM UTC
Duration
13m
Detected by Pingoru
Mar 04, 2026, 05:46 PM UTC

Affected components

Epsilon3 Fedramp production

Update timeline

  1. identified Mar 04, 2026, 05:46 PM UTC

    We are currently experiencing errors from our Fedramp environment. Our provider is aware and is working on a resolution.

  2. monitoring Mar 04, 2026, 05:50 PM UTC

    We are seeing access being restored and are continuing to monitor.

  3. resolved Mar 04, 2026, 06:00 PM UTC

    This incident has been resolved.