RateQueue Host Down Did Not Recover

resolved · 4 Nov 2026, 18:10

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

monitoring · 4 Nov 2026, 16:14

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available. **2026-11-03T19:13:31.030Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 8 hours or as soon as new information is available. **2026-11-04T03:47:16.214Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 16 hours or as soon as new information is available. **2026-11-04T16:13:36.356Z** — Messaging is operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.

identified · 4 Nov 2026, 03:48

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available. **2026-11-03T19:13:31.030Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 8 hours or as soon as new information is available. **2026-11-04T03:47:16.214Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 16 hours or as soon as new information is available.

identified · 3 Nov 2026, 19:14

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available. **2026-11-03T19:13:31.030Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 8 hours or as soon as new information is available.

identified · 3 Nov 2026, 10:56

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available.

identified · 3 Nov 2026, 10:54

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available.

identified · 3 Nov 2026, 10:52

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available.

identified · 3 Nov 2026, 06:56

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available.

identified · 3 Nov 2026, 04:54

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available

identified · 3 Nov 2026, 02:50

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available

investigating · 3 Nov 2026, 02:16

**2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available