PrismaCloud: APP3: Stale data in asset inventory — Palo Alto Networks Cloud Services Incident Timeline & Status

Try DevHelm Uptime

Palo Alto Networks Cloud Services Status

PrismaCloud: APP3: Stale data in asset inventory

Started

Sep 29, 6:32 AM UTC

Resolved

Oct 1, 5:25 AM UTC

Duration

1 day

Resolvedminor impactVendor link

Affected:Americas - US - app3.prismacloud.io

Update timeline

ResolvedOct 1, 5:25 AM

This incident has been resolved.

IdentifiedOct 1, 2:37 AM

We are continuing to work on a fix for this issue.

IdentifiedOct 1, 1:40 AM

We are continuing to work on a fix for this issue.

IdentifiedOct 1, 12:14 AM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 10:41 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 9:29 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 8:11 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 6:42 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 5:33 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 4:16 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 2:00 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 9:44 AM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 7:50 AM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 2:01 AM

We are continuing to work on a fix for this issue.

IdentifiedSep 30, 12:59 AM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 11:55 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 10:35 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 9:43 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 8:47 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 7:40 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 6:28 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 5:29 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 3:35 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 1:55 PM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 9:36 AM

We are continuing to work on a fix for this issue.

IdentifiedSep 29, 6:32 AM

The issue has been identified and a fix is being implemented.