Partial Service Disruption
July 30, 2026 11:24AM CDT
July 30, 2026 4:24PM UTC
IDENTIFIED
Following the release of BLOX Subscription 1.70.1, we have received reports that subscription-related webhooks are not being sent.
Our engineering team has identified the issue and is actively working on an out-of-band release to restore webhook delivery.
We will provide additional updates as they become available.July 30, 2026 11:27AM CDT
July 30, 2026 4:27PM UTC
IDENTIFIED
The previously published advisory incorrectly stated that the issue affected BLOX Subscription 1.70.1. The affected release is BLOX Subscription 1.70.0. This correction does not change the nature of the issue or our remediation efforts.July 30, 2026 1:01PM CDT
July 30, 2026 6:01PM UTC
MONITORING
Our engineering team has completed development and validation of the fix for the subscription-related webhook delivery issue affecting BLOX Subscription 1.70.0.
The out-of-band release is scheduled to be deployed today at 1:00 PM Central Time. Once deployment is complete, we will provide a final update confirming that the issue has been resolved.July 31, 2026 11:09AM CDT
July 31, 2026 4:09PM UTC
MONITORING
To ensure no subscription-related webhook events are missed as a result of the issue affecting BLOX Subscription 1.70.0, we will replay all webhooks that were not delivered during the impacted period.
Replay Schedule:
- Today at 4:00 PM Central Time
Customers that rely on subscription-related webhooks may receive delayed webhook events as they are replayed.
If you do not want the missed webhooks to be replayed, please contact our Support team before 4:00 PM Central Time so we can exclude your environment from the replay process.
We apologize for the inconvenience and appreciate your patience while we complete the recovery process.July 31, 2026 4:13PM CDT
July 31, 2026 9:13PM UTC
RESOLVED
RESOLVED
The replay of all subscription-related webhooks that were not delivered during the affected period has been successfully completed.
All missed webhook events have now been processed, and normal webhook delivery has resumed.
If you believe your environment did not receive the expected webhook events or you experience any related issues, please contact our Support team for assistance.
We apologize for the inconvenience and appreciate your patience while we worked to resolve this issue.