Time: March 22, 2022, 1:04 a.m.

Status: Resolved

Update: Our integrations team has resolved the incident and services have returned to their normal operation. Backlog of updates have successfully been processed, and live share notification processing is back to normal operating levels. <b>What's impacted?</b> • Backlog of Incident Updates (Comments, Resolves, etc) • This should not delay any current/live share notification processing <b>What’s not impacted?</b> • Incident Sharing We apologize for any inconvenience that this may have caused. Should you continue to experience any issues, please reach out to us via our in-app chat or at [email protected].

Time: March 21, 2022, 11:46 p.m.

Status: Monitoring

Update: Our integrations team is continuing to process backlog of updates. We will continue to monitor for any change in operational capacity. <b>What's impacted?</b> • Backlog of Incident Updates (Comments, Resolves, etc) • This should not delay any current/live share notification processing <b>What’s not impacted?</b> • Incident Sharing We apologize for any inconvenience that this may be causing.

Time: March 21, 2022, 10:35 p.m.

Status: Monitoring

Update: Our integrations team is continuing to process backlog of updates. <b>What's impacted?</b> • Backlog of Incident Updates (Comments, Resolves, etc) • This should not delay any current/live share notification processing <b>What’s not impacted?</b> • Incident Sharing We apologize for any inconvenience that this may be causing.

Time: March 21, 2022, 9:29 p.m.

Status: Monitoring

Update: Our team has implemented a fix for the issue. Backlog of updates are still being processed gradually. We will continue to monitor for any change in operational capacity. <b>What's impacted?</b> • Backlog of Incident Updates (Comments, Resolves, etc) • New shares might experience some delays processing updates <b>What’s not impacted?</b> • Incident Sharing Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.

Time: March 21, 2022, 8:30 p.m.

Status: Identified

Update: Our integrations team continues to work on processing backlog of updates that failed to process. <b>What's impacted?</b> • Backlog of Incident Updates (Comments, Resolves, etc) • New shares might experience some delays processing updates <b>What’s not impacted?</b> • Incident Sharing We apologize for any inconvenience that this may be causing.

Time: March 21, 2022, 3:41 p.m.

Status: Identified

Update: Our team has identified the root cause and deployed a fix. All updates (comments, resolves) that were not processed are being reprocessed. <b>What's impacted?</b> • Incident Updates (Comments, Resolves, etc) <b>What’s not impacted?</b> • Incident Sharing Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.

Time: March 21, 2022, 3:15 p.m.

Status: Investigating

Update: Some users may be experiencing issues with our OOTB ServiceNow and Jira integrations. Our teams are engaged and investigating. <b>What's impacted?</b> • Incident Updates (Comments, Resolves, etc) <b>What’s not impacted?</b> • Incident Sharing We are working to mitigate impacts to our customers as quickly as possible. Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.

Time: March 21, 2022, 1 a.m.

Status: Resolved

Update: Our team has resolved the incident and services have returned to their normal operation. Incident Tags, including calculations against Incidents are be functioning again. <b>What was impacted?</b> Incident Tags - Users may have been unable to load Incident Tag configurations, and Incident Tags may have been calculated against Incidents <b>What was not impacted?</b> All other areas of the pipeline, including alert ingest, processing, console updates, and sharing were operational throughout this incident. We apologize for any inconvenience that this may have caused. Should you continue to experience any issues, please reach out to us via our in-app chat or at [email protected].

Time: March 21, 2022, 12:26 a.m.

Status: Monitoring

Update: The team has reverted a recent change done to the service. Incident Tags, including calculations against Incidents should be functioning again. We will continue to monitor for any change in operational capacity. <b>What's impacted?</b> Incident Tags - Users may not be able to load Incident Tag configurations, and Incident Tags may not be calculated against Incidents <b>What’s not impacted?</b> All other areas of the pipeline, including alert ingest, processing, console updates, and sharing remain operational.

Time: March 21, 2022, 12:09 a.m.

Status: Investigating

Update: Some users may be experiencing issues with Incident Tags. Our teams are engaged and investigating. <b>What's impacted?</b> Incident Tags - Users may not be able to load Incident Tag configurations, and Incident Tags may not be calculated against Incidents <b>What’s not impacted?</b> All other areas of the pipeline, including alert ingest, processing, console updates, and sharing remain operational. We are working to mitigate impacts to our customers as quickly as possible. Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.

Time: March 14, 2022, 3:05 p.m.

Status: Resolved

Update: Our team has resolved the incident and services have returned to their normal operation. We identified the rootcause to be related to the maintenance performed to our Outbound service and rolled back. Another maintenance window will be scheduled in the near future to complete the deployment. <b>Start time:</b> 12:30 UTC <b>End time:</b> 14:28 UTC <b>What's impacted?</b> • Incidents under maintenance <b>What’s not impacted?</b> • Login • Incident Feed • Incident Feed Search • Automatic Incident Triage • Root Cause Changes • Administrator Screens • Incident Actions • Incident Activity Feed • Unified Search • Analytics • Integration Diagnostics / Troubleshooting We apologize for any inconvenience that this may have caused. Should you continue to experience any issues, please reach out to us via our in-app chat or at [email protected].

Time: March 14, 2022, 2:34 p.m.

Status: Monitoring

Update: Our team has implemented a fix for the issue. We will continue to monitor for any change in operational capacity. <b>What's impacted?</b> • Incidents under maintenance <b>What’s not impacted?</b> • Login • Incident Feed • Incident Feed Search • Automatic Incident Triage • Root Cause Changes • Administrator Screens • Incident Actions • Incident Activity Feed • Unified Search • Analytics • Integration Diagnostics / Troubleshooting

Time: March 14, 2022, 2:29 p.m.

Status: Identified

Update: Some users may be experiencing issues with incidents under maintenance being Autoshared. Our teams are engaged and working to resolve the issue. <b>What's impacted?</b> • Incidents under maintenance <b>What’s not impacted?</b> • Login • Incident Feed • Incident Feed Search • Automatic Incident Triage • Root Cause Changes • Administrator Screens • Incident Actions • Incident Activity Feed • Unified Search • Analytics • Integration Diagnostics / Troubleshooting We are working to mitigate impact to our customers as quickly as possible. Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing

Time: March 3, 2022, 11:09 p.m.

Status: Resolved

Update: Our team has resolved the issue and shares to ServiceNow have returned to their normal operation. <b>Start time:</b> 21:15 UTC <b>End time:</b> 22:15 UTC <b>What was impacted?</b> • Incident Sharing We apologize for any inconvenience that this may have caused. Should you continue to experience any issues, please reach out to us via our in-app chat or at [email protected].

Time: March 3, 2022, 10:23 p.m.

Status: Monitoring

Update: Our team has mitigated the issues and shares to ServiceNow should be operating normally again.

Time: March 3, 2022, 10:17 p.m.

Status: Monitoring

Update: Some users may be experiencing issues with sharing to ServiceNow. Our teams are engaged and monitoring. <b>What's impacted?</b> • Incident Sharing We are working to mitigate impacts to our customers as quickly as possible. Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.

Time: Feb. 17, 2022, 7:29 p.m.

Status: Resolved

Update: Our team has resolved the incident and services have returned to their normal operation. <b>Start time:</b> 17:55 UTC <b>End time:</b> 19:09 UTC <b>What was impacted?</b> • Data Pipeline - All data is being accepted into the BigPanda platform, but we are experiencing delays within pipeline services. Due to this, updates to users' Incident Feeds may be delayed. <b>What was not impacted?</b> Other areas of the platform - including data ingest, analytics, incident sharing, user actions - should not be impacted. We apologize for any inconvenience that this may have caused. Should you continue to experience any issues, please reach out to us via our in-app chat or at [email protected].

Time: Feb. 17, 2022, 7:10 p.m.

Status: Monitoring

Update: Our team has implemented a fix for the issue. We will continue to monitor for any change in operational capacity. <b>What's impacted?</b> • Data Pipeline - All data is being accepted into the BigPanda platform, but we are experiencing delays within pipeline services. Due to this, updates to users' Incident Feeds may be delayed. <b>What’s not impacted?</b> Other areas of the platform - including data ingest, analytics, incident sharing, user actions - should not be impacted.

Time: Feb. 17, 2022, 6:31 p.m.

Status: Identified

Update: Latencies have been mitigated for the majority of impacted customers, and the team is working on mitigation efforts for the few still experiencing latencies. <b>What's impacted?</b> • Data Pipeline - All data is being accepted into the BigPanda platform, but we are experiencing delays within pipeline services. Due to this, updates to users' Incident Feeds may be delayed. <b>What’s not impacted?</b> Other areas of the platform - including data ingest, analytics, incident sharing, user actions - should not be impacted.

Time: Feb. 17, 2022, 6:15 p.m.

Status: Identified

Update: Our team has identified the root cause and are working on a resolution. <b>What's impacted?</b> • Data Pipeline - All data is being accepted into the BigPanda platform, but we are experiencing delays within pipeline services. Due to this, updates to users' Incident Feeds may be delayed. <b>What’s not impacted?</b> Other areas of the platform - including data ingest, analytics, incident sharing, user actions - should not be impacted.

Time: Feb. 17, 2022, 5:59 p.m.

Status: Investigating

Update: Some users may be experiencing data pipeline latencies. Our teams are engaged and investigating. <b>What's impacted?</b> • Data Pipeline - All data is being accepted into the BigPanda platform, but we are experiencing delays within pipeline services. Due to this, updates to users' Incident Feeds may be delayed. <b>What’s not impacted?</b> Other areas of the platform - including data ingest, analytics, incident sharing, user actions - should not be impacted. We are working to mitigate impacts to our customers as quickly as possible. Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.