We identified an issue preventing calls from being triggered when a large volume was submitted within a short period of time. In such cases, an internal rate-limiting mechanism was activated, blocking the calls from being triggered.

As a workaround, we provide a dedicated batch webhook endpoint that allows a large number of calls to be triggered at once. Clients should use this endpoint instead of the individual call-triggering endpoint to avoid encountering rate limits.

To address this mor...

Until 2026-02-24 19:15:00 UTC, a misconfigured TTL caused a subset of calls to silently crash. This occurred only when the system was under high load, which is why it affected some calls but not all.

As a result, those calls could not be placed properly and would crash silently. By “silent”, we mean that the calls did crash, but were not marked as such. Consequently, they were effectively “lost” instead of being sent back to our clients’ systems as crashed calls.

As soon as the issue and it...

From 2026-02-13 01:00:00 UTC to 2026-02-20 21:30:00 UTC, calls that hard bounced were incorrectly marked (and therefore routed back) as crashed instead of bounced. This impacted a small subset of calls, as hard bounces are very rare.

A hard bounce, unlike a soft bounce, occurs when a call cannot connect to the destination phone number at all. A soft bounce occurs when the network can reach the phone number, but the recipient is unavailable (e.g., the call goes to voicemail).

Because these c...