Starting at 8 PM ET tomorrow evening (11/7) webhooks will begin to be sent out via the following IPs for each environment:

Production: 52.203.95.168 (new), 52.4.158.130,3.216.152.234, 54.243.233.84, 50.19.211.21

Sandbox/staging: 52.200.234.230 (new), 18.206.70.225,44.195.8.253, 44.198.216.125

Add the new IPs to any IP allowlists your team is using to prevent possible interruptions in the receipt of webhook events. If you don't use an IP allowlist, no action is required.

See additional details on the IP change in our October 2026 release notes and the full list of IPs used by our system in our API docs. Note that we recommend verifying webhook signatures in place of IP whitelisting when possible as a more reliable method of authenticating events.

Maintenance has completed

DoseSpot’s fix is in place and performance is back to normal. If you’re still experiencing issues using the integration try refreshing your browser, clearing your browser cache or logging out then back in.

Site performance is restored.

This is resolved. Refresh the page and you’ll be able to log in to staging without error.

Faxing services are back to normal. Errors are no longer occurring when sending or viewing faxes.

All inbound faxes sent during the incident were still received and are accessible.

Fix is in place and we're no longer seeing errors when attempting to send or view faxes.

Zoom has resolved the degradation on their end and meeting links can be accessed again without any issues.

In the Staging Sandbox environment from about 6 AM to 12:37 PM ET, certain API requests or UI actions were intermittently affected by 500 or Internal Server Errors.

Production was not affected.

Fix is in place and we're no longer seeing the same errors in our logs. We're marking the incident as resolved.

Maintenance has completed

We observed elevated response times on API requests and when accessing certain pages of the platform from around 11 AM to 12:06 PM ET, as well as around 1 PM to 1:28 PM ET.

Our Engineering team has applied several optimizations to the backend to address the cause of the increased response times. Load times have remained stable after these updates, we're marking the incident as resolved.

We have not seen reports of customer issues, despite the blocks remaining in place, so are marking this as resolved. We continue to advise using an MFA app (vs SMS based authentication) especially for non-US phone numbers.

Early this morning, our captcha provider experienced an issue which led to a large increase of "Captcha Validation Failed" errors when attempting to sign in. We temporarily disabled the check at 7:35 am eastern, and our captcha provider confirmed the issue and resolved it at 8:10 a.m.

We saw much higher than normal response times between ~2:46-3:00 p.m eastern. This has since been resolved and our team continues to investigate the root cause.

Fix is in place and we're not seeing any new occurrences of the "session expired" error when signing into Staging. We're marking this as resolved.

Maintenance has completed

Prior to deploying, we identified a potential issue with this evening's planned update. We are postponing this work until we have a resolution.

Maintenance has completed

This issue should now be resolved and API key operations should be working normally.

Maintenance has completed

Response times have remained normal since our last update and the changes we performed to resolve the issue. We're closing out the incident.

Thank you for your patience. All queues are back to normal. The issue appears to have been related to underlying hardware in one of our AWS cluster and was resolved via cycling out all the hardware.

In the process of trying to manually keep queue volumes low and verify different potential solutions, some invalid webhooks were sent out (e.g webhooks for data that does not exist) and which are not able to be actioned on. These did not replace any valid webhooks, and all valid webhooks have been sent.

This issue has been resolved. Clients who received the error should refresh their page and attempt to join again. They will now be able to join video calls without issue.