Retreaver Outage History

Retreaver is up right now

Pingoru has recorded 57 incidents for Retreaver: 16 in the last 12 months and 6 in the last 90 days.

Source: status.retreaver.com

57incidents recorded
16last 12 months
6last 90 days
3 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Retreaver in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202626 of 720 (1%)
May 202618 of 744 (1%)
June 202600 of 720 (0%)
July 2026410 of 744 (1%)
August 202627 of 744 (1%)
September 202632 of 720 (0%)
October 202612 of 527 (0%)

Incidents, newest first

Minor October 9, 2026 RTB Reporting Delayed 2h 25m Reporting

Started Oct 09, 2026, 03:58 PM UTC· resolved Oct 09, 2026, 06:23 PM UTC

  1. investigating Oct 09, 2026, 03:58 PM UTC

    We detected a delay in RTB records showing up in our reporting interfaces (RTB Dashboard) for the last 15 minutes. Our team is working on restoring this.

  2. resolved Oct 09, 2026, 06:23 PM UTC

    RTB reporting is back to fully operational.

Read the full incident report →

Minor September 29, 2026 Users are seeing degraded performance of RTB 9m Real Time Bidding

Started Sep 29, 2026, 12:03 PM UTC· resolved Sep 29, 2026, 12:13 PM UTC

  1. investigating Sep 29, 2026, 12:03 PM UTC

    A small subset of users are seeing errors when making RTB requests

  2. identified Sep 29, 2026, 12:07 PM UTC

    Our developers have found the problem and are working on resolving it.

  3. resolved Sep 29, 2026, 12:13 PM UTC

    RTB is now Operational

  4. postmortem Sep 29, 2026, 12:13 PM UTC

    The development team noticed that there is a spike in RTB error rate. After an investigation a fix was applied. 0\.6% of the received RTB requests were impacted. Since the incident has been resolved and no more requests are impacted.

Read the full incident report →

Minor September 29, 2026 Users are seeing degraded performance. 24m Site/Account Portal, Reporting

Started Sep 29, 2026, 11:38 AM UTC· resolved Sep 29, 2026, 12:02 PM UTC

  1. investigating Sep 29, 2026, 11:38 AM UTC

    Calls are operational

Read the full incident report →

Notice September 23, 2026 RTB reporting timeouts 1h 30m Real Time Bidding

Started Sep 23, 2026, 09:00 PM UTC· resolved Sep 23, 2026, 10:30 PM UTC

  1. resolved Sep 23, 2026, 11:13 PM UTC

    At 21:00 UTC, a percentage of RTB traffic began returning timeouts. Overall traffic volume was unaffected, though some publishers may have received timeout responses during the incident. The issue was fully resolved by 22:30 UTC.

Read the full incident report →

Minor August 5, 2026 Degraded performance on account portal 4h 18m Site/Account Portal

Started Aug 05, 2026, 04:43 PM UTC· resolved Aug 05, 2026, 09:01 PM UTC

  1. investigating Aug 05, 2026, 04:43 PM UTC

    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. monitoring Aug 05, 2026, 05:35 PM UTC

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

  3. resolved Aug 05, 2026, 09:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 3, 2026 RTB reporting delay 3h 3m Real Time Bidding

Started Aug 03, 2026, 02:26 PM UTC· resolved Aug 03, 2026, 05:29 PM UTC

  1. investigating Aug 03, 2026, 02:26 PM UTC

    RTB Inbound Request Delay Inbound RTB requests on the dashboard are currently experiencing higher-than-usual delays. The delay is usually under a minute, but it is currently taking significantly longer to update.

  2. resolved Aug 03, 2026, 05:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 14, 2026 API Issues 2h 44m Site/Account Portal, API

Started Jul 14, 2026, 03:20 PM UTC· resolved Jul 14, 2026, 06:04 PM UTC

  1. investigating Jul 14, 2026, 03:20 PM UTC

    Investigating some service issues with our API endpoints

  2. investigating Jul 14, 2026, 03:54 PM UTC

    We are experience issues with our host and it is now impacting our account portal and JavaScript. Our engineers are working to bring everything back online and will provide an update soon

  3. monitoring Jul 14, 2026, 05:44 PM UTC

    API service is back to operational, we are continuing to monitor our servers before closing out this status issue.

  4. resolved Jul 14, 2026, 06:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 13, 2026 RTB performance is degraded 2h 50m Real Time Bidding

Started Jul 13, 2026, 04:38 PM UTC· resolved Jul 13, 2026, 07:28 PM UTC

  1. identified Jul 13, 2026, 04:38 PM UTC

    We are investigating an issue with our RTB servers.

  2. identified Jul 13, 2026, 05:06 PM UTC

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

  3. monitoring Jul 13, 2026, 05:29 PM UTC

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

  4. monitoring Jul 13, 2026, 06:02 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jul 13, 2026, 07:28 PM UTC

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

Read the full incident report →

Minor July 7, 2026 API requests return slower than normal 3h 6m API

Started Jul 07, 2026, 07:11 PM UTC· resolved Jul 07, 2026, 10:17 PM UTC

  1. investigating Jul 07, 2026, 07:11 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 07, 2026, 10:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 2, 2026 Investigating issue with our API servers 1h 23m API

Started Jul 02, 2026, 09:43 PM UTC· resolved Jul 02, 2026, 11:07 PM UTC

  1. investigating Jul 02, 2026, 09:43 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 02, 2026, 09:53 PM UTC

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

  3. monitoring Jul 02, 2026, 09:57 PM UTC

    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. investigating Jul 02, 2026, 10:02 PM UTC

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

  5. monitoring Jul 02, 2026, 10:14 PM UTC

    API service is back online and we are monitoring

  6. resolved Jul 02, 2026, 11:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 19, 2026 AI Analyst temporarily offline 7h 50m AI features

Started May 19, 2026, 10:20 PM UTC· resolved May 20, 2026, 06:10 AM UTC

  1. identified May 19, 2026, 10:20 PM UTC

    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. resolved May 20, 2026, 06:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 24, 2026 api.retreaver.com is degraded and might return results slower 4h 11m API

Started Apr 24, 2026, 08:55 AM UTC· resolved Apr 24, 2026, 01:07 PM UTC

  1. investigating Apr 24, 2026, 08:55 AM UTC

    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. resolved Apr 24, 2026, 01:07 PM UTC

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

Read the full incident report →

Notice April 23, 2026 Call/RTB Reporting dashboard 2.0 is not loaded 2h 12m Reporting

Started Apr 23, 2026, 10:57 AM UTC· resolved Apr 23, 2026, 01:09 PM UTC

  1. investigating Apr 23, 2026, 10:57 AM UTC

    The issue is currently under investigation. Please use Call 1.0

  2. investigating Apr 23, 2026, 11:19 AM UTC

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

  3. monitoring Apr 23, 2026, 11:58 AM UTC

    Incident should be resolved. We are monitoring and confirming.

  4. resolved Apr 23, 2026, 01:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 25, 2026 RTB heavy load 1h 5m Real Time Bidding

Started Feb 25, 2026, 05:55 PM UTC· resolved Feb 25, 2026, 07:00 PM UTC

  1. investigating Feb 25, 2026, 05:55 PM UTC

    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. resolved Feb 25, 2026, 07:00 PM UTC

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

Read the full incident report →

Minor February 20, 2026 Degraded performance on calls 4h 8m Call Handling

Started Feb 20, 2026, 06:36 PM UTC· resolved Feb 20, 2026, 10:44 PM UTC

  1. identified Feb 20, 2026, 06:36 PM UTC

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

  2. monitoring Feb 20, 2026, 07:04 PM UTC

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

  3. resolved Feb 20, 2026, 10:44 PM UTC

    Carrier marked as operational

Read the full incident report →

Minor January 22, 2026 Reports slowdown detected 21m Reporting

Started Jan 22, 2026, 01:06 PM UTC· resolved Jan 22, 2026, 01:27 PM UTC

  1. investigating Jan 22, 2026, 01:06 PM UTC

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

  2. resolved Jan 22, 2026, 01:27 PM UTC

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

Read the full incident report →

Minor October 20, 2025 AWS degraded 14h 4m Twilio Incoming Phone Calls, Twilio Incoming SIP Calls, Twilio Outgoing Phone Calls, Twilio Outgoing SIP Calls

Started Oct 20, 2025, 04:35 PM UTC· resolved Oct 21, 2025, 06:39 AM UTC

  1. investigating Oct 20, 2025, 04:35 PM UTC

    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. monitoring Oct 20, 2025, 04:44 PM UTC

    Monitoring the results.

  3. identified Oct 20, 2025, 04:44 PM UTC

    Monitoring the results.

  4. identified Oct 20, 2025, 06:12 PM UTC

    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. monitoring Oct 20, 2025, 07:44 PM UTC

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

  6. resolved Oct 21, 2025, 06:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025 AWS outage 4h 38m Twilio Incoming Phone Calls, Twilio Incoming SIP Calls, Twilio Outgoing Phone Calls, Twilio Outgoing SIP Calls

Started Oct 20, 2025, 08:20 AM UTC· resolved Oct 20, 2025, 12:58 PM UTC

  1. investigating Oct 20, 2025, 08:20 AM UTC

    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. investigating Oct 20, 2025, 08:24 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Oct 20, 2025, 11:24 AM UTC

    Call are processing again. Continuing monitoring

  4. resolved Oct 20, 2025, 12:58 PM UTC

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

Read the full incident report →

Minor September 2, 2025 Detected an increase in errors on web portal 1d Site/Account Portal

Started Sep 02, 2025, 03:23 PM UTC· resolved Sep 03, 2025, 03:31 PM UTC

  1. investigating Sep 02, 2025, 03:23 PM UTC

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

  2. identified Sep 02, 2025, 05:39 PM UTC

    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. identified Sep 02, 2025, 11:44 PM UTC

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

  4. identified Sep 03, 2025, 12:00 AM UTC

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

  5. monitoring Sep 03, 2025, 12:06 AM UTC

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

  6. resolved Sep 03, 2025, 03:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 31, 2025 Investigating some RTB calls not showing up in reporting 44m Reporting

Started Jul 31, 2025, 06:09 PM UTC· resolved Jul 31, 2025, 06:53 PM UTC

  1. investigating Jul 31, 2025, 06:09 PM UTC

    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. investigating Jul 31, 2025, 06:52 PM UTC

    RTB log has caught and all the requests are shown

  3. resolved Jul 31, 2025, 06:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 21, 2025 Experiencing delays on reporting 26m Reporting

Started Jul 21, 2025, 02:44 PM UTC· resolved Jul 21, 2025, 03:11 PM UTC

  1. investigating Jul 21, 2025, 02:44 PM UTC

    Investigating an issue with our reporting system

  2. resolved Jul 21, 2025, 03:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2025 Identified an issue impacting a subset of our users when visiting the reporting page 28m Reporting

Started May 06, 2025, 01:01 PM UTC· resolved May 06, 2025, 01:30 PM UTC

  1. identified May 06, 2025, 01:01 PM UTC

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

  2. resolved May 06, 2025, 01:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 3, 2025 Clients using Convoso are experiencing issues 3h 9m Call Handling

Started Apr 03, 2025, 01:48 PM UTC· resolved Apr 03, 2025, 04:58 PM UTC

  1. investigating Apr 03, 2025, 01:48 PM UTC

    https://statusgator.com/services/convoso

  2. identified Apr 03, 2025, 01:59 PM UTC

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

  3. resolved Apr 03, 2025, 04:58 PM UTC

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

  4. postmortem Apr 04, 2025, 06:40 AM UTC

    #### 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.

Read the full incident report →

Minor April 1, 2025 RTB performance degraded 3h 52m Call Handling, Real Time Bidding, Webhooks

Started Apr 01, 2025, 03:03 PM UTC· resolved Apr 01, 2025, 06:55 PM UTC

  1. investigating Apr 01, 2025, 03:03 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 01, 2025, 03:31 PM UTC

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

  3. investigating Apr 01, 2025, 03:32 PM UTC

    We are continuing to investigate this issue.

  4. resolved Apr 01, 2025, 06:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 31, 2025 Investigating an increase in errors from our phone provider (Twilio) 3h 13m Twilio Incoming Phone Calls

Started Mar 31, 2025, 04:02 PM UTC· resolved Mar 31, 2025, 07:16 PM UTC

  1. investigating Mar 31, 2025, 04:02 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 31, 2025, 04:04 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 31, 2025, 04:06 PM UTC

    Twilio provided information about issues with their service: 'Programmable Voice - 11200 HTTP Retrieval Failures' https://status.twilio.com/incidents/djx8tktw4z0p

  4. monitoring Mar 31, 2025, 06:40 PM UTC

    Twilio has updated their status to "operating normally". We will continue monitoring over the next hour.

  5. resolved Mar 31, 2025, 07:16 PM UTC

    This incident has been resolved.

Read the full incident report →