Resolved after 23 hours 14 minutes, on October 15, 2024.
Transitioning this disruption to a resolved status. After monitoring the system overnight - no further instances of misbehavior or resurgence of the issue have been identified. Please reach out to our Customer Care team via a support request if misbehavior with the logging application resurface. .
Update timeline
- investigating Oct 15, 2024, 01:45 PM UTC
We are currently investigating an issue with the logging services. Please note, this issue is **not affecting call processing or functionality**, and all calls are being handled as expected. Our team is actively working to identify the cause and resolve the issue as soon as possible. We will provide updates as more information becomes available..
- monitoring Oct 15, 2024, 02:43 PM UTC
We’ve identified the issue and implemented a fix. Logging is now working correctly for all calls made after the fix. Our systems are currently processing the logs from calls made during the incident, and once the backlog is cleared, they will be available for review. To clarify, no data has been lost—our systems are simply processing through the queue. We’ll continue to monitor the system and provide updates as needed..
- resolved Oct 16, 2024, 12:59 PM UTC
Transitioning this disruption to a resolved status. After monitoring the system overnight - no further instances of misbehavior or resurgence of the issue have been identified. Please reach out to our Customer Care team via a support request if misbehavior with the logging application resurface. .
Your product runs on more than Plum Voice
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