Rainforest API incident

Parsing

Minor Resolved View vendor source →

Rainforest API experienced a minor incident on February 8, 2023 affecting Product Requests, lasting 2h 55m. The incident has been resolved; the full update timeline is below.

Started
Feb 08, 2023, 01:25 PM UTC
Resolved
Feb 08, 2023, 04:21 PM UTC
Duration
2h 55m
Detected by Pingoru
Feb 08, 2023, 01:25 PM UTC

Affected components

Product Requests

Update timeline

  1. identified Feb 08, 2023, 01:25 PM UTC

    Product result parsing is currently operating in a degraded state where the 'product.variants' field is not being successfully parsed on some page layouts. Rainforest API apologise for the inconvenience caused during this incident. Our team, based in the UK and online between 9am and 5:30pm GMT Monday to Friday, are working on a resolution as quickly as possible. As Rainforest API sources data through public web-scraping parsing issues such as this can occur (albeit rarely) when page layouts change or when the underlying website is down for maintenance. You may use the 'skip_on_incident' request parameter to instruct Rainforest API to not serve you requests when a parsing incident such as this is detected. For example, requests made with 'skip_on_incident=all' or 'skip_on_incident=major_only' will refuse requests when any, or just a'major', incident occurs for the affected API component. This can be desirable if your system is making unsupervised requests to the API that you would like to gracefully fail in the event of an incident. In addition any Collections started during this incident will be queued and automatically started once the incident is resolved. We will post further updates, including an estimation on resolution time, when available, thank you for your patience.

  2. identified Feb 08, 2023, 03:49 PM UTC

    Product result parsing is currently experiencing a critical error with no product node being parsed.

  3. resolved Feb 08, 2023, 04:21 PM UTC

    This incident has been resolved.