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.

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 2023 - 13:46 PST
Scheduled - Apigee Runtime Data Infrastructure maintenance for Apigee Edge Public Cloud is planned from 08:00 AM PT Tuesday January 17, 2023. The activity is expected to continue till March 31st, 2023.

The maintenance will be rolled out in phases & regions. This maintenance is not expected to have any impact on Apigee Edge API traffic.

For any questions or clarifications, please contact Apigee Support (https://cloud.google.com/apigee/support/).

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 02, 2022 - 16:45 PDT
Scheduled - On this page, we provide the latest update of the potential impact of the recently announced OpenSSL vulnerabilities(https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/) on Apigee products and services. Investigations are ongoing as this is a developing event. We will continue to assess potential impact as we learn more, and we will update this post with details on any impacted Apigee products and services.

As Apigee components do not explicitly install the OpenSSL package in the base images, Apigee products are not found to be impacted with the OpenSSL vulnerability reported on OpenSSL 3.x.

As of this publication, we have found no evidence of any exploitation activities.

Background:
On November 1, the OpenSSL project team released (https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/) OpenSSL version 3.0.7 to fix two vulnerabilities in OpenSSL 3.0.x. OpenSSL initially suggested (https://mta.openssl.org/pipermail/openssl-announce/2022-October/000238.html) that the pending release would resolve a critical vulnerability. The version 3.0.7 release, however, assigned a high severity to both vulnerabilities. This assessment was based on further technical review and alignment with OpenSSL’s security policies (https://www.openssl.org/policies/general/security-policy.html).

We’ll share more information with customers as it becomes available and update this page with the results of our investigation and any guidance if appropriate.

Please also refer to Google Cloud Security Advisory at https://cloud.google.com/openssl-security-advisory

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, 2021 - 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, 2021 - 09:04 PST
API Services ? Under Maintenance
Management Services UI ? Operational
Management Services API ? Operational
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.
Past Incidents
Feb 4, 2023

No incidents reported today.

Feb 3, 2023

No incidents reported.

Feb 2, 2023

No incidents reported.

Feb 1, 2023
Completed - The scheduled maintenance has been completed.
Feb 1, 10:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 1, 09:00 PST
Scheduled - We have maintenance planned for Apigee Monetization Infrastructure from Wednesday 2023-02-01 9:00 AM PST. The activity is expected to continue until Wednesday 2023-02-01 10:00 AM PST.

During the maintenance window, Apigee Monetization billing and reports will not be available.

If you have any questions or require assistance, please contact Apigee Support (https://cloud.google.com/apigee/support/).

Components affected:
Apigee Monetization billing and reports.

FAQs:
What is changing?
A maintenance activity will be performed on the backend systems supporting monetization.

Are customers required to make any changes?
No.

Will customers be able to access Monetization reports during this period ?
Reporting functionality will NOT be available during this maintenance period.

Jan 27, 15:33 PST
Jan 31, 2023

No incidents reported.

Jan 30, 2023

No incidents reported.

Jan 29, 2023

No incidents reported.

Jan 28, 2023

No incidents reported.

Jan 27, 2023

No incidents reported.

Jan 26, 2023

No incidents reported.

Jan 25, 2023

No incidents reported.

Jan 24, 2023

No incidents reported.

Jan 23, 2023

No incidents reported.

Jan 22, 2023

No incidents reported.

Jan 21, 2023

No incidents reported.