58 Retreaver incidents · Oktober 2016 — official updates, affected components, duration and resolution details.
Wir haben eine Verzögerung bei RTB-Datensätzen festgestellt, die in den letzten 15 Minuten in unseren Berichtsschnittstellen (RTB Dashboard) angezeigt wurden. Unser Team arbeitet daran, dies wiederherzustellen.
Die RTB-Berichterstattung ist wieder voll funktionsfähig.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Eine kleine Untergruppe von Benutzern sieht Fehler beim Erstellen von RTB-Anfragen
Unsere Entwickler haben das Problem gefunden und arbeiten daran, es zu lösen.
RTB ist jetzt in Betrieb
Das Entwicklungsteam bemerkte, dass es einen Anstieg der RTB-Fehlerrate gibt. Nach einer Untersuchung wurde ein Fix angewendet. 0\,6% der empfangenen RTB-Anfragen waren betroffen. Da der Vorfall behoben wurde und keine weiteren Anfragen mehr betroffen sind.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Anrufe sind betriebsbereit
Wir werden dieses Problem weiter untersuchen.
Dieser Vorfall wurde behoben
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Um 21:00 UTC begann ein Prozentsatz des RTB-Verkehrs, Timeouts zurückzugeben. Das Gesamtverkehrsvolumen war nicht betroffen, obwohl einige Publisher während des Vorfalls Timeout-Antworten erhalten haben könnten. Das Problem wurde bis 22:30 UTC vollständig gelöst.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Calls and other services are operating fine, we are just seeing an elevated amount of errors on the account portal so marking as degraded.
Ein Fix wurde implementiert und wir überwachen die Ergebnisse.
This incident has been resolved.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
RTB Inbound Request verzögert sich Inbound RTB-Anfragen auf dem Dashboard haben derzeit höhere Verzögerungen als üblich. Die Verzögerung ist in der Regel unter einer Minute, aber es dauert derzeit deutlich länger zu aktualisieren.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Untersuchung einiger Serviceprobleme mit unseren API-Endpunkten
Wir haben Probleme mit unserem Host und es hat jetzt Auswirkungen auf unser Kontoportal und JavaScript. Unsere Ingenieure arbeiten daran, alles wieder online zu bringen und werden bald ein Update bereitstellen
Der API-Service ist wieder in Betrieb, wir überwachen weiterhin unsere Server, bevor wir dieses Statusproblem schließen.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
We are investigating an issue with our RTB servers.
Our engineering team is continuing to work on restoring RTB to full performance.
Service to RTB is improving and we are continuing to monitor it.
We are continuing to monitor for any further issues.
RTB service has been stable for the past 2hrs, marking as resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
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.
After restoring service we detected another regression in API servers and are investigating.
API service is back online and we are monitoring
This incident has been resolved.
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.
This incident has been resolved.
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.
Improvements have been deployed and clients should not be experiencing this.
The issue is currently under investigation. Please use Call 1.0
A third party service involved in the reporting are experiencing issues. Working with them on a resolution.
Incident should be resolved. We are monitoring and confirming.
This incident has been resolved.
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.
The incident has been resolved. It is occurring for a limited amount of time.
A 'carrier' which is used by another 'call tracking provider' which isn’t Retreaver or Twilio is currently experiencing an incident.
A fix has been implemented and we are monitoring the results.
Carrier marked as operational
There has been and instance of a report with degraded performance.
The incident has been resolved the benchmark report ran in a satisfactory amount of time
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.
Monitoring the results.
Monitoring the results.
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/)
We see no issues on our side. At the same time AWS reports that services are still impacted.
This incident has been resolved.
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.
We are continuing to investigate this issue.
Call are processing again. Continuing monitoring
We see no issues on Retreaver at the moment despite the fact the that there are 64 services with degraded performance on AWS.
You may occasionally see an error message with “We’re sorry, something went wrong.” We will be deploying a fix shortly.
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.
We detected another spike in errors for a subset of visitors to our website. Our team is investigating.
Website access has now been restored, we will keep monitoring for any further issues
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
RTB log has caught and all the requests are shown
This incident has been resolved.
