Resolved -
Status: Resolved
Start time: Approximately 7:30 AM PT, July 23, 2026
Resolved time: [09:29AM PT, July 23, 2026]
Resolution: BluIP completed a regional change to route AIVA 2.5 speech processing away from the Azure region affected by the upstream Microsoft incident. No users have reported issues since the migration, and speech services have remained stable throughout the monitoring period. This incident is now closed.
Thank you for your patience while we worked through this. Users who experience any further issues should open a ticket with BluIP Support.
Jul 23, 15:56 PDT
Monitoring -
Monitoring — AIVA 2.5 Speech Processing Degradation
Status: Monitoring
Start time: Approximately 7:30 AM PT, July 23, 2026
Update time: [09:35 PT, July 23, 2026]
Update: We have completed a regional change to route AIVA 2.5 speech processing away from the affected Azure region. Text-to-speech and speech-to-text services have returned to normal operation.
Impact: Users should no longer experience failed or delayed TTS/STT responses. Call setup, routing, and all other AIVA functions remain unaffected.
Current action: We are monitoring speech service performance and Microsoft's service health updates for recurrence. This incident will be closed after a sustained period of stable operation. Users who continue to experience issues should open a ticket with BluIP Support.
Thank you for your patience in this matter.
Jul 23, 09:35 PDT
Identified -
Investigating — AIVA 2.5 Speech Processing Degradation
Status: Investigating
Start time: Approximately 7:30 AM PT, July 23, 2026
Impact: Some users may experience issues with AIVA 2.5 speech services. Text-to-speech (TTS) and speech-to-text (STT) requests may fail or return delayed responses, which can result in AIVA not responding audibly or not recognizing spoken input. Call setup, routing, and all other AIVA functions are unaffected.
Cause: This is related to an ongoing Microsoft Azure service incident affecting the speech services used by AIVA 2.5. The issue is upstream of BluIP's network and is being tracked by Microsoft.
Current action: We are monitoring Microsoft's service health updates and validating availability as Azure services are restored. In parallel, we are evaluating alternative speech processing paths to reduce impact if the incident is prolonged. No customer-side action is required.
Thank you for your patience ; we will update as more information becomes available.
Jul 23, 09:29 PDT