迟发的机票转让通知
Outage重大事件
- investigating
我们目前正在调查这一问题.
- identified
我们正在继续努力解决这个问题。
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
82 Gorgias incidents · 2025年11月 — official updates, affected components, duration and resolution details.
我们目前正在调查这一问题.
我们正在继续努力解决这个问题。
这一事件已经得到解决.
自动翻译自官方事件更新。
我们知道Shopify商店有针对第三方应用的运动, 在初步调查之后,我们可以证实我们没有证据表明戈尔吉亚斯受到影响。 我们的工程组正在积极监测局势,我们正在核实我们为你们提供的脚本的完整性。 我们一收到更多信息,就会发出最新消息。 我们建议审查你店里的第三方应用, 如果你看到与Gorgias有关的异常情况,请联系我们@gorgias.com.
我们的工程团队继续调查 肖菲第三方应用安全运动。 此时,我们没有证据表明戈尔吉亚斯受到了影响. 我们正在继续核查我们库存前台脚本的完整性并监测收到的客户报告。 随着调查的进展,我们将继续提供最新情况。 如果您发现任何与Gorgias有关的可疑行为,请联系支持@gorgias.com
我们认为这一事件已经解决,因为我们没有证据表明戈尔吉亚斯受到影响。 作为调查的一部分,我们: - 检查我们店面和退房代码(聊天、自助服务、转换和我们店面扩展),以了解每一个已知的妥协指标。 我们发现没有。 - 审查了过去30天的基础设施和CDN日志 用于我们所服务的脚本 存储封面和退票。 我们没有发现任何篡改或虐待的迹象。 - 证实我们的剧本 和我们制造的管道完全一致 作为预防措施,我们正在采取额外的强化措施,并遵循Shoppify对应用伙伴的安全建议. 我们的工程队将继续密切监测局势。 我们仍建议店主审查在店里安装的第三方应用程序, 如果你看到与Gorgias有关的异常情况,请联系我们@gorgias.com.
自动翻译自官方事件更新。
使用循环返回(Loop Return)的动作可能会因为循环持续出事而被延迟或失败. 其他行动不受影响。 循环恢复后我们分享最新消息.
循环回归解决了他们的事件,使用循环回归的工作流程动作也正常运行.
自动翻译自官方事件更新。
我们在空召V2集成中发现了一个问题,这个问题由空召自己管理. 详情请查询:https://status.aircall.com/incicents/8v8s2hp1pj66
空中呼叫已经解决了他们一方的问题 参见现状页面更新:https://status.aircall.com/incicents/8v8s2hp1pj66. 我们正在监控空中呼叫V2集成交通 以确认修复.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
我们正在继续努力解决这个问题。
一项措施已经执行,我们正在监测结果,局势正逐步恢复正常.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正监视局势。 问题似乎站在LLM提供者一边
外部LLM提供商面临高耐用性,影响了AI代理的响应时间.
外部LLM提供商面临高耐用性,影响了AI代理的响应时间.
自动翻译自官方事件更新。
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
我们查明了这个问题,目前正在就该决议积极努力.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
我们正在继续努力解决这个问题。
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个可能阻止Gorgias新账户 创建帮助中心的问题
事情已经解决了
自动翻译自官方事件更新。
我们意识到一个问题 可能导致延迟 在戈尔吉亚斯接收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的实时更新可能滞后
我们正在继续努力解决这个问题。
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。