Rainforest API Outage History

Rainforest API is up right now

Rainforest API had 3 outages in the last 2 years totaling 54h 47m of downtime — averaging 0.1 incidents per month.

There were 3 Rainforest API outages since July 31, 2025 totaling 54h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://rainforestapi.statuspage.io

Notice November 18, 2025

Update on Upstream Provider Issues

Detected by Pingoru
Nov 18, 2025, 02:54 PM UTC
Resolved
Nov 18, 2025, 09:05 PM UTC
Duration
6h 11m
Affected: DashboardWebsite
Timeline · 2 updates
  1. monitoring Nov 18, 2025, 02:54 PM UTC

    Cloudflare has identified an issue which is presently impacting their security and domain proxy solutions, and they are currently rolling out a fix. We are observing improvements in connectivity and error rates are returning to normal levels. Traject Data users are seeing intermittent access issues impacting the API playground, Dashboards and Documentation. We will continue to monitor the situation until the upstream incident is fully resolved to ensure stability for all users.

  2. resolved Nov 18, 2025, 09:05 PM UTC

    CloudFlare have stabilized their platform, and have marked the previous issue as resolved.

Read the full incident report →

Minor July 31, 2025

Website Access Issues (Regional Impact)

Detected by Pingoru
Jul 31, 2025, 02:41 PM UTC
Resolved
Aug 01, 2025, 01:20 PM UTC
Duration
22h 38m
Affected: DashboardWebsite
Timeline · 3 updates
  1. investigating Jul 31, 2025, 02:41 PM UTC

    Heads Up – We’re seeing intermittent issues accessing our website from certain international regions. The underlying cause appears to be tied to broader disruptions with upstream network providers (including Cloudflare). Our core services are unaffected, and the issue is limited to web access. We're actively monitoring and will update as more information becomes available.

  2. investigating Jul 31, 2025, 06:31 PM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 01, 2025, 01:20 PM UTC

    This incident has been resolved.

Read the full incident report →