Pelco Calipsa Status - Incident history https://status.pelco.com Pelco Calipsa Tue, 14 Apr 2026 19:08:51 +0000 Calipsa Incident: May experience some alarms come through unprocessed using external API or Services API Type: Incident Affected Components: Calipsa API Apr 14, 19:08:51 GMT+0 - Investigating - Issue occurred at 11:25 PST and was resolved at 11:37 PST Apr 14, 19:09:09 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>19:08:51</var> GMT+0</small><br><strong>Investigating</strong> - Issue occurred at 11:25 PST and was resolved at 11:37 PST.</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>19:09:09</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 14 Apr 2026 19:08:51 +0000 https://status.pelco.com/incident/cmnyzvz1700nik0rjssj5t26w https://status.pelco.com/incident/cmnyzvz1700nik0rjssj5t26w [EU] Issue with Calipsa interface Type: Incident Duration: 3 hours and 40 minutes Affected Components: Calipsa Website Feb 8, 15:00:07 GMT+0 - Investigating - We are currently investigating this incident. Feb 8, 15:18:57 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 8, 17:26:53 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 8, 18:39:50 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 40 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>15:00:07</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>15:18:57</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>17:26:53</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>18:39:50</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 8 Feb 2026 15:00:07 +0000 https://status.pelco.com/incident/cmldvdprx0jih61oj0ostubdy https://status.pelco.com/incident/cmldvdprx0jih61oj0ostubdy Calipsa UI login not available EU Cluster Type: Incident Duration: 16 minutes Feb 7, 16:06:51 GMT+0 - Investigating - We are currently investigating this incident. Feb 7, 16:08:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 7, 16:09:10 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 7, 16:22:52 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 16 minutes

<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>16:06:51</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>16:08:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>16:09:10</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>16:22:52</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 7 Feb 2026 16:06:51 +0000 https://status.pelco.com/incident/cmlciboxn0254yoolylwvwqut https://status.pelco.com/incident/cmlciboxn0254yoolylwvwqut Eu Cluster: Alarms not presented on platform (Alarm Processing Unaffected) Type: Incident Affected Components: Calipsa API, Calipsa Website, Calipsa Alarm Processing Sep 9, 19:28:04 GMT+0 - Resolved - Between 19:33 GMT and 19:47 GMT, Calipsa experienced an issue where alarms were processed and forwarded but not presented on the platform. This issue has since been resolved. Sep 9, 19:29:36 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components: , ,

<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>19:28:04</var> GMT+0</small><br><strong>Resolved</strong> - Between 19:33 GMT and 19:47 GMT, Calipsa experienced an issue where alarms were processed and forwarded but not presented on the platform. This issue has since been resolved..</p> <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>19:29:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 9 Sep 2025 19:28:04 +0000 https://status.pelco.com/incident/cmfcy0tsl0008bbp51rik4ydx https://status.pelco.com/incident/cmfcy0tsl0008bbp51rik4ydx Calipsa Incident: May experience some alarms come through unprocessed Type: Incident Duration: 1 hour and 44 minutes Affected Components: Calipsa Alarm Processing Jul 17, 05:19:46 GMT+0 - Resolved - This incident has been resolved. Our team will continue to monitor the situation. Jul 17, 03:36:00 GMT+0 - Monitoring - We experienced an incident which may have impacted alarm processing through our AI. Impact Period looks to have been from 9:36PM PST to 10:45PM PST 16th July. Type: Incident

Duration: 1 hour and 44 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>05:19:46</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Our team will continue to monitor the situation. .</p> <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>03:36:00</var> GMT+0</small><br><strong>Monitoring</strong> - We experienced an incident which may have impacted alarm processing through our AI. Impact Period looks to have been from 9:36PM PST to 10:45PM PST 16th July..</p> ]]> Thu, 17 Jul 2025 03:36:00 +0000 https://status.pelco.com/incident/cmd6z58u6007oqu6tbz7q2zu4 https://status.pelco.com/incident/cmd6z58u6007oqu6tbz7q2zu4 EU Cluster: SMTP - Some alarms unprocessed between 12:22 GMT and 12:27 GMT Type: Incident Affected Components: Calipsa Alarm Processing Jul 6, 12:54:00 GMT+0 - Resolved - Between 12:22 GMT and 12:27 GMT, you may have experienced some alarms that went unprocessed. Operations are back to normal and we are currently monitoring the system. Jul 9, 18:17:33 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>12:54:00</var> GMT+0</small><br><strong>Resolved</strong> - Between 12:22 GMT and 12:27 GMT, you may have experienced some alarms that went unprocessed. Operations are back to normal and we are currently monitoring the system. .</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>18:17:33</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 6 Jul 2025 12:54:00 +0000 https://status.pelco.com/incident/cmcrobot900vuty7jhbwymyai https://status.pelco.com/incident/cmcrobot900vuty7jhbwymyai [EU Cluster] Issue Yesterday Evening With Alarm Processing Type: Incident Affected Components: Calipsa Alarm Processing May 15, 17:20:00 GMT+0 - Resolved - Yesterday evening (5/5/2025) Calipsa underwent an incident that affected the EU Cluster * Start: 18:20 GMT+1 * Finish: 18:45 GMT+1 * What happened: The exact origin of the issue is still under investigation, seems to be related to the alarm saving mechanisms. * In parallel, the status page was not updated due to human error. * Affected services: Partial outage of alarm processing, some alarms during that period may have gone unprocessed, all integrations We will continue our internal investigation and consequently implement the necessary measures to prevent it from happening again. Apologies to the inconveniences caused to your service. Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 15</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br><strong>Resolved</strong> - Yesterday evening (5/5/2025) Calipsa underwent an incident that affected the EU Cluster * Start: 18:20 GMT+1 * Finish: 18:45 GMT+1 * What happened: The exact origin of the issue is still under investigation, seems to be related to the alarm saving mechanisms. * In parallel, the status page was not updated due to human error. * Affected services: Partial outage of alarm processing, some alarms during that period may have gone unprocessed, all integrations We will continue our internal investigation and consequently implement the necessary measures to prevent it from happening again. Apologies to the inconveniences caused to your service..</p> ]]> Thu, 15 May 2025 17:20:00 +0000 https://status.pelco.com/incident/cmaqmnso6000trc8nw55ebhrq https://status.pelco.com/incident/cmaqmnso6000trc8nw55ebhrq Issues loading alarms on the Calipsa platform (Alarm Processing Unaffected) Type: Incident Duration: 5 hours and 26 minutes Affected Components: Calipsa API, Calipsa Website, Calipsa Alarm Processing Apr 3, 03:54:46 GMT+0 - Resolved - This incident has been resolved. Apr 2, 23:15:38 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 2, 22:29:00 GMT+0 - Investigating - We are currently investigating this incident. It began 3:29PM PST Apr 3, 01:28:47 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 5 hours and 26 minutes

Affected Components: , ,

<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>03:54:46</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>23:15:38</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>22:29:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. It began 3:29PM PST.</p> <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>01:28:47</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Wed, 2 Apr 2025 22:29:00 +0000 https://status.pelco.com/incident/cm90jc92q002hcxwwjpr3rbdv https://status.pelco.com/incident/cm90jc92q002hcxwwjpr3rbdv Alarm processing incident Type: Incident Duration: 2 hours and 6 minutes Affected Components: Calipsa Alarm Processing Apr 2, 13:48:54 GMT+0 - Resolved - Starting at 11:06GMT Calipsa experienced issues with the processing of alarms in the EU Cluster which was focused on the API integration, but as a result of which all other integrations were also impacted in some degree. The problem was solved at 13:18GMT and is now working as expected. We will conduct an internal investigation to further understand what happened. Apr 2, 11:42:29 GMT+0 - Investigating - We are currently investigating this incident. Apr 2, 12:56:38 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 2 hours and 6 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>13:48:54</var> GMT+0</small><br><strong>Resolved</strong> - Starting at 11:06GMT Calipsa experienced issues with the processing of alarms in the EU Cluster which was focused on the API integration, but as a result of which all other integrations were also impacted in some degree. The problem was solved at 13:18GMT and is now working as expected. We will conduct an internal investigation to further understand what happened..</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>11:42:29</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>12:56:38</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Wed, 2 Apr 2025 11:42:29 +0000 https://status.pelco.com/incident/cm8zuxnox0020nmajvfyww9f0 https://status.pelco.com/incident/cm8zuxnox0020nmajvfyww9f0 Planned Downtime Today, 26th February 2025 Type: Incident Duration: 3 hours and 4 minutes Affected Components: Calipsa API, Calipsa Website, Calipsa Alarm Processing Feb 26, 15:06:19 GMT+0 - Resolved - US Cluster update completed. Feb 26, 13:04:29 GMT+0 - Identified - \[EU Cluster\] Planned Downtime has now started, expected duration: 30min Feb 26, 12:02:36 GMT+0 - Investigating - Due to a necessary database update, we have a scheduled downtime today, February 26th. This update will ensure that our database is more efficient, resilient, and will allow for future maintenance without extended outage periods. This update will be performed on the EU Cluster first and once the EU Cluster upgrade is completed, we will update the US Cluster. We will update the status page when the upgrade for each Cluster starts and finishes. **When:** Today, 26th February 2025 **Estimated time for completion:** 30 minutes For more information, you can refer to the email that was sent on February 3rd or contact your Calipsa/ Motorola representative. During the outage, the database will not be accessible so no alarms will be saved and processed by Calipsa. Any cameras connected via API or our integrations will be presented to your operators without processing. Those processed via SMTP will not be stored, processed, or passed through during this period. Feb 26, 13:13:05 GMT+0 - Monitoring - \[EU Cluster\] Update is now completed. Expected to be working as usual. Feb 26, 13:30:49 GMT+0 - Investigating - EU Cluster update completed. US Cluster to follow later today, status page will be updated when downtime starts Feb 26, 15:00:35 GMT+0 - Identified - \[US Cluster\] Planned Downtime has now started, expected duration: 30min Type: Incident

Duration: 3 hours and 4 minutes

Affected Components: , ,

<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>15:06:19</var> GMT+0</small><br><strong>Resolved</strong> - US Cluster update completed..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>13:04:29</var> GMT+0</small><br><strong>Identified</strong> - \[EU Cluster\] Planned Downtime has now started, expected duration: 30min.</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>12:02:36</var> GMT+0</small><br><strong>Investigating</strong> - Due to a necessary database update, we have a scheduled downtime today, February 26th. This update will ensure that our database is more efficient, resilient, and will allow for future maintenance without extended outage periods. This update will be performed on the EU Cluster first and once the EU Cluster upgrade is completed, we will update the US Cluster. We will update the status page when the upgrade for each Cluster starts and finishes. **When:** Today, 26th February 2025 **Estimated time for completion:** 30 minutes For more information, you can refer to the email that was sent on February 3rd or contact your Calipsa/ Motorola representative. During the outage, the database will not be accessible so no alarms will be saved and processed by Calipsa. Any cameras connected via API or our integrations will be presented to your operators without processing. Those processed via SMTP will not be stored, processed, or passed through during this period..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>13:13:05</var> GMT+0</small><br><strong>Monitoring</strong> - \[EU Cluster\] Update is now completed. Expected to be working as usual..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>13:30:49</var> GMT+0</small><br><strong>Investigating</strong> - EU Cluster update completed. US Cluster to follow later today, status page will be updated when downtime starts.</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>15:00:35</var> GMT+0</small><br><strong>Identified</strong> - \[US Cluster\] Planned Downtime has now started, expected duration: 30min.</p> ]]> Wed, 26 Feb 2025 12:02:36 +0000 https://status.pelco.com/incident/cm7lv8tjy003mc7z1z3dncb1r https://status.pelco.com/incident/cm7lv8tjy003mc7z1z3dncb1r Planned Downtime: Wednesday - February 26th Type: Incident Affected Components: Calipsa API, Calipsa Website, Calipsa Alarm Processing Feb 24, 16:04:37 GMT+0 - Resolved - Due to a necessary database update, we are planning a scheduled downtime on February 26th. This update will ensure that our database is more efficient, resilient, and will allow for future maintenance without extended outage periods. **When:** Wednesday, 26th February 2025 **Estimated time for completion:** 30 minutes For more information, you can refer to the email that was sent on February 3rd or contact your Calipsa / Motorola representative. During the outage, the database will not be accessible so no alarms will be saved and processed by Calipsa. Any cameras connected via API or our integrations will be presented to your operators without processing. Those processed via SMTP will not be stored, processed, or passed through during this period. Type: Incident

Affected Components: , ,

<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>16:04:37</var> GMT+0</small><br><strong>Resolved</strong> - Due to a necessary database update, we are planning a scheduled downtime on February 26th. This update will ensure that our database is more efficient, resilient, and will allow for future maintenance without extended outage periods. **When:** Wednesday, 26th February 2025 **Estimated time for completion:** 30 minutes For more information, you can refer to the email that was sent on February 3rd or contact your Calipsa / Motorola representative. During the outage, the database will not be accessible so no alarms will be saved and processed by Calipsa. Any cameras connected via API or our integrations will be presented to your operators without processing. Those processed via SMTP will not be stored, processed, or passed through during this period..</p> ]]> Mon, 24 Feb 2025 16:04:37 +0000 https://status.pelco.com/incident/cm7j90e1y0003lu389d9a0bpx https://status.pelco.com/incident/cm7j90e1y0003lu389d9a0bpx [EU Cluster] Calipsa not showing alarm images in queue Type: Incident Duration: 1 hour and 7 minutes Affected Components: Calipsa Website Feb 4, 12:02:37 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 4, 11:57:38 GMT+0 - Identified - Issue limited to alarms queue interface Alarms are still getting processed as expected Feb 4, 11:38:17 GMT+0 - Investigating - We are currently investigating this incident. Feb 4, 12:04:58 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 4, 12:40:57 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 4, 12:45:25 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 7 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>12:02:37</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>11:57:38</var> GMT+0</small><br><strong>Identified</strong> - Issue limited to alarms queue interface Alarms are still getting processed as expected.</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>11:38:17</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>12:04:58</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>12:40:57</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>12:45:25</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 4 Feb 2025 11:38:17 +0000 https://status.pelco.com/incident/cm6qeotjg000pr8j3iaop7i6z https://status.pelco.com/incident/cm6qeotjg000pr8j3iaop7i6z [US Cluster] 'Cannot read properties of undefined' Error when logging in Type: Incident Duration: 1 hour Affected Components: Calipsa Website Nov 20, 14:34:14 GMT+0 - Investigating - We are currently investigating this incident. Issue limited to logging into <https://m.us-01.calipsa.io/> No alarm processing issues detected Nov 20, 14:43:37 GMT+0 - Identified - Root of the issue is detected, working on a fix Nov 20, 15:20:41 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 20, 14:33:04 GMT+0 - Investigating - We are currently investigating this incident. Nov 20, 15:33:23 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour

Affected Components:

<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>14:34:14</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Issue limited to logging into <https://m.us-01.calipsa.io/> No alarm processing issues detected.</p> <p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>14:43:37</var> GMT+0</small><br><strong>Identified</strong> - Root of the issue is detected, working on a fix.</p> <p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>15:20:41</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>14:33:04</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>15:33:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 20 Nov 2024 14:33:04 +0000 https://status.pelco.com/incident/cm3pzguqg000j19tp60v9pifm https://status.pelco.com/incident/cm3pzguqg000j19tp60v9pifm Request failures through Services API Type: Incident Duration: 15 minutes Affected Components: Calipsa API Oct 15, 14:50:00 GMT+0 - Resolved - This incident has been resolved. Oct 15, 14:35:00 GMT+0 - Investigating - We are currently investigating this incident. Some customers using Services API have been affected. Type: Incident

Duration: 15 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>14:50:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>14:35:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Some customers using Services API have been affected..</p> ]]> Tue, 15 Oct 2024 14:35:00 +0000 https://status.pelco.com/incident/cm2aqp16w0006y83yrejso5ll https://status.pelco.com/incident/cm2aqp16w0006y83yrejso5ll US Cluster: Potential Intermittent Alarm Processing Errors Type: Incident Duration: 22 minutes Affected Components: Calipsa Alarm Processing Oct 12, 19:43:09 GMT+0 - Monitoring - Operations are back to normal and we are currently monitoring the system. Oct 12, 19:35:25 GMT+0 - Investigating - We are currently investigating this incident. This is impacting the US Cluster only. Oct 12, 19:57:45 GMT+0 - Resolved - Systems are back to being fully operational. Between the times of 12:08PM PST and 12:29PM PST you may have experienced some alarms failing to be processed. Our engineering team will continue to investigate the root cause of the issue and mitigations steps. Type: Incident

Duration: 22 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>19:43:09</var> GMT+0</small><br><strong>Monitoring</strong> - Operations are back to normal and we are currently monitoring the system..</p> <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>19:35:25</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. This is impacting the US Cluster only..</p> <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>19:57:45</var> GMT+0</small><br><strong>Resolved</strong> - Systems are back to being fully operational. Between the times of 12:08PM PST and 12:29PM PST you may have experienced some alarms failing to be processed. Our engineering team will continue to investigate the root cause of the issue and mitigations steps..</p> ]]> Sat, 12 Oct 2024 19:35:25 +0000 https://status.pelco.com/incident/cm26k3gsv0009zt0ayj04n2qz https://status.pelco.com/incident/cm26k3gsv0009zt0ayj04n2qz EU Cluster: Intermittent SMTP alarms failing to be forwarded Type: Incident Duration: 22 minutes Affected Components: Calipsa Alarm Processing Oct 4, 18:28:27 GMT+0 - Investigating - We are currently investigating this incident. Oct 4, 18:50:45 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 22 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>18:28:27</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>18:50:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 4 Oct 2024 18:28:27 +0000 https://status.pelco.com/incident/cm1v26iyo000vjbga3v5hprmu https://status.pelco.com/incident/cm1v26iyo000vjbga3v5hprmu [Alarm Processing] Type: Incident Duration: 16 minutes Affected Components: Calipsa Alarm Processing Aug 5, 11:42:18 GMT+0 - Resolved - This incident has been resolved. Aug 5, 11:31:24 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 5, 11:26:07 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 16 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>11:42:18</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>11:31:24</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>11:26:07</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Mon, 5 Aug 2024 11:26:07 +0000 https://status.pelco.com/incident/clzgwo9df3607hhn3fi8qu1tn https://status.pelco.com/incident/clzgwo9df3607hhn3fi8qu1tn EU Cluster: SMTP - Some alarms unprocessed from 03:36 GMT to 03:39 GMT Type: Incident Affected Components: Calipsa Alarm Processing Jun 22, 03:46:45 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>03:46:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 22 Jun 2024 03:46:45 +0000 https://status.pelco.com/incident/clxpkw2my37031b8ohb5f6cstj https://status.pelco.com/incident/clxpkw2my37031b8ohb5f6cstj EU Cluster: Unable to load alarms Type: Incident Duration: 1 hour and 2 minutes Affected Components: Calipsa Website, Calipsa Alarm Processing May 4, 14:52:33 GMT+0 - Investigating - We are currently investigating this incident and will provide updates as they become available. Alarm processing is currently unaffected. May 4, 15:54:28 GMT+0 - Resolved - This incident has been resolved. May 4, 15:07:52 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 1 hour and 2 minutes

Affected Components: ,

<p><small>May <var data-var='date'> 4</var>, <var data-var='time'>14:52:33</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident and will provide updates as they become available. Alarm processing is currently unaffected..</p> <p><small>May <var data-var='date'> 4</var>, <var data-var='time'>15:54:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 4</var>, <var data-var='time'>15:07:52</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Sat, 4 May 2024 14:52:33 +0000 https://status.pelco.com/incident/clvs83jx7632921asojjtobwf6f https://status.pelco.com/incident/clvs83jx7632921asojjtobwf6f [Sentinel] Partial outage - Some alarms unprocessed from 16:26 GMT to 16:30 GMT Type: Incident Affected Components: Calipsa Alarm Processing May 1, 16:31:58 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>16:31:58</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 1 May 2024 16:31:58 +0000 https://status.pelco.com/incident/clvo1bu7n4036blod86guzegq https://status.pelco.com/incident/clvo1bu7n4036blod86guzegq Intermittent SMTP alarms failed to be forwarded Type: Incident Duration: 1 day and 12 hours Affected Components: Calipsa Alarm Processing May 1, 11:10:00 GMT+0 - Resolved - We have identified an issue which has now been resolved by our engineering team. Impacted time periods: 08:10AM - 09:10AM GMT 10:30AM - 11:00PM Type: Incident

Duration: 1 day and 12 hours

Affected Components:

<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>11:10:00</var> GMT+0</small><br><strong>Resolved</strong> - We have identified an issue which has now been resolved by our engineering team. Impacted time periods: 08:10AM - 09:10AM GMT 10:30AM - 11:00PM.</p> ]]> Wed, 1 May 2024 11:10:00 +0000 https://status.pelco.com/incident/clvnpwbb228911bborcw6ghh8k https://status.pelco.com/incident/clvnpwbb228911bborcw6ghh8k Alarms currently not able to be viewed within the Calipsa platform Type: Incident Duration: 2 hours and 29 minutes Affected Components: Calipsa Website, Calipsa Alarm Processing May 1, 08:59:39 GMT+0 - Investigating - We are currently investigating this incident and will provide updates as they become available. Alarm processing is currently unaffected. May 1, 09:23:02 GMT+0 - Identified - We are continuing to work on a fix for this incident. The alarm page within the Calipsa platform is currently back online. However, you may see some alarms with a higher processing time than usual. May 1, 11:15:03 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 1, 11:28:40 GMT+0 - Resolved - This issue has now been resolved. Type: Incident

Duration: 2 hours and 29 minutes

Affected Components: ,

<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>08:59:39</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident and will provide updates as they become available. Alarm processing is currently unaffected. .</p> <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>09:23:02</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. The alarm page within the Calipsa platform is currently back online. However, you may see some alarms with a higher processing time than usual. .</p> <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>11:15:03</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>11:28:40</var> GMT+0</small><br><strong>Resolved</strong> - This issue has now been resolved..</p> ]]> Wed, 1 May 2024 08:59:39 +0000 https://status.pelco.com/incident/clvnl65ns117380c5ncygzve6e9 https://status.pelco.com/incident/clvnl65ns117380c5ncygzve6e9 [Sentinel] Partial outage - Some alarms unprocessed from 20:09 GMT to 20:12 GMT Type: Incident Affected Components: Calipsa Alarm Processing Apr 29, 20:16:54 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>20:16:54</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 29 Apr 2024 20:16:54 +0000 https://status.pelco.com/incident/clvlehev0137594b4lsyhj9kq6j https://status.pelco.com/incident/clvlehev0137594b4lsyhj9kq6j EU Cluster: Alarm Processing Type: Incident Duration: 7 days, 4 hours and 41 minutes Affected Components: Calipsa Alarm Processing Apr 27, 22:00:25 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 27, 21:22:12 GMT+0 - Investigating - We are currently investigating this incident. Apr 27, 22:18:55 GMT+0 - Investigating - We are currently investigating this incident. Apr 27, 22:40:42 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 28, 00:14:52 GMT+0 - Resolved - We just experienced an issue that has affected the Calipsa system. Services have since resumed to normal. Between the time of 22:13 UTC and 22:31 UTC on 27/04/24, you may have some alarms that took longer to process, timed out or potentially may have gone unprocessed by Calipsa AI. If you are still experiencing any issues, please reach out to us via the email address below. Our sincerest apologies for the inconvenience this caused. If you want to speak to someone about this issue, please contact [support@calipsa.io](mailto:support@calipsa.io). Type: Incident

Duration: 7 days, 4 hours and 41 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>22:00:25</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>21:22:12</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>22:18:55</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>22:40:42</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>00:14:52</var> GMT+0</small><br><strong>Resolved</strong> - We just experienced an issue that has affected the Calipsa system. Services have since resumed to normal. Between the time of 22:13 UTC and 22:31 UTC on 27/04/24, you may have some alarms that took longer to process, timed out or potentially may have gone unprocessed by Calipsa AI. If you are still experiencing any issues, please reach out to us via the email address below. Our sincerest apologies for the inconvenience this caused. If you want to speak to someone about this issue, please contact [support@calipsa.io](mailto:support@calipsa.io)..</p> ]]> Sat, 27 Apr 2024 21:22:12 +0000 https://status.pelco.com/incident/clvilxo0b28400b6ol1osbgxg9 https://status.pelco.com/incident/clvilxo0b28400b6ol1osbgxg9 [Sentinel] Partial outage - Some alarms unprocessed from 20:51 GMT to 21:01 GMT Type: Incident Affected Components: Calipsa Alarm Processing Apr 27, 20:59:33 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>20:59:33</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 27 Apr 2024 20:59:33 +0000 https://status.pelco.com/incident/clvil4jt118936bdol6mtk5ipu https://status.pelco.com/incident/clvil4jt118936bdol6mtk5ipu