OpenWater Outage History

OpenWater is up right now

OpenWater had 2 outages in the last 2 years totaling 17h 0m of downtime, averaging 0.1 incidents per month.

There were 2 OpenWater outages since April 28, 2025 totaling 17h 0m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: openwater.statuspage.io

Major September 2, 2026

Payments Outage

Detected by Pingoru
Sep 02, 2026, 08:00 PM UTC
Resolved
Sep 03, 2026, 01:00 PM UTC
Duration
17h
Timeline · 1 update
  1. resolved Sep 03, 2026, 02:08 PM UTC

    From September 2 approximately 4:00 PM until September 3 approximately 10:00 AM eastern time, all payment transactions failed to process. Users checking out of their cart received an error message alerting them their payment was not successful and during this time no actual charges were made. Users should complete their payments and it is recommended to extend any deadlines from yesterday to today. The outage occurred due to human error, a change in our network configuration resulted in our payments module being unreachable. The change went by unnoticed until we observed an uptick in payment failures this morning as the work day started.

Read the full incident report →

Minor April 28, 2025

Github Workflows Security Update - External Keys Must Be Rotated

Detected by Pingoru
Apr 28, 2025, 01:00 PM UTC
Resolved
Apr 28, 2025, 01:00 PM UTC
Duration
–
Timeline · 2 updates
  1. resolved May 09, 2025, 03:30 PM UTC

    On Friday, April 25th one of our developers clicked a phishing email which gave a bot access to certain integrations related code. Our developers do not have access to customer data and steps were taken immediately to close out access to potential unauthorized users. The developers do however have access to certain API keys used to integrate OpenWater with external CRM/AMS products. As per proper security protocol, we are asking all impacted customers to rotate their API keys immediately. Our integrations support team is reaching out this week. While our investigation is ongoing, at this time, we have found no evidence of code modifications, unauthorized access to production systems, exposure of customer data, or access to personal information. We are working with a third party, S-RM (https://www.s-rminform.com/digital-forensics-services) to validate our findings and we will update this article upon the conclusion.

  2. postmortem May 09, 2025, 03:32 PM UTC

    S-RM has validated our findings by checking access logs from March 1 to May 5 for unauthorized or suspicious behavior. We remain confident in our assessment that API keys were not used by an unauthorized party. This date range was chosen to provide significant data from the past to confirm and validate expected behavior patterns and confirm there was no significant deviation. Further we have confirmed most customer systems are protected by IP address restrictions in addition to API Keys and that there is no further action for customers once the key rotation is complete. In terms of after action we have determined our own use of CloudFlare enterprise which includes automatic bot detection and prevention, along with other defense in depth security strategy reduced the overall risk of this incident. In terms of areas of improvement, OpenWater has also since implemented additional anti-phishing measures and additional security controls around developer code repositories.

Read the full incident report →