Retreaver 中断历史

1. 2026年10月9日 UTC 15:58investigating

   我们检测到了RTB记录出现于我们报告界面(RTB Dashboard)的延迟15分钟. 我们的团队正努力恢复这一点.

2. 2026年10月9日 UTC 18:23resolved

   RTB报告恢复全面运行.

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

1. 2026年9月29日 UTC 12:03investigating

   一小部分用户在生成RTB请求时看到错误

2. 2026年9月29日 UTC 12:07identified

   我们的开发者已经发现了这个问题,并正在努力解决这个问题.

3. 2026年9月29日 UTC 12:13resolved

   RTB 现已投入使用

4. 2026年9月29日 UTC 12:13postmortem

   开发团队注意到RTB出错率激增. 经调查后,采取了补救措施。 收到的RTB申请中,有0.6%受到影响。 由于事件已经解决,不再有请求受到影响.

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

1. 2026年9月29日 UTC 11:38investigating

   呼叫已启动

2. 2026年9月29日 UTC 11:53investigating

   我们正在继续调查这一问题.

3. 2026年9月29日 UTC 11:53resolved

   这件事已经解决了

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

1. 2026年9月23日 UTC 23:13resolved

   协调世界时21:00,有一定比例的RTB流量开始回放超时. 虽然一些出版商在事件中可能收到了超时回复,但总流量没有受到影响. 这个问题在协调世界时22:30前已完全解决.

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

1. 2026年8月5日 UTC 16:43investigating

   我们刚刚看到账号门户上出现大量错误.

2. 2026年8月5日 UTC 17:35monitoring

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

3. 2026年8月5日 UTC 21:01resolved

   This incident has been resolved.

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

1. 2026年8月3日 UTC 14:26investigating

   RTB 入境请求延迟 仪表盘上输入的RTB请求目前遇到比平时更高的延误. 延迟时间通常不到一分钟,但目前更新时间要花很长时间.

2. 2026年8月3日 UTC 17:29resolved

   这一事件已经得到解决.

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

1. 2026年7月14日 UTC 15:20investigating

   用我们的API端点调查一些服务问题

2. 2026年7月14日 UTC 15:54investigating

   我们与我们的东道主是经验问题,它正在影响我们的账户门户和JavaScript。 我们的工程师正在努力把一切重新上线 并很快提供最新消息

3. 2026年7月14日 UTC 17:44monitoring

   API服务恢复运行,我们继续监控我们的服务器,然后才能解决这个地位问题.

4. 2026年7月14日 UTC 18:04resolved

   这一事件已经得到解决.

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

1. 2026年7月13日 UTC 16:38identified

   We are investigating an issue with our RTB servers.

2. 2026年7月13日 UTC 17:06identified

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

3. 2026年7月13日 UTC 17:29monitoring

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

4. 2026年7月13日 UTC 18:02monitoring

   We are continuing to monitor for any further issues.

5. 2026年7月13日 UTC 19:28resolved

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

1. 2026年7月7日 UTC 19:11investigating

   We are currently investigating this issue.

2. 2026年7月7日 UTC 22:17resolved

   This incident has been resolved.

1. 2026年7月2日 UTC 21:43investigating

   We are currently investigating this issue.

2. 2026年7月2日 UTC 21:53monitoring

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

3. 2026年7月2日 UTC 21:57monitoring

   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日 UTC 22:02investigating

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

5. 2026年7月2日 UTC 22:14monitoring

   API service is back online and we are monitoring

6. 2026年7月2日 UTC 23:07resolved

   This incident has been resolved.

1. 2026年5月19日 UTC 22:20identified

   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日 UTC 06:10resolved

   This incident has been resolved.

1. 2026年4月24日 UTC 08:55investigating

   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日 UTC 13:07resolved

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

1. 2026年4月23日 UTC 10:57investigating

   The issue is currently under investigation. Please use Call 1.0

2. 2026年4月23日 UTC 11:19investigating

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

3. 2026年4月23日 UTC 11:58monitoring

   Incident should be resolved. We are monitoring and confirming.

4. 2026年4月23日 UTC 13:09resolved

   This incident has been resolved.

1. 2026年2月25日 UTC 17:55investigating

   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日 UTC 19:00resolved

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

1. 2026年2月20日 UTC 18:36identified

   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日 UTC 19:04monitoring

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

3. 2026年2月20日 UTC 22:44resolved

   Carrier marked as operational

1. 2026年1月22日 UTC 13:06investigating

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

2. 2026年1月22日 UTC 13:27resolved

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

1. 2025年10月20日 UTC 16:35investigating

   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日 UTC 16:44monitoring

   Monitoring the results.

3. 2025年10月20日 UTC 16:44identified

   Monitoring the results.

4. 2025年10月20日 UTC 18:12identified

   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日 UTC 19:44monitoring

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

6. 2025年10月21日 UTC 06:39resolved

   This incident has been resolved.

1. 2025年10月20日 UTC 08:20investigating

   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日 UTC 08:24investigating

   We are continuing to investigate this issue.

3. 2025年10月20日 UTC 11:24monitoring

   Call are processing again. Continuing monitoring

4. 2025年10月20日 UTC 12:58resolved

   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日 UTC 15:23investigating

   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日 UTC 17:39identified

   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日 UTC 23:44identified

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

4. 2025年9月3日 UTC 00:00identified

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

5. 2025年9月3日 UTC 00:06monitoring

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

6. 2025年9月3日 UTC 15:31resolved

   This incident has been resolved.

1. 2025年7月31日 UTC 18:09investigating

   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日 UTC 18:52investigating

   RTB log has caught and all the requests are shown

3. 2025年7月31日 UTC 18:53resolved

   This incident has been resolved.