Monitoring - Poodle is a vulnerability in the SSL 3.0 protocol used in SSL encrypted communications. Officially, its reported as CVE-2014-3566. Detailed information on the attack can be found at any of the following sites:
Apigee allows the use of SSL 3.0 in the configuration of secure connections into the Apigee Edge platform. At the time of this announcement, Apigee is not aware of any active exploitation of this flaw. However, the protocol (SSL 3.0) is still vulnerable and its use should be deprecated as soon as possible for all Apigee customers.
Apigee recommends that all customers stop the use of SSL v3.0 in their configurations.
For cloud customers, this can be accomplished by opening a support ticket with Apigee Support and requesting your SSL configuration be updated to not allow SSL v3.0.
For on-premises customers, the change would need to be made where your SSL termination is done - often inside of a load balancer. The process to complete this will depend on the systems used for SSL and assistance should be obtained from your load balancer or SSL vendor.
Oct 15, 10:40 PDT
The issue reported earlier against the GeoMap is a known issue and requires an update that is currently undergoing testing. We will be releasing this update in the next two weeks. There is no data loss but until the release the GeoMap will continue to present an inaccurate view of traffic data
Oct 17, 17:42 PDT
We are currently investigating reports that the GeoMap is not displaying traffic details consistently. There is no impact to API run time traffic and all other Analytics reports are working as expected.
Oct 17, 13:51 PDT
The API Proxy deployment issue has been resolved; You can now deploy a different API Proxy version without manually un-deploying the existing version.
Oct 13, 12:59 PDT
We are doing an Emergency release to edge in order to fix the deployment issue. API runtime traffic will not be affected.
APAC and EU - Friday Oct 10th, 2014 5 pm - 9 pm PDT
Americas - Saturday Oct 11th, 2014 9 am - 5 pm PDT
- Sunday (Reserved)
Oct 10, 16:28 PDT
Please be aware that we are currently investigating an issue with deployment of API proxies.
To ensure a new version of a proxy is deployed correctly until this issue is resolved, please do the following:
1. Un-deploy the old version
2. Deploy the new version
Please note that this will cause 1-2 minutes of downtime for your APIs while deploying and therefore must be used with caution during peak hours.
We are working to fix this issue ASAP and will keep everyone notified once resolved.
Oct 10, 09:20 PDT