Apigee Release Schedule

Apigee Edge: Tue-Thu 12am to 4am in Singapore, Central European, and US Eastern time zones (learn more)

Read the release notes to learn what is new.

Update - Log4j v1.x:
We are aware of the recent upgrade to CVE-2021-4104 which affects versions of Log4j 1 which are used on Apigee Edge and OPDK. This CVE requires a specific configuration of Log4j 1 which Apigee Edge does not use and which Apigee OPDK does not ship as a default configuration.

User Supplied Log4j 1 Java Callouts
Apigee SaaS (X and Edge):
Customers can upload vulnerable configurations of Log4j 1 in their custom resources, but CVE-2021-4104 is mitigated due to Java Security Manager restrictions.

Apigee OPDK and Hybrid
Users should upgrade all of their custom resources of Log4j to the latest version.
Users can mitigate uploaded vulnerable versions of Log4j 1 in Hybrid and OPDK by enabling a custom java callout security policy:
Hybrid: https://cloud.google.com/apigee/docs/api-platform/develop/adding-custom-java-callout-security-policy
OPDK: https://docs.apigee.com/api-platform/reference/java-permission-reference
Dec 17, 10:40 PST
Monitoring - Updated December 15, 2021 15:22 PST

Google Apigee is actively following the security vulnerability in the open-source Apache “Log4j 2" utility (CVE-2021-44228 and CVE-2021-45046). We encourage you to update to the latest version of Log4j 2. We are currently assessing the potential impact of the vulnerability for Apigee products and services. This is an ongoing event and we will continue to provide updates through this page and our customer communications channels.

Background: The Apache Log4j 2 utility is a commonly used component for logging requests. On December 9, 2021, a vulnerability was reported that could allow a system running Apache Log4j 2 version 2.14.1 or below to be compromised and allow an attacker to execute arbitrary code.

On December 10, 2021, NIST published a critical Common Vulnerabilities and Exposure alert, CVE-2021-44228. More specifically, Java Naming Directory Interface (JNDI) features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from remote servers when message lookup substitution is enabled.

==== Platform ====

Apigee X:
Apigee X does not use Log4j 2.

Apigee Hybrid:
Current supported versions of Hybrid do not use Log4j 2.
Unsupported versions of Hybrid used Log4j 1.x, but it is not included in any of the currently supported versions. Customers on Hybrid 1.4 or lower are unaffected by this CVE but should still upgrade to a supported version.

Apigee Edge:
Apigee Edge’s default configuration contained Log4j 2 but was not vulnerable to Log4j 2 (CVE-2021-44228).

Apigee OPDK:
Apigee OPDK’s default configuration contained Log4j 2 but was not vulnerable to Log4j 2 (CVE-2021-44228).
The service “apigee-machinekey” includes Log4j 2 and does not process any user-provided input. It is not susceptible to the vulnerability CVE-2021-44228.


==== User Supplied Log4j 2 Instances ====


Apigee SaaS (X and Edge):
Customers can upload vulnerable versions of Log4j 2 in their custom resources, but CVE-2021-4228 is mitigated due to Java Security Manager restrictions.

Apigee Hybrid and OPDK:
Users can mitigate uploaded vulnerable versions of Log4j 2 in Hybrid and OPDK by enabling a custom java callout security policy:
Hybrid: https://cloud.google.com/apigee/docs/api-platform/develop/adding-custom-java-callout-security-policy
OPDK:
https://docs.apigee.com/api-platform/reference/java-permission-reference


==== Versions Updates ====

Log4j v1.x:
Apigee Edge and Apigee OPDK contain Log4j 1.x and Log4j 2.x libraries. Log4j 1 is not part of this particular assessment.
All instances of Log4j 1 will be upgraded across all Apigee products in upcoming releases to the latest version of Log4j 2. Upgrades to SaaS services and releases for OPDK are expected in January.

==== More Information ====

Information on this page is based on findings in our ongoing investigations.

Please see these helpful articles published to the Apigee Community:

How to Detect Network Probes on Traversing Your Apigee Proxies-
https://www.googlecloudcommunity.com/gc/Apigee/Detecting-Attempts-to-Exploit-Log4j-CVE-2021-44228-on-Apigee/td-p/178123

How To Mitigate Log4Jv2 Attacks CVE-2021-44228 Traversing Apigee Proxies -
https://www.googlecloudcommunity.com/gc/Apigee/How-To-Block-requests-that-exploit-Log4j-CVE-2021-44228-on/td-p/178138
Dec 14, 09:04 PST
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 21, 06:19 PST
Identified - The issue has been identified and a fix is being implemented.
Dec 21, 06:09 PST
Investigating - We are currently aware of an issue with our Management APIs resulting in "Bad Gateway Error", and are working internally to identify the cause and fix the issue.
Dec 21, 04:31 PST
API Services ? Operational
Management Services UI ? Operational
Management Services API ? Partial Outage
Analytics Services ? Operational
Developer Services ? Operational
Apigee Edge (Developer Edition) ? Operational
API Exchange Operational
Apigee Login and Single Sign-On Operational
Apigee Sense Operational
Edge Private Cloud ? Operational
Edge Private Cloud - API Platform Operational
Edge Private Cloud - Developer Portal Operational
Edge Private Cloud - API BaaS Operational
Edge Private Cloud - Developer Services ? Operational
Developer Portal Operational
Integrated Operational
Drupal-based (alternative) Operational
Community Operational
90 days ago
100.0 % uptime
Today
Apigee Community ? Operational
90 days ago
100.0 % uptime
Today
Monitoring Operational
90 days ago
100.0 % uptime
Today
API Monitoring Operational
90 days ago
100.0 % uptime
Today
Adapter for Envoy ? Operational
90 days ago
100.0 % uptime
Today
Apigee Monetization Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
We have an Apigee Runtime Data Infrastructure maintenance planned from Thursday Jan 20, 2022. The activity is expected to continue till Feb 27, 2022.

The rollout is planned in phases based on regions. We will update this status notice weekly with the regions being actively worked on. This release is not expected to cause any downtime to Apigee Edge.

If you have any questions or require assistance, please contact Apigee Support (https://cloud.google.com/apigee/support/).
Posted on Jan 18, 20:14 PST
Past Incidents
Jan 19, 2022

No incidents reported today.

Jan 18, 2022

No incidents reported.

Jan 17, 2022

No incidents reported.

Jan 16, 2022

No incidents reported.

Jan 15, 2022

No incidents reported.

Jan 14, 2022
Completed - The scheduled maintenance has been completed.
Jan 14, 09:29 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 12:20 PST
Scheduled - Apigee released a patch for Apigee Edge for Private cloud for versions 4.50.00 and 4.51.00 to address the Apache Log4j vulnerabilities.

Please refer to the release notes for details:
4.50.00: https://docs.apigee.com/release/notes/4500013-private-cloud-relnotes
4.51.00: https://docs.apigee.com/release/notes/4510003-private-cloud-relnotes


Please also refer to the Apigee update: https://status.apigee.com/incidents/v1x2xgy4mnfj
Jan 13, 12:18 PST
Jan 13, 2022
Completed - The scheduled maintenance has been completed.
Jan 13, 12:18 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 12, 14:50 PST
Scheduled - Apigee will release a patch on Apigee Edge for Private Cloud 4.50.00 and 4.51.00 versions on Thursday Jan 13, 2022 from 09:30 AM to 11:30 PM PT. Please refrain from downloading binaries from software.apigee.com during the release window.
Jan 12, 14:44 PST
Jan 12, 2022
Jan 11, 2022

No incidents reported.

Jan 10, 2022

No incidents reported.

Jan 9, 2022

No incidents reported.

Jan 8, 2022

No incidents reported.

Jan 7, 2022

No incidents reported.

Jan 6, 2022

No incidents reported.

Jan 5, 2022
Completed - The scheduled maintenance has been completed.
Jan 5, 07:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 1, 08:00 PDT
Scheduled - To minimize the risk of service outage during the Holiday 2021 season, Apigee will enforce a “release moratorium” from November 01, 2021 through January 03, 2022.

This moratorium covers critical components including API Services, Management Services UI, Management Services API, Analytics Services, Developer Services, Apigee Login and Single Sign-On, Apigee Sense and Apigee Monetization.

During this period, we will only make emergency changes to the system. In the event we need to make any such change, due to security or other concerns, we will notify you prior to making them.
Oct 28, 10:25 PDT