SIP呼叫失败
在我们最近的缓解措施之后,工程师已追踪到SIP呼叫失败率已恢复至基线水平。我们将很快发布完整的根本原因分析。
原文After our recent mitigation steps, our engineers have traced SIP call failure rate as it has returned to baseline. We will publish a complete root cause analysis shortly.
我们的工程师正在制定一项针对性修复方案,以解决美国区域剩余的SIP故障。
原文Our engineers are putting together a targeted fix to resolve the remaining SIP failures in the US region.
我们已确定SIP呼叫失败的根本原因,并准备了修复方案。
原文We have identified the root cause of the failed SIP calls and prepared a fix.
我们的团队仍在积极努力,将所有通话和电话号码恢复正常工作状态。
原文Our team is still actively working to restore all calls and phone numbers to their normal working state.
欧盟和印度地区的通话应已恢复正常。美国地区可能仍会经历一些中断,但我们的团队正在努力解决问题。在此期间,如果可能的话,立即的解决办法是移除受影响的号码并重新添加。
原文Calls should be back to normal for the EU and India residencies. The US residency may still experience some downtime, but our team is working to resolve the issue. In the meantime, the immediate workaround is to remove the affected number and re-add it, if possible.
我们的团队已确定通话中断的一个潜在原因,并正在验证修复方案。一旦有更多信息,我们将及时分享最新进展。
原文Our team has identified a potential cause of the call outages and is currently validating a fix. We will share further updates as soon as we have more information.
在之前的修复之后,我们注意到部分电话号码再次出现入站呼叫路由失败的情况。我们正在调查中。
原文Following the earlier fix, we're seeing renewed inbound call routing failures for a portion of phone numbers. We're currently investigating.
问题已解决。呼叫路由现已完全恢复,我们正在评估后续措施,以改进主动告警并防止问题再次发生。
原文The issue has been resolved. Call routing is now fully restored, and we're assessing follow-ups to improve proactive alerting and prevent recurrence.
我们已识别出一个可能的影响因素,与基础设施资源限制有关,影响了SIP呼叫路由。目前正在验证修复方案。
原文We've identified a likely contributing factor related to infrastructure resource constraints affecting SIP call routing. We're currently validating a fix.
自大约1:00 UTC起,导入到ElevenLabs Agent Platform的部分电话号码的呼叫失败。我们目前正在努力隔离根本原因并恢复全部功能。
原文Starting at ~1:00 UTC, calls to a portion of phone numbers imported into the ElevenLabs Agent Platform are failing. We are currently working to isolate the root cause and restore full functionality.
关于这些数据
事件从哪来?
全部来自各厂商官方状态页的公开接口,由本站每 5 分钟同步一次,保留最近 90 天。事件标题、时间、影响级别与更新记录均为官方原文,本站不做改写;点详情页底部的链接可回到厂商原始记录核对。
为什么有的服务查不到历史?
本页只收录对外提供官方状态页的服务。没有公开状态页的厂商(多数国产大模型属于此类)无法取得可信数据,本站不做自建拨测去猜,因此也不会出现在状态总览里。
持续时长怎么算?
按官方标注的开始时间到恢复时间计算;尚未恢复的事件按「至今」计算并标为进行中。跨天的事件在状态条上会覆盖它经过的每一天。