Puzzle Technology
← All incidents

Conversations Classic Customers Can Experience Issues With Delivery Receipts Functionality

Minor · resolved · started 11 May 2026, 16:17 · resolved 11 May 2026, 17:28

Twilio

  1. resolved · 11 May 2026, 17:28

    Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

  2. monitoring · 11 May 2026, 17:26

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  3. monitoring · 11 May 2026, 17:24

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  4. monitoring · 11 May 2026, 17:22

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  5. monitoring · 11 May 2026, 17:20

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  6. monitoring · 11 May 2026, 17:18

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  7. monitoring · 11 May 2026, 17:16

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  8. monitoring · 11 May 2026, 17:15

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  9. monitoring · 11 May 2026, 17:12

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  10. monitoring · 11 May 2026, 17:10

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  11. monitoring · 11 May 2026, 17:08

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  12. monitoring · 11 May 2026, 17:06

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  13. monitoring · 11 May 2026, 17:04

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  14. monitoring · 11 May 2026, 17:02

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  15. monitoring · 11 May 2026, 17:00

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  16. identified · 11 May 2026, 16:58

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue.

  17. monitoring · 11 May 2026, 16:56

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue. **2026-05-11T15:54:49.555Z** — Conversations Classic is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  18. identified · 11 May 2026, 16:54

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue.

  19. identified · 11 May 2026, 16:52

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue.

  20. identified · 11 May 2026, 16:50

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue.

  21. identified · 11 May 2026, 16:48

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue.

  22. identified · 11 May 2026, 16:46

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue.

  23. identified · 11 May 2026, 16:44

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available. **2026-05-11T15:42:37.984Z** — We are continuing to work on a fix for this issue.

  24. identified · 11 May 2026, 16:18

    **2026-05-11T15:17:33.273Z** — Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available.