Outage in Palo Alto Networks

Prisma Access (Panorama Managed) Minimum 3.0 Plugin Extended to October 31, 2022 (Not applicable for FedRamp Moderate)

Resolved Minor
October 17, 2022 - Started about 2 years ago - Lasted 3 months
Official incident page

Need to monitor Palo Alto Networks outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Palo Alto Networks, and never miss an outage again.
Start Free Trial

Outage Details

With reference to the following notification, we are extending the time period to upgrade your Cloud Services plugin to 3.0 version by 2 weeks. The new effective date will be October 31st 2022 to be on the minimum 3.0 plugin version to successfully commit to your Prisma Access instances. In order for your Prisma Access deployment to have the most up-to-date functionality and features, and to maintain backward compatibility with the current service infrastructure, a minimum Cloud Services plugin version of 3.0 will be required for Panorama Managed Prisma Access deployments. This requirement takes effect on October 17, 2022. Starting October 17, 2022, a minimum Cloud Services version of 3.0 plugin will be required to successfully commit to your Prisma Access instances. Commits from earlier versions of the plugin will not be successful. If an upgrade of the plugin is required for your Prisma Access deployment, be sure to leverage the plugin upgrade path listed in the 3.0 Release Notes, the Changes to Default Behavior for 3.0, and the supported Panorama versions for each Cloud Services plugin version. While a minimum version of 3.0 will be required, Palo Alto Networks strongly recommends that you upgrade to the latest plugin as soon as it is available to download. If your Prisma Access dataplane version is 10.0.8 or later, only a plugin upgrade is required. To check your dataplane version, select Panorama > Cloud Services > Configuration > Service Setup and check the Dataplane PAN-OS Version. If your dataplane requires an upgrade, reach out to your Palo Alto Networks account representative and submit a request.
Components affected
Palo Alto Networks Americas-Mexico Central Palo Alto Networks APAC-New Zealand Palo Alto Networks EMEA-Germany Central Palo Alto Networks EMEA-Russia Central Palo Alto Networks EMEA-Portugal Palo Alto Networks EMEA-Lithuania Palo Alto Networks EMEA-Saudi Arabia Palo Alto Networks EMEA-South Africa West Palo Alto Networks EMEA-Germany Central (Location on-boarded prior to version 1.4) Palo Alto Networks EMEA-Spain Central Palo Alto Networks Americas-US East Palo Alto Networks APAC-Indonesia Palo Alto Networks Americas-Chile Palo Alto Networks EMEA-Slovakia Palo Alto Networks EMEA-Kenya Palo Alto Networks Americas-US Southeast Palo Alto Networks EMEA-Egypt Palo Alto Networks APAC-South Korea (Location on-boarded prior to version 1.4) Palo Alto Networks APAC-Australia Southeast (Location on-boarded prior to version 1.4) Palo Alto Networks APAC-Taiwan Palo Alto Networks EMEA-Netherlands Central Palo Alto Networks Americas-US Central (Location on-boarded prior to version 1.4) Palo Alto Networks APAC-Bangladesh Palo Alto Networks APAC-Malaysia Palo Alto Networks Americas-US Northwest (Location on-boarded prior to version 1.4) Palo Alto Networks APAC-Vietnam Palo Alto Networks EMEA-Turkey Palo Alto Networks APAC-India West Palo Alto Networks APAC-Myanmar Palo Alto Networks APAC-South Korea Palo Alto Networks APAC-Philippines Palo Alto Networks APAC-Thailand Palo Alto Networks EMEA-Sweden Palo Alto Networks EMEA-Russia Northwest Palo Alto Networks EMEA-France South Palo Alto Networks EMEA-Moldova Palo Alto Networks EMEA-Monaco Palo Alto Networks Americas-Brazil South (Location on-boarded prior to version 1.4) Palo Alto Networks EMEA-Switzerland Palo Alto Networks EMEA-Denmark Palo Alto Networks Americas-Colombia Palo Alto Networks APAC-Cambodia Palo Alto Networks Americas-Brazil East Palo Alto Networks Americas-Mexico West Palo Alto Networks Americas-Venezuela Palo Alto Networks Americas-Canada East (Location on-boarded prior to version 1.4) Palo Alto Networks EMEA-Croatia Palo Alto Networks Americas-US West (Location on-boarded prior to version 1.4) Palo Alto Networks APAC-Australia East Palo Alto Networks EMEA-Israel Palo Alto Networks EMEA-Ireland (Location on-boarded prior to version 1.4) Palo Alto Networks EMEA-Czech Republic Palo Alto Networks Americas-US West Palo Alto Networks EMEA-Kuwait Palo Alto Networks EMEA-Slovenia Palo Alto Networks APAC-India West (Location on-boarded prior to version 1.4) Palo Alto Networks EMEA-Spain East Palo Alto Networks Americas-US South Palo Alto Networks Americas-Costa Rica Palo Alto Networks EMEA-Luxembourg Palo Alto Networks EMEA-UK (Location on-boarded prior to version 1.4) Palo Alto Networks Americas-US Southwest Palo Alto Networks Americas-Canada West Palo Alto Networks APAC-Australia Southeast Palo Alto Networks EMEA-Ireland Palo Alto Networks Americas-Peru Palo Alto Networks APAC-Pakistan South Palo Alto Networks EMEA-France North (Location on-boarded prior to version 1.4) Palo Alto Networks EMEA-Germany North Palo Alto Networks Americas-Canada Central Palo Alto Networks EMEA-Bulgaria Palo Alto Networks APAC-Hong Kong Palo Alto Networks Americas-Panama Palo Alto Networks EMEA-Norway Palo Alto Networks EMEA-Italy Palo Alto Networks Americas-Bolivia Palo Alto Networks Americas-Brazil Central Palo Alto Networks EMEA-France North Palo Alto Networks EMEA-Ukraine Palo Alto Networks EMEA-Austria Palo Alto Networks EMEA-Uzbekistan Palo Alto Networks Americas-Canada East Palo Alto Networks EMEA-Jordan Palo Alto Networks EMEA-United Arab Emirates Palo Alto Networks EMEA-Netherlands South Palo Alto Networks Americas-Ecuador Palo Alto Networks EMEA-Poland Palo Alto Networks Americas-Brazil South Palo Alto Networks Americas-US East (Location on-boarded prior to version 1.4) Palo Alto Networks EMEA-Greece Palo Alto Networks EMEA-Hungary Palo Alto Networks APAC-Japan South Palo Alto Networks APAC-Papua New Guinea Palo Alto Networks EMEA-UK Palo Alto Networks EMEA-Romania Palo Alto Networks APAC-Singapore Palo Alto Networks Americas-Paraguay Palo Alto Networks APAC-Pakistan West Palo Alto Networks APAC-Australia South Palo Alto Networks EMEA-Nigeria Palo Alto Networks EMEA-Germany South Palo Alto Networks EMEA-Belarus Palo Alto Networks APAC-Singapore (Location on-boarded prior to version 1.4) Palo Alto Networks APAC-India South Palo Alto Networks APAC-India North Palo Alto Networks EMEA-Finland Palo Alto Networks EMEA-South Africa Central Palo Alto Networks Americas-Argentina Palo Alto Networks EMEA-Belgium Palo Alto Networks Americas-US Northeast Palo Alto Networks APAC-Japan Central Palo Alto Networks Americas-US Northwest Palo Alto Networks EMEA-Liechtenstein Palo Alto Networks Americas-US Central Palo Alto Networks APAC-Japan Central (Location on-boarded prior to version 1.4) Palo Alto Networks EMEA-Andorra
Latest Updates ( sorted recent to last )
RESOLVED almost 2 years ago - at 01/12/2023 09:53PM

This incident has been resolved.

MONITORING about 2 years ago - at 10/17/2022 11:30PM

With reference to the following notification, we are extending the time period to upgrade your Cloud Services plugin to 3.0 version by 2 weeks. The new effective date will be October 31st 2022 to be on the minimum 3.0 plugin version to successfully commit to your Prisma Access instances.
In order for your Prisma Access deployment to have the most up-to-date functionality and features, and to maintain backward compatibility with the current service infrastructure, a minimum Cloud Services plugin version of 3.0 will be required for Panorama Managed Prisma Access deployments. This requirement takes effect on October 17, 2022.

Starting October 17, 2022, a minimum Cloud Services version of 3.0 plugin will be required to successfully commit to your Prisma Access instances. Commits from earlier versions of the plugin will not be successful.

If an upgrade of the plugin is required for your Prisma Access deployment, be sure to leverage the plugin upgrade path listed in the 3.0 Release Notes, the Changes to Default Behavior for 3.0, and the supported Panorama versions for each Cloud Services plugin version.

While a minimum version of 3.0 will be required, Palo Alto Networks strongly recommends that you upgrade to the latest plugin as soon as it is available to download. If your Prisma Access dataplane version is 10.0.8 or later, only a plugin upgrade is required. To check your dataplane version, select Panorama > Cloud Services > Configuration > Service Setup and check the Dataplane PAN-OS Version. If your dataplane requires an upgrade, reach out to your Palo Alto Networks account representative and submit a request.

Keeping track of cloud vendor outages shouldn't be hard

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 3257 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook

Setup in 5 minutes or less

How much time you'll save your team, by having the outages information close to them?

14-day free trial · No credit card required · Cancel anytime