Resolved on June 11, 2025, affecting section-160679 (Login).
We are currently investigating an issue where certain clients are unable to access the Keka application due to a Content Delivery Network (CDN) caching and propagation anomaly. This appears to be affecting tenant-specific assets or login endpoints, causing partial or complete service disruption for impacted users. Our engineering team has identified that some edge nodes may be serving stale or corrupted content due to improper cache invalidation or TTL (time-to-live) configuration. 🛠 Next Steps: We are performing a CDN cache purge and forcing revalidation of content across all PoPs (Points of Presence). DNS-level inspection and propagation checks are underway to ensure edge resolution consistency. We will continue to provide updates as we mitigate the issue. Thank you for your patience and understanding.
Affected components
Update timeline
- resolved Jun 11, 2025, 01:30 AM UTC
We are currently investigating an issue where certain clients are unable to access the Keka application due to a Content Delivery Network (CDN) caching and propagation anomaly. This appears to be affecting tenant-specific assets or login endpoints, causing partial or complete service disruption for impacted users. Our engineering team has identified that some edge nodes may be serving stale or corrupted content due to improper cache invalidation or TTL (time-to-live) configuration. 🛠 Next Steps: We are performing a CDN cache purge and forcing revalidation of content across all PoPs (Points of Presence). DNS-level inspection and propagation checks are underway to ensure edge resolution consistency. We will continue to provide updates as we mitigate the issue. Thank you for your patience and understanding.
Your product runs on more than Keka
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services