Outage in Rivery

River failures - can't compare datetime.datetime to datetime.date

Resolved Minor
May 29, 2025 - Started 8 days ago - Lasted about 6 hours
Official incident page

Need to monitor Rivery outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Rivery, and never miss an outage again.
Start Free Trial

Outage Details

We are currently investigating an issue causing failures in a minor portion of River runs. The error message observed is: "TypeError: can't compare datetime.datetime to datetime.date" Our team is actively working to pinpoint the exact configuration that is leading to these failures. Most River runs continue to operate normally. We will provide further updates as soon as more information becomes available. Thank you for your patience. Data integration (Rivery) suport team
Latest Updates ( sorted recent to last )
RESOLVED 8 days ago - at 05/29/2025 07:47PM

We have deployed a fix for the issue that was causing failures in some Rivers using S3 and Azure Blob data sources.

A limited number of River runs were impacted by the following error:
TypeError: can't compare datetime.datetime to datetime.date

The root cause was identified and a fix was successfully deployed. Since then, no further failures have been observed. System performance has remained stable during the monitoring period.

This incident is now considered fully resolved. Thank you for your patience and understanding.

For any further questions please contact our Support Team.

MONITORING 8 days ago - at 05/29/2025 02:37PM

We have deployed a fix for the issue that was causing failures in some Rivers using S3 and Azure Blob data sources.

Incident start: May 28, 2025, at 16:00 IST (13:00 UTC)

Incident resolved: May 29, 2025, at 17:30 IST (14:30 UTC)

The issue resulted in a limited number of River runs failing with the error:
TypeError: can't compare datetime.datetime to datetime.date

We are currently monitoring the system to ensure full stability. No further failures have been observed since the fix was deployed.

We will post a final update once the incident is fully resolved.

Thank you for your patience.
Data integration (Rivery) suport team

IDENTIFIED 8 days ago - at 05/29/2025 02:00PM

We have identified that the issue is impacting Rivers with S3 and Azure Blob as their data sources. These Rivers may fail with the following error: TypeError: can't compare datetime.datetime to datetime.date

We are working on a fix and will update as progress is made.

Best Regards
Data integration (Rivery) suport team

INVESTIGATING 8 days ago - at 05/29/2025 01:58PM

We are continuing to investigate this issue.

INVESTIGATING 8 days ago - at 05/29/2025 01:38PM

We are currently investigating an issue causing failures in a minor portion of River runs.

The error message observed is: "TypeError: can't compare datetime.datetime to datetime.date"

Our team is actively working to pinpoint the exact configuration that is leading to these failures.
Most River runs continue to operate normally.

We will provide further updates as soon as more information becomes available.

Thank you for your patience.
Data integration (Rivery) suport team

All Third-Party Status Pages in One Dashboard

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 · 4200 services available

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