As of 9am Eastern, Engaging Networks can confirm that The Senate Communicating with Congress API has unblocked US traffic and messages are able to be delivered.
As of 10am Eastern, Engaging Networks has implemented a temporary configuration change to enable non-US clients to communicate with the Congress API for Senate Communications. We have confirmed that CA clients are now sending messages to the US Senate.
Posted Oct 24, 2026 - 16:22 UTC
Update
Data Centers: CA, US, and US2 Databases: US Senate (US House is not affected)
The Senate Communicating with Congress API is now blocking all traffic due to cybersecurity implementation. This status has been updated to expand the impacted data centers, but still only impacts the Senate.
This is not limited to Engaging Networks, but impacts any applications utilizing the Senate Communicating with Congress environments.
Posted Oct 23, 2026 - 19:53 UTC
Identified
Data Center: CA Only Databases: US Senate (US House is not affected)
The Senate Communicating with Congress API is blocking all traffic from outside the US due to the recently-disclosed PHP vulnerabilities. As a result, no messages can be delivered to the US Senate from client accounts in the CA datacenter. CWC have indicated this will remain blocked until all Senate systems are remediated. Engaging Networks is pressing for a specific timeline and will continue to update this page.