Advicepay 中断历史

1. 2026年10月23日 UTC 16:26monitoring

   从9:41AM MDT到9:55AM MDT,我们有一个影响AssociationPay应用程序与我们支持的Frede实例之间的连通性的简短问题. 这个问题已经解决,我们正在调查其影响.

2. 2026年10月23日 UTC 20:01resolved

   此事已决.

自动翻译自官方事件更新。

1. 2026年10月21日 UTC 15:15monitoring

   由于PHP的弱点很普遍,Dropbox已经将Dropbox Sign下线. 核心咨询服务、付款处理、Docusign和Acrobat Sign正在正常运行,没有问题。 如果您目前对您的进程使用 Dropbox 标志, 您将无法发送签名请求 。 咨询处将继续监测这一问题并更新这一事件.

2. 2026年10月21日 UTC 16:19resolved

   Dropbox已经补齐了弱点, Dropbox Sign 正在正常运行中.

自动翻译自官方事件更新。

1. 2026年4月6日 UTC 15:56resolved

   An anti-fraud measure that resulted in clients being unable to manually enter bank account information for future-due subscriptions without upfront payments has been resolved.

1. 2025年10月20日 UTC 15:41investigating

   We’re currently experiencing partial disruption due to a widespread AWS outage affecting several third-party services and integrations. Our core platform remains accessible, but some connected features may be slow or temporarily unavailable. Please also note that response times from our Support team may be delayed as a result of this outage. We’re monitoring the situation closely and will provide updates as AWS restores services. Thank you for your patience.

2. 2025年10月21日 UTC 01:32resolved

   This incident has been resolved.

1. 2023年4月19日 UTC 17:54resolved

   At 11:37 AM MDT on 4/19/2023 we received an alert from our uptime monitoring service that the AdvicePay application was unreachable. Functionality was restored as of 11:50 AM MDT. We are investigating the underlying cause.

2. 2023年5月18日 UTC 18:59postmortem

   AWS S3 was having issues with very high latency on the day of the outage. Additionally, AdvicePay was using a default HTTP client without a timeout to request firms' logo images from S3. The combination of those two issues led to a denial of service due to starvation of connections on our servers. AWS has since resolved things on their end. To protect against this issue in the future, AdvicePay has implemented timeouts for all HTTP clients that we use for requesting any resource.

1. 2022年4月1日 UTC 15:32resolved

   A large number of quarterly requests from our payment processor resulted in slow response times on AdvicePay's production site from 12:00 AM to 12:01 AM.

1. 2021年12月1日 UTC 21:01resolved

   A series of requests from a third party resulted in slow response times from 9:02-9:04 PM MDT

1. 2021年10月1日 UTC 15:17resolved

   A series of requests from a third party resulted in slow response times from 1:04-1:05 AM MDT

1. 2021年10月1日 UTC 15:16resolved

   A series of requests from a third party resulted in slow response times from 11:02-11:03 PM MDT

1. 2021年8月10日 UTC 16:04resolved

   A series of requests from a third party resulted in slow response times from 1:03-1:04 AM MDT

1. 2021年8月10日 UTC 16:02resolved

   A series of requests from a third party resulted in slow response times from 10:02-10:04 PM MDT

1. 2021年7月1日 UTC 15:13resolved

   An unexpected large number of webhook calls from one of AdvicePay's integration partners resulted in slow response times from 3:00AM until 3:02AM while we processed the calls.

1. 2021年7月1日 UTC 15:12resolved

   An unexpected large number of webhook calls from one of AdvicePay's integration partners resulted in slow response times from 1:00AM until 1:02AM while we processed the calls.

1. 2020年7月31日 UTC 23:51resolved

   On 7/29/2020, from 8:47 AM until 9:06 AM (MDT) a bad gateway issue prevented users from accessing the AdvicePay production site.

2. 2021年7月1日 UTC 15:14postmortem

   This issue was due to a memory leak when generating invoice PDFs for a large amount of historical data. As a result, we implemented better fault tolerance on the server instances.

1. 2020年5月18日 UTC 22:21resolved

   A server issue occurred preventing access to the production instance AdvicePay.

2. 2020年5月19日 UTC 00:28postmortem

   AdvicePay’s server instances were upgraded to faster hardware, which uncovered a code issue that resulted in a race condition. The race condition was a low-level issue that caused a server panic.