Rainforest API incident
Delivery-location setting bug on Amazon affecting performance
Rainforest API experienced a notice incident on November 5, 2020, lasting 17h 21m. The incident has been resolved; the full update timeline is below.
Update timeline
- identified Nov 05, 2020, 12:38 PM UTC
Processing delays are present due to changes in the method of location-setting in the API. Our team are investigating workarounds. At this time Collection processing is paused and will resume automatically when the issue is resolved.
- identified Nov 05, 2020, 04:35 PM UTC
The underlying bug causing the slow response is present on the Amazon site(s) and relates to setting the location of the request. We continue to monitor the situation and will update the status when more information is available. The API will continue to respond and Collections are being processed, albeit at a considerably slower rate.
- monitoring Nov 05, 2020, 05:55 PM UTC
We continue to monitor the situation and are seeing increased success rates as Amazon look to be resolving the issue. As soon as Amazon returns to normal then API performance will be restored. Some domains will function faster than others, however the issue appears sporadic in nature and has affected different Amazon domains to a greater and lessor extent throughout the day. Collections are re-enabled and the backlog is cleared. Collections can be started but thruput will be lower than normal due to the underlying Amazon issue. Our team continue to monitor and will update status accordingly.
- monitoring Nov 05, 2020, 08:50 PM UTC
Performance has returned to normal levels across real-time and Collection requests. Our team continue to monitor as, because this issue was caused by an issue on the Amazon site itself, it is possible it will recur. We will update the status page if the situation changes.
- resolved Nov 06, 2020, 06:00 AM UTC
The bug on the Amazon site that caused this issue now appears to be resolved (by Amazon). API performance is normal at this time.