Instagram 直接信件被延迟摄入
Outage重大事件
受影响的组件
Instagram Direct Messages
- identified
我们意识到一个问题 可能导致延迟 在戈尔吉亚斯接收Instagram直接消息。 信息不会丢失,它们会比通常时间晚到。 我们的小组正在调查和努力恢复正常的交货时间.
- monitoring
一项措施已经执行,我们正在监测结果.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
71 Gorgias incidents · 2025年11月 — official updates, affected components, duration and resolution details.
我们意识到一个问题 可能导致延迟 在戈尔吉亚斯接收Instagram直接消息。 信息不会丢失,它们会比通常时间晚到。 我们的小组正在调查和努力恢复正常的交货时间.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们的上游电话供应商Twilio目前正在经历一起影响语音服务的事件(status.twilio.com)。 因此,一些客户在戈尔吉亚斯可能会遇到语音调用功能被退化或失败——包括呼叫失败或延迟和不准确的调用测试结果. 短消息和所有其他Gorgias功能(电子邮件,聊天,帮助台)不受影响. 特维里奥的工程团队已经确定了原因,正在部署固定装置. 我们正在监测情况,一旦恢复服务或掌握更多信息,我们将更新这一页。 您一方无需采取任何行动.
影响我们上游电话供应商Twilio的事件已经得到解决。 Gorgias的语音调用功能已恢复正常,包括调用测试结果.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
我们看到复苏的迹象,我们继续监视我们的服务
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
我们正在继续努力解决这个问题。
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
Between 4:30 PM and 8:00 PM UTC on August 10th, some customers using the WhatsApp integration saw unexpected ticket behavior. New tickets were created with older messages, and some previously closed tickets reopened with older messages added to them, which in some cases produced duplicates. Current status: The underlying issue is resolved and normal WhatsApp message processing has resumed. We are investigating the billing impact for affected accounts. Impact: - Closed WhatsApp tickets reopened unexpectedly, with older messages added to them. - Some accounts may have had new or duplicate tickets created during the affected window. - Ticket counts during that period may have been inflated, which could affect billing. We are reviewing this. What to know: We did not close or merge affected tickets ourselves. Deciding which ticket to keep depends on your workflow, and we can't make that call for you. Some merchants have also already cleaned up the data on their end, so running an automated cleanup risked overwriting changes you'd made or leaving you with a state you didn't want. Use the filters below to find the duplicated and newly created tickets, then bulk-close them as appropriate. How to identify affected (duplicated/created) tickets: Apply these filters in your helpdesk. All times are UTC, so convert to your helpdesk timezone: - Channel: WhatsApp - Created before: August 10, 2026 at 20:30 UTC - Created after: August 10, 2026 at 16:00 UTC - Last shopper message received: between July 23, 2026 at 17:00 UTC and August 10, 2026 at 18:00 UTC - Status: Open (or other status filters relevant to your workflow) Billing: We are working to remove the tickets created by this incident from your billing. We will follow up once this is complete.
The WhatsApp ticket issue that occurred on August 10th between 4:30 PM and 8:00 PM UTC is now fully resolved. **What happened:** A replay of WhatsApp webhooks caused older messages to be imported, which resulted in closed tickets reopening and, in some cases, duplicate tickets being created. **Billing:** Billable tickets created as a result of this incident have been removed from affected merchants' billing counts. Please note that billing corrections may take a bit of time to reflect in your account. Merchants who were already charged before this correction was applied will receive a refund in the following days — our team will reach out as needed. **What's next:** A public post-mortem detailing the root cause, impact, and steps taken to prevent recurrence will be published by tomorrow, August 13th, at the latest. We sincerely apologize for the disruption this caused to your workflows. Thank you for your patience.
On August 10, 2026, between approximately 4:30 and 8:00 PM UTC, some WhatsApp tickets unexpectedly reopened or duplicated. We understand how disruptive that is when you're trying to stay on top of customer conversations, and we'd like to walk you through what happened and how to tidy things up. **What happened** Between July 23 and August 10, a separate issue had prevented some inbound WhatsApp messages from reaching Gorgias. On August 10 we fixed it and ran a recovery to bring those messages in. As the older messages arrived, our system read them as brand-new activity, so it created new tickets, reopened some closed ones, and in a few cases produced duplicates. **What you may have seen** During that window you may have seen reopened, new, or duplicate WhatsApp tickets, auto-replies that didn't send, and brief delays on new messages. Because of the extra tickets, your ticket counts for that period may also have looked higher than usual. **What we did** We finished restoring the missing messages and fixed the underlying cause of the duplicates to prevent a recurrence. We also corrected the billing impact: the tickets this incident created have been removed from your bill, so you won't be charged and no action is needed on your side. The tickets themselves stay in your helpdesk, so you can review or close them as you see fit. **What you can do** We didn't close or merge any tickets for you, since you know your workflow best and some teams had already tidied things up. If you'd like to clean up, the search below surfaces the new and duplicate tickets created during the window \(it won't include tickets that were reopened when an older message was added to them\). Apply these criteria to your tickets. All times are in UTC, so convert them to your helpdesk timezone: * Channel: WhatsApp * Created between August 10, 2026 16:00 and 20:30 UTC * Last customer message between July 23, 2026 17:00 UTC and August 10, 2026 18:00 UTC Then bulk-close whatever you don't need. **What's next** We're strengthening how we handle large message recoveries and expanding our monitoring so issues like this are caught and addressed earlier. We sincerely apologize for the disruption and any confusion it may have caused you and your customers, and we thank you for your patience.
We are currently investigating this issue. Some users may experience issues during signup
The issue has been resolved
我们目前正在调查这一问题.
Gmail集成正常恢复同步,新邮件正在按预期制作票. 从Gmail发送的通知停止,然后自行恢复,我们方面没有任何改变。 我们发现我们的系统没有问题,这表明其原因是外部的。 我们正在监测 以确认稳定 之前标记这一点解决.
我们的应用程序的Gmail通知流量恢复到正常水平.
自动翻译自官方事件更新。
我们的一个数据库暂时无法使用。 因此,一些电子商务数据无法通过我们的服务获得。 我们正在调查这一问题并努力尽快恢复全部功能.
我们的一个数据库暂时无法使用。 因此,一些电子商务数据无法通过我们的服务获得。 我们正在调查这一问题并努力尽快恢复全部功能。 该问题从协调世界时的10:56一直持续到11:28. 该数据库现已投入使用,服务已经恢复.
A transient network issue has been resolved, and all queued requests have been processed. All services are now operational.
自动翻译自官方事件更新。
我们目前正在调查这一问题。 我们-中央1-df88的实时更新可能滞后
我们正在继续努力解决这个问题。
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
发生的事情:在协调世界时01:43至02:25之间,一些客户经历了Helpdesk反应缓慢或失败以及间歇性登录问题. 影响仅限于一个单一的基础设施集群(US-east1-2607)。 原因: 我们云层存储层的暂时断层 隔离到一个数据中心区 这是一个基本的基础设施问题,不是戈尔吉斯应用问题,也不是我们一方的变化。 分辨率:我们的系统通过内置故障自动恢复。 没有丢失数据,不需要人工干预。 下一步:我们将与我们的云提供商一起审查这一事件,并评估进一步加强抵御这一类问题的措施. 我们为中断道歉, 你可以联系你的支持 联系任何问题.
自动翻译自官方事件更新。
我们已经查明了AI代理API错误率上升的原因. 在此期间,一些AI代理请求可能失败或被延迟,对受影响罚单的自动响应可能不会被发送. 我们的团队正在积极研究一个恢复全面服务的解决方案.
这一事件已经得到解决.
自动翻译自官方事件更新。
在协调世界时7月14日8:00至18:30之间,我们第三方的ML供应商之一的基础设施问题导致AI Agent的知识检索间歇性故障. 在这个窗口中,AI Agent在编集解答时并不总是收集到知识来源(Help Center文章和指南),并且可以仅根据对话背景来进行回击. 一些基于意图的自动化(规则和路线)也受到了间歇性的影响.
自动翻译自官方事件更新。
从 Store 网站和 Knowledge 的 URL 源头同步内容对于许多商店都是失败的. 我们正在调查这个问题。 现有内容不受影响.
从 Store 网站和 Knowledge 的 URL 源头同步内容对于许多商店都是失败的. 我们正在调查这个问题。 现有内容不受影响.
解决了Store网站同步问题 我们正在监测局势.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
我们正在部署一个固定
这一事件已经得到解决.
自动翻译自官方事件更新。
由于交通量激增,一些客户可能需要很长时间来进行分析。 我们已经查明了根源,并促成了一个解决办法。 如果您仍然遇到问题,您应该尝试在浏览器中重新装入应用程序.
根本原因已经解决,我们目前正在监测这些服务.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们发现了一个影响查票的问题。 由于大约9:19 AM CEST,搜索结果可能不包括最新入场券或反映对现有入场券的最新更新. 车票本身没有受到影响——这些车票正在正常接收和处理,搜索之外的所有功能继续如预期的那样运作.
车票查询现已更新. 9:19 AM到10:34 AM CEST之间,由于一个集群的基础设施问题,最近制作或更新的门票可能没有出现在搜索结果中. 这项工作已经固定,所有有待更新的内容均已处理完毕。 车票本身从未受到影响.
自动翻译自官方事件更新。
欧洲西部3组的客户可能在其观点中看到陈旧的数据——包括票数不正确或缺失。 其他区域没有受到影响。 我们的团队正在积极寻找解决办法,一旦解决,将提供最新情况.
我们正在继续调查这一问题.
我们缓解了影响欧洲西部3组观点的问题。 车票清点和查看数据现在应该正在更新,但性能仍然退化,更新可能比通常需要更长的时间. 我们正在监测局势,并将为充分解决这一问题采取明确措施.
此事已决. 截至12:57 CEST(协调世界时10:57),欧洲-西3集群的取景和票点已完全投入使用并正常更新. 我们进行了修改,以提高数据摄取的可靠性,并确认了查看数据和票数准确和最新。 性能恢复正常了 其他地区从未受到影响。 我们为这可能造成的任何不便感到抱歉,谢谢你的耐心.
自动翻译自官方事件更新。
We identified that the Shopify API is experiencing some degraded performance. That means some of our customers may experience some issues in regards to the Shopify actions. That includes the manual actions and the actions that are performed by the AI agent on Shopify, but also the historical sync. Shopify status page: https://www.shopifystatus.com/. We will provide the next update in 1 hour.
We are continuing to monitor this issue.
This incident has been resolved. Shopify fixed the outage on their side.