Retreaver Outage History

Retreaver is up right now

Retreaver had 25 outages in the last 2 years totaling 2469h 19m of downtime — averaging 1 incident per month.

There were 25 Retreaver outages since August 23, 2024 totaling 2469h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.retreaver.com

Major July 14, 2026

API Issues

Detected by Pingoru
Jul 14, 2026, 03:20 PM UTC
Resolved
Jul 14, 2026, 06:04 PM UTC
Duration
2h 44m
Affected: Site/Account PortalAPI
Timeline · 4 updates
  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

Detected by Pingoru
Jul 13, 2026, 04:38 PM UTC
Resolved
Jul 13, 2026, 07:28 PM UTC
Duration
2h 50m
Affected: Real Time Bidding
Timeline · 5 updates
  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

Detected by Pingoru
Jul 07, 2026, 07:11 PM UTC
Resolved
Jul 07, 2026, 10:17 PM UTC
Duration
3h 6m
Affected: API
Timeline · 2 updates
  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

Detected by Pingoru
Jul 02, 2026, 09:43 PM UTC
Resolved
Jul 02, 2026, 11:07 PM UTC
Duration
1h 23m
Affected: API
Timeline · 6 updates
  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

Detected by Pingoru
May 19, 2026, 10:20 PM UTC
Resolved
May 20, 2026, 06:10 AM UTC
Duration
7h 50m
Affected: AI features
Timeline · 2 updates
  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

Detected by Pingoru
Apr 24, 2026, 08:55 AM UTC
Resolved
Apr 24, 2026, 01:07 PM UTC
Duration
4h 11m
Affected: API
Timeline · 2 updates
  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

Detected by Pingoru
Apr 23, 2026, 10:57 AM UTC
Resolved
Apr 23, 2026, 01:09 PM UTC
Duration
2h 12m
Affected: Reporting
Timeline · 4 updates
  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

Detected by Pingoru
Feb 25, 2026, 05:55 PM UTC
Resolved
Feb 25, 2026, 07:00 PM UTC
Duration
1h 5m
Affected: Real Time Bidding
Timeline · 2 updates
  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

Detected by Pingoru
Feb 20, 2026, 06:36 PM UTC
Resolved
Feb 20, 2026, 10:44 PM UTC
Duration
4h 8m
Affected: Call Handling
Timeline · 3 updates
  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

Detected by Pingoru
Jan 22, 2026, 01:06 PM UTC
Resolved
Jan 22, 2026, 01:27 PM UTC
Duration
21m
Affected: Reporting
Timeline · 2 updates
  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 →

Major October 20, 2025

AWS degraded

Detected by Pingoru
Oct 20, 2025, 04:44 PM UTC
Resolved
Oct 21, 2025, 06:39 AM UTC
Duration
13h 55m
Affected: Twilio Incoming Phone CallsTwilio Incoming SIP CallsTwilio Outgoing Phone CallsTwilio Outgoing SIP Calls
Timeline · 6 updates
  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

Detected by Pingoru
Oct 20, 2025, 08:20 AM UTC
Resolved
Oct 20, 2025, 12:58 PM UTC
Duration
4h 38m
Affected: Twilio Incoming Phone CallsTwilio Incoming SIP CallsTwilio Outgoing Phone CallsTwilio Outgoing SIP Calls
Timeline · 4 updates
  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

Detected by Pingoru
Sep 02, 2025, 03:23 PM UTC
Resolved
Sep 03, 2025, 03:31 PM UTC
Duration
1d
Affected: Site/Account Portal
Timeline · 6 updates
  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

Detected by Pingoru
Jul 31, 2025, 06:09 PM UTC
Resolved
Jul 31, 2025, 06:53 PM UTC
Duration
44m
Affected: Reporting
Timeline · 3 updates
  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

Detected by Pingoru
Jul 21, 2025, 02:44 PM UTC
Resolved
Jul 21, 2025, 03:11 PM UTC
Duration
26m
Affected: Reporting
Timeline · 2 updates
  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 April 3, 2025

Clients using Convoso are experiencing issues

Detected by Pingoru
Apr 03, 2025, 01:48 PM UTC
Resolved
Apr 03, 2025, 04:58 PM UTC
Duration
3h 9m
Affected: Call Handling
Timeline · 4 updates
  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

Detected by Pingoru
Apr 01, 2025, 03:03 PM UTC
Resolved
Apr 01, 2025, 06:55 PM UTC
Duration
3h 52m
Affected: Call HandlingReal Time BiddingWebhooks
Timeline · 4 updates
  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)

Detected by Pingoru
Mar 31, 2025, 04:02 PM UTC
Resolved
Mar 31, 2025, 07:16 PM UTC
Duration
3h 13m
Affected: Twilio Incoming Phone Calls
Timeline · 5 updates
  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 →

Minor March 6, 2025

Some resources are not loading

Detected by Pingoru
Mar 06, 2025, 12:40 PM UTC
Resolved
Mar 06, 2025, 03:42 PM UTC
Duration
3h 2m
Affected: Site/Account Portal
Timeline · 4 updates
  1. investigating Mar 06, 2025, 12:40 PM UTC

    We have received a complaint that in some cases resources are not loading and some pages cannot be displayed

  2. investigating Mar 06, 2025, 12:40 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 06, 2025, 12:51 PM UTC

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

  4. resolved Mar 06, 2025, 03:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 19, 2025

Reported issue affecting components loading on our website

Detected by Pingoru
Feb 19, 2025, 11:40 PM UTC
Resolved
Feb 20, 2025, 12:02 PM UTC
Duration
12h 22m
Affected: Site/Account Portal
Timeline · 4 updates
  1. investigating Feb 19, 2025, 11:40 PM UTC

    We're experiencing issues with a small number of components not loading in our web app, such as the datepicker in Call Log. This has only been reported by a subset of users and may not impact everyone. Our development team is investigating.

  2. investigating Feb 20, 2025, 12:00 PM UTC

    UI components are loading.

  3. investigating Feb 20, 2025, 12:01 PM UTC

    We are continuing to investigate this issue.

  4. resolved Feb 20, 2025, 12:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 31, 2025

Purchasing new local (non toll-free) numbers is temporary disabled for certain area codes.

Detected by Pingoru
Jan 31, 2025, 01:28 PM UTC
Resolved
May 09, 2025, 11:55 AM UTC
Duration
97d 22h
Affected: Site/Account Portal
Timeline · 2 updates
  1. investigating Jan 31, 2025, 01:28 PM UTC

    Vendors providing the numbers are experiencing difficulties and we've temporary disabled the ability to purchase certain local area codes.

  2. resolved May 09, 2025, 11:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 4, 2024

Investigating issue with our background jobs system

Detected by Pingoru
Oct 04, 2024, 08:18 PM UTC
Resolved
Oct 04, 2024, 09:41 PM UTC
Duration
1h 22m
Affected: Background Jobs
Timeline · 2 updates
  1. investigating Oct 04, 2024, 08:18 PM UTC

    This may impact routing of calls and outbound API requests .

  2. resolved Oct 04, 2024, 09:41 PM UTC

    This incident has been resolved

Read the full incident report →

Minor August 23, 2024

Investigating Carrier Issue

Detected by Pingoru
Aug 23, 2024, 03:17 PM UTC
Resolved
Aug 23, 2024, 03:47 PM UTC
Duration
30m
Affected: Twilio Incoming Phone Calls
Timeline · 3 updates
  1. investigating Aug 23, 2024, 03:17 PM UTC

    We are seeing carrier issues where some calls are not correctly marked as completed.

  2. investigating Aug 23, 2024, 03:17 PM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 23, 2024, 03:47 PM UTC

    This incident has been resolved.

Read the full incident report →