Previous incidents

This incident has been resolved. No user traffic was affected - all requests were handled by our stable service

During a routine deployment, an internal configuration change introduced an inconsistency in our traffic routing system, causing an internal reconciliation loop. No user traffic was affected - all requests were served by the stable service throughout. The affected deployment was rolled back and normal operation was restored.

We are currently experiencing outbound call failures for customers using our RingCentral integration configured with the sip12.ringcentral.com SIP proxy. This only affects customers on that specific configuration. All other Synthflow customers are unaffected.

Calls may fail with a “403 Forbidden” response.

Our team is actively working with RingCentral to resolve the issue as quickly as possible. At this time, the impact is limited to customers routed through the sip12 registrar.

We will pr...

We have identified cases where the voice agent prematurely terminates speech output during a response. This is due an external vendor issue we are investigating.