Outage in Rainforest API

Parsing Issue

Resolved Minor
December 19, 2023 - Started about 2 years ago - Lasted about 14 hours
Official incident page

Incident Report

Reviews result parsing is currently operating in a degraded state where the 'reviews.attributes' 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.

Need to monitor Rainforest API outages?

One place to monitor all your cloud vendors.
Get instant alerts when an outage is detected.

Latest Updates ( sorted recent to last )
RESOLVED about 2 years ago - at 12/20/2023 02:30PM

This incident has been resolved.

IDENTIFIED about 2 years ago - at 12/20/2023 12:27AM

Reviews result parsing is currently operating in a degraded state where the 'reviews.attributes' 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.

Latest Rainforest API outages

Update on Upstream Provider Issues - about 2 months ago
Rainforest Outage - over 1 year ago
Collections Running Slowly - over 1 year ago

The Status Page Aggregator with Early Outage Detection

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 5350 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook