Dialbotix status

A fix was deployed and connection latency has returned to normal. Root cause was a capacity limit on one telephony carrier route during a regional traffic spike; overflow routing has been tuned to prevent recurrence.

Call routing has been shifted to a backup carrier path. Latency is back within normal range and we're monitoring before marking this resolved.

We've identified elevated latency on outbound call connections tied to a single telephony carrier route. Traffic is being rerouted.

We're investigating reports of slower-than-normal call connection times for some outbound campaigns.

Webhook delivery has fully caught up and is running in real time. The queue backlog was caused by a downstream rate limit from HubSpot's API during a burst of contact syncs; we've added backoff handling to avoid a repeat.

The backlog is draining steadily. New webhooks are being delivered in real time; queued events are catching up.

Webhook deliveries to HubSpot are queueing rather than failing. No data has been lost — deliveries are simply delayed.

We're investigating delayed webhook deliveries affecting the HubSpot integration. Other integrations are unaffected.

Realtime updates (live call status, transcripts) are back to normal latency. The issue was a memory pressure spike on one realtime server node, which has since been resized.

We've restarted the affected realtime server node and update latency has dropped back to normal. Continuing to monitor.

Some users may see delayed live-call and transcript updates on the dashboard. Calls themselves are not affected — this is a display delay only.