Amperity incident

Amperity has identified the issue and implementing a resolution

Resolved after 1 hour 59 minutes, affecting East US 2 (Amperity MCP) and East US 2 (Website) and 1 more, on August 27, 2026.

resolved Aug 27, 2026, 09:57 PM UTC

All services are confirmed stable.

Started
Aug 27, 2026, 07:58 PM UTC
Resolved
Aug 27, 2026, 09:57 PM UTC
Duration
1h 59m
Detected by Pingoru
Aug 27, 2026, 07:58 PM UTC

Affected components

East US 2 (Amperity MCP)East US 2 (Website)East US 2 (Sources)East US 2 (Stitch)East US 2 (Customer 360)East US 2 (Segments)East US 2 (Destinations)East US 2 (Journeys)East US 2 (Workflows)East US 2 (Real-time API)

Update timeline

  1. investigating Aug 27, 2026, 07:58 PM UTC

    We will continue to investigate and provide an update shortly. If you are impacted please submit a ticket to Amperity Support. Thank you for your patience.

  2. investigating Aug 27, 2026, 07:58 PM UTC

    We will continue to investigate and provide an update shortly. If you are impacted please submit a ticket to Amperity Support. Thank you for your patience.

  3. identified Aug 27, 2026, 08:28 PM UTC

    The issue has been identified and Amperity is implementing a resolution. We will provide an update in the next 30 minutes.

  4. identified Aug 27, 2026, 08:28 PM UTC

    The issue has been identified and Amperity is implementing a resolution. We will provide an update in the next 30 minutes.

  5. resolved Aug 27, 2026, 09:57 PM UTC

    All services are confirmed stable.

  6. resolved Aug 27, 2026, 09:57 PM UTC

    All services are confirmed stable.

  7. resolved Aug 27, 2026, 09:57 PM UTC

    All services are confirmed stable.

Your product runs on more than Amperity

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →