Retreaver 장애 기록

1. 2026년 8월 5일 PM 4:43 UTCinvestigating

   Calls and other services are operating fine, we are just seeing an elevated amount of errors on the account portal so marking as degraded.

2. 2026년 8월 5일 PM 5:35 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026년 8월 5일 PM 9:01 UTCresolved

   This incident has been resolved.

1. 2026년 8월 3일 PM 2:26 UTCinvestigating

   RTB 인바운드 요청 지연 대시보드의 인바운드 RTB 요청은 현재 더 높은 대기 지연을 경험하고 있습니다. 지연은 일반적으로 분 미만이지만 현재 업데이트가 크게 길어지고 있습니다.

2. 2026년 8월 3일 PM 5:29 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 7월 14일 PM 3:20 UTCinvestigating

   API endpoints로 일부 서비스 문제를 조사

2. 2026년 7월 14일 PM 3:54 UTCinvestigating

   우리는 우리의 호스트와 함께 경험 문제입니다 지금 우리의 계정 포털 및 JavaScript에 영향을 미치는. 우리의 엔지니어는 다시 온라인 모든 것을 가져오고 갱신을 곧 제공할 것입니다

3. 2026년 7월 14일 PM 5:44 UTCmonitoring

   API 서비스는 가동으로 돌아갑니다, 우리는 이 상태 문제점을 닫기 전에 우리의 서버를 감시하고 있습니다.

4. 2026년 7월 14일 PM 6:04 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 7월 13일 PM 4:38 UTCidentified

   We are investigating an issue with our RTB servers.

2. 2026년 7월 13일 PM 5:06 UTCidentified

   Our engineering team is continuing to work on restoring RTB to full performance.

3. 2026년 7월 13일 PM 5:29 UTCmonitoring

   Service to RTB is improving and we are continuing to monitor it.

4. 2026년 7월 13일 PM 6:02 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2026년 7월 13일 PM 7:28 UTCresolved

   RTB service has been stable for the past 2hrs, marking as resolved.

1. 2026년 7월 7일 PM 7:11 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 7월 7일 PM 10:17 UTCresolved

   This incident has been resolved.

1. 2026년 7월 2일 PM 9:43 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 7월 2일 PM 9:53 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026년 7월 2일 PM 9:57 UTCmonitoring

   We detected some our API servers went offline, our engineers responded, and service has been restored. We will continuing monitoring for a period of time before marking this as resolved.

4. 2026년 7월 2일 PM 10:02 UTCinvestigating

   After restoring service we detected another regression in API servers and are investigating.

5. 2026년 7월 2일 PM 10:14 UTCmonitoring

   API service is back online and we are monitoring

6. 2026년 7월 2일 PM 11:07 UTCresolved

   This incident has been resolved.

1. 2026년 5월 19일 PM 10:20 UTCidentified

   We are working on resolving an issue with our AI model vendor. For the time being disposition analysis and AI chat features on learn.retreaver.com are currently offline. We will mark this as resolved once Retreaver AI services are restored.

2. 2026년 5월 20일 AM 6:10 UTCresolved

   This incident has been resolved.

1. 2026년 4월 24일 AM 8:55 UTCinvestigating

   Requests that were send through the night might have returned HTTP 504. If some ingest processes are dependent on this please be advised that these requests will have to be send again once the incident is resolved.

2. 2026년 4월 24일 PM 1:07 UTCresolved

   Improvements have been deployed and clients should not be experiencing this.

1. 2026년 4월 23일 AM 10:57 UTCinvestigating

   The issue is currently under investigation. Please use Call 1.0

2. 2026년 4월 23일 AM 11:19 UTCinvestigating

   A third party service involved in the reporting are experiencing issues. Working with them on a resolution.

3. 2026년 4월 23일 AM 11:58 UTCmonitoring

   Incident should be resolved. We are monitoring and confirming.

4. 2026년 4월 23일 PM 1:09 UTCresolved

   This incident has been resolved.

1. 2026년 2월 25일 PM 5:55 UTCinvestigating

   Over the last three days, we have observed a recurring industry-wide performance dip between 11:30 AM and 12:30 PM EST. During this window, several external platforms and agencies are experiencing significant RTB latency. Because Retreaver processes these incoming requests and routes them to buyers, this upstream slowdown is resulting in occasional “heavy load” alerts or timeouts. To mitigate this, Ping Shield is actively scaling its protection to stabilize the system. These bursts typically last for 10–15 minutes before service returns to normal. Based on the data we will release a few additional improvements to Ping Shield to help protect against them.

2. 2026년 2월 25일 PM 7:00 UTCresolved

   The incident has been resolved. It is occurring for a limited amount of time.

1. 2026년 2월 20일 PM 6:36 UTCidentified

   A 'carrier' which is used by another 'call tracking provider' which isn’t Retreaver or Twilio is currently experiencing an incident.

2. 2026년 2월 20일 PM 7:04 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026년 2월 20일 PM 10:44 UTCresolved

   Carrier marked as operational

1. 2026년 1월 22일 PM 1:06 UTCinvestigating

   There has been and instance of a report with degraded performance.

2. 2026년 1월 22일 PM 1:27 UTCresolved

   The incident has been resolved the benchmark report ran in a satisfactory amount of time

1. 2025년 10월 20일 PM 4:35 UTCinvestigating

   We are currently experiencing service disruptions across several product lines due to an ongoing AWS outage in their US1 Region. You can track AWS’s official status here: https://health.aws.amazon.com/health/status This incident is impacting many of our connected services and telephony providers, resulting in disruptions across multiple areas of our platform. The issue stems from an ongoing AWS outage in their US1 Region and is the same as the one from a few hours ago.

2. 2025년 10월 20일 PM 4:44 UTCmonitoring

   Monitoring the results.

3. 2025년 10월 20일 PM 4:44 UTCidentified

   Monitoring the results.

4. 2025년 10월 20일 PM 6:12 UTCidentified

   We see calls not connected. We've identified that this is caused by the same issue experienced across the board with Twilio (https://status.twilio.com/) and AWS (https://status.aws.amazon.com/)

5. 2025년 10월 20일 PM 7:44 UTCmonitoring

   We see no issues on our side. At the same time AWS reports that services are still impacted.

6. 2025년 10월 21일 AM 6:39 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 AM 8:20 UTCinvestigating

   We are currently experiencing service disruptions across several product lines due to an ongoing AWS outage in their US1 Region. You can track AWS’s official status here: https://health.aws.amazon.com/health/status This incident is impacting many of our connected services and telephony providers, resulting in disruptions across multiple areas of our platform. The issue stems from an ongoing AWS outage in their US1 Region.

2. 2025년 10월 20일 AM 8:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 10월 20일 AM 11:24 UTCmonitoring

   Call are processing again. Continuing monitoring

4. 2025년 10월 20일 PM 12:58 UTCresolved

   We see no issues on Retreaver at the moment despite the fact the that there are 64 services with degraded performance on AWS.

1. 2025년 9월 2일 PM 3:23 UTCinvestigating

   You may occasionally see an error message with “We’re sorry, something went wrong.” We will be deploying a fix shortly.

2. 2025년 9월 2일 PM 5:39 UTCidentified

   We've identified an issue impacting a very limited set of users. A solution is being implemented. If you come across an error message when accessing our web portal and it's a showstopper, please get in touch with us and we'll find a way to help.

3. 2025년 9월 2일 PM 11:44 UTCidentified

   We detected another spike in errors for a subset of visitors to our website. Our team is investigating.

4. 2025년 9월 3일 AM 12:00 UTCidentified

   Website access has now been restored, we will keep monitoring for any further issues

5. 2025년 9월 3일 AM 12:06 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

6. 2025년 9월 3일 PM 3:31 UTCresolved

   This incident has been resolved.

1. 2025년 7월 31일 PM 6:09 UTCinvestigating

   We are aware of some RTBs not showing up in our RTB Log reporting section. These RTBs are still operational and our engineers are working on resolving the issue so they appear properly in the Log section.

2. 2025년 7월 31일 PM 6:52 UTCinvestigating

   RTB log has caught and all the requests are shown

3. 2025년 7월 31일 PM 6:53 UTCresolved

   This incident has been resolved.

1. 2025년 7월 21일 PM 2:44 UTCinvestigating

   Investigating an issue with our reporting system

2. 2025년 7월 21일 PM 3:11 UTCresolved

   This incident has been resolved.

1. 2025년 5월 6일 PM 1:01 UTCidentified

   This issue will be restored shortly as we are currently rolling out a fix

2. 2025년 5월 6일 PM 1:30 UTCresolved

   This incident has been resolved.

1. 2025년 4월 3일 PM 1:48 UTCinvestigating

   https://statusgator.com/services/convoso

2. 2025년 4월 3일 PM 1:59 UTCidentified

   Convoso have updated their status page with 'likely issue'. Waiting for updates from them

3. 2025년 4월 3일 PM 4:58 UTCresolved

   Convoso's status health is marked as back up. https://statusgator.com/services/convoso/dialer

4. 2025년 4월 4일 AM 6:40 UTCpostmortem

   #### Summary At the start of the business day, several clients reported issues calls. Our team quickly determined that the issue was isolated to clients using Convoso. Other call traffic was unaffected. Over the next hour, additional clients—all using Convoso—experienced the same symptoms. At 9:30 AM EST, Convoso updated their [status page](https://statusgator.com/services/convoso/dialer) indicating a “potential issue.” At 9:40 AM EST, Convoso updated their [status page](https://statusgator.com/services/convoso/dialer) indicating a “likely issue.” We continued monitoring independently. Convoso have acknowledged an incident stating: #### Resolution Convoso resolved the issue on their end. No action was required from our systems.

1. 2025년 4월 1일 PM 3:03 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 4월 1일 PM 3:31 UTCinvestigating

   Customers are complaining that calls are ending on transfer for no apparent reason

3. 2025년 4월 1일 PM 3:32 UTCinvestigating

   We are continuing to investigate this issue.

4. 2025년 4월 1일 PM 6:55 UTCresolved

   This incident has been resolved.