Advicepay 장애 기록

1. 2026년 10월 23일 오후 4:26 UTCmonitoring

   9:41AM MDT에서 9:55AM MDT에, 우리는 AdvicePay 신청과 우리의 역행 줄무늬 인스턴스 사이에서 영향을 받는 간단한 문제점이 있었습니다. 이 문제는 해결되었습니다. 우리는 영향을 조사하고 있습니다.

2. 2026년 10월 23일 오후 8:01 UTCresolved

   이 사건은 해결됩니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 21일 오후 3:15 UTCmonitoring

   광범위한 PHP 취약점 때문에 Dropbox는 Dropbox Sign을 오프라인으로 가져 왔습니다. Core AdvicePay 서비스, 결제 처리, Docusign 및 Acrobat Sign은 문제없이 제대로 운영됩니다. 현재 프로세스에 Dropbox Sign을 사용한다면 서명 요청을 보낼 수 없습니다. AdvicePay는 이 사건을 감시하고 업데이트하는 것을 계속할 것입니다.

2. 2026년 10월 21일 오후 4:19 UTCresolved

   Dropbox는 취약점과 Dropbox Sign을 올바르게 패치했습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 4월 6일 오후 3:56 UTCresolved

   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일 오후 3:41 UTCinvestigating

   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일 오전 1:32 UTCresolved

   This incident has been resolved.

1. 2023년 4월 19일 오후 5:54 UTCresolved

   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일 오후 6:59 UTCpostmortem

   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일 오후 3:32 UTCresolved

   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일 오후 9:01 UTCresolved

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

1. 2021년 10월 1일 오후 3:17 UTCresolved

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

1. 2021년 10월 1일 오후 3:16 UTCresolved

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

1. 2021년 8월 10일 오후 4:04 UTCresolved

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

1. 2021년 8월 10일 오후 4:02 UTCresolved

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

1. 2021년 7월 1일 오후 3:13 UTCresolved

   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일 오후 3:12 UTCresolved

   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일 오후 11:51 UTCresolved

   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일 오후 3:14 UTCpostmortem

   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일 오후 10:21 UTCresolved

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

2. 2020년 5월 19일 오전 12:28 UTCpostmortem

   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.