Degraded Web Asset Delivery

Incident Report for Churnkey

Resolved

A CloudFront cache served a 501 error for certain web assets (used by Cancel Flows, and other Churnkey embeds). Cache purged; assets loading normally.

[Timeline]
• 01:35 AM — CloudFront edge cached a 501 response
• 02:05 AM — Elevated 501 errors detected
• 03:30 AM — Root cause isolated to single edge cache
• 04:15 AM — Cache purged, error rate falling
• 06:08 AM — Confirmed stable; incident closed

[Impact]
Some end-users saw blank or delayed Churnkey components (Retention Flows and Payment Components)

Posted Jul 01, 2025 - 08:00 UTC