Mission Communications Status - Incident history https://status.123scada.com Mission Communications Tue, 29 Sep 2026 16:15:36 +0000 Mission SCADA System Degraded Performance Type: Incident Affected Components: Intertie, Inbound, Legacy Portal, Corporate Website, Tank & Well, Email, Integrations, Phone, Bulk Water Meter, Mission Phone Queue, OPC UA, SMS, Outbound, Verizon, Telenor, 123Scada, AT&T Sep 29, 16:15:36 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 29, 18:43:59 GMT+0 - Identified - Mission engineers continue working to stabilize our systems. Incoming RTU data is being processed, but updates may appear slightly delayed in the [123scada.com](http://123scada.com) portal. Alarms remain operational; however, notifications by text message, phone call, and email may also be delayed. The root cause has been traced back to a hardware failure. Type: Incident

Affected Components: , , , , , , , , , , , , , , , ,

<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>16:15:36</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>18:43:59</var> GMT+0</small><br><strong>Identified</strong> - Mission engineers continue working to stabilize our systems. Incoming RTU data is being processed, but updates may appear slightly delayed in the [123scada.com](http://123scada.com) portal. Alarms remain operational; however, notifications by text message, phone call, and email may also be delayed. The root cause has been traced back to a hardware failure..</p> ]]> Tue, 29 Sep 2026 16:15:36 +0000 https://status.123scada.com/incident/cmumvo9ps059g1bnl25cibwyb https://status.123scada.com/incident/cmumvo9ps059g1bnl25cibwyb Partial Carrier Outage Type: Incident Duration: 11 hours and 47 minutes Affected Components: Intertie, Tank & Well, Bulk Water Meter, Telenor Aug 27, 23:20:00 GMT+0 - Identified - Mission Engineers are aware of a partial outage affecting a small number of RTU. We are working with the carrier to resolve as soon as possible. Automated Remote Control customers should monitor for communications failure alarms carefully. Aug 28, 11:06:36 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 11 hours and 47 minutes

Affected Components: , , ,

<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>23:20:00</var> GMT+0</small><br><strong>Identified</strong> - Mission Engineers are aware of a partial outage affecting a small number of RTU. We are working with the carrier to resolve as soon as possible. Automated Remote Control customers should monitor for communications failure alarms carefully. .</p> <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>11:06:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 27 Aug 2026 23:20:00 +0000 https://status.123scada.com/incident/cmtc9k7dn001713ldfr2s85ty https://status.123scada.com/incident/cmtc9k7dn001713ldfr2s85ty Data Ingress Issues Type: Incident Duration: 3 hours and 20 minutes Affected Components: Intertie, Inbound, Tank & Well, Bulk Water Meter Aug 8, 14:29:12 GMT+0 - Identified - Mission Engineers have identified an issue with Data ingress issues and are working to resolve. Aug 8, 14:39:00 GMT+0 - Monitoring - Mission Engineers resolved the issue and data ingress has entirely stabilized. We continue to monitor for stability. Aug 8, 17:49:31 GMT+0 - Resolved - Mission Engineers have confirmed stability of data ingress and will continue to monitor. Type: Incident

Duration: 3 hours and 20 minutes

Affected Components: , , ,

<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>14:29:12</var> GMT+0</small><br><strong>Identified</strong> - Mission Engineers have identified an issue with Data ingress issues and are working to resolve. .</p> <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>14:39:00</var> GMT+0</small><br><strong>Monitoring</strong> - Mission Engineers resolved the issue and data ingress has entirely stabilized. We continue to monitor for stability. .</p> <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>17:49:31</var> GMT+0</small><br><strong>Resolved</strong> - Mission Engineers have confirmed stability of data ingress and will continue to monitor. .</p> ]]> Sat, 8 Aug 2026 14:29:12 +0000 https://status.123scada.com/incident/cmskgz5ol0psk0kpqylru06u8 https://status.123scada.com/incident/cmskgz5ol0psk0kpqylru06u8 RTU Connectivity Disturbance for Telenor Devices Type: Incident Duration: 1 hour and 9 minutes Affected Components: Telenor Jul 14, 13:12:48 GMT+0 - Investigating - We are currently investigating this incident. Jul 14, 13:13:49 GMT+0 - Identified - We are continuing to monitor RTU reconnections. Jul 14, 13:41:28 GMT+0 - Monitoring - We are continuing to monitor RTUs as their connections stabilize. Jul 14, 14:21:42 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 9 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>13:12:48</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>13:13:49</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to monitor RTU reconnections..</p> <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>13:41:28</var> GMT+0</small><br><strong>Monitoring</strong> - We are continuing to monitor RTUs as their connections stabilize..</p> <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>14:21:42</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 14 Jul 2026 13:12:48 +0000 https://status.123scada.com/incident/cmrko8lfd0ejs0zpnmhb2g4uy https://status.123scada.com/incident/cmrko8lfd0ejs0zpnmhb2g4uy Identified-SystemAlert-No-Notify Type: Incident Duration: 6 hours and 25 minutes Affected Components: Inbound, Legacy Portal, Corporate Website, Email, Phone, SMS, Verizon, Telenor, 123Scada, AT&T May 26, 12:34:34 GMT+0 - Identified - Mission Engineers have identified potential issues with 123SCADA and phone lines and are working to resolve. May 26, 12:36:38 GMT+0 - Investigating - We are currently investigating this incident. May 26, 15:40:40 GMT+0 - Monitoring - Mission Engineers have implemented a fix and are monitoring the resolution. May 26, 19:00:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 6 hours and 25 minutes

Affected Components: , , , , , , , , ,

<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>12:34:34</var> GMT+0</small><br><strong>Identified</strong> - Mission Engineers have identified potential issues with 123SCADA and phone lines and are working to resolve..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>12:36:38</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>15:40:40</var> GMT+0</small><br><strong>Monitoring</strong> - Mission Engineers have implemented a fix and are monitoring the resolution..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. .</p> ]]> Tue, 26 May 2026 12:34:34 +0000 https://status.123scada.com/incident/cmpmmaoum0dm4nrmm38h8m0fn https://status.123scada.com/incident/cmpmmaoum0dm4nrmm38h8m0fn OPC-UA Maintenance Type: Maintenance Duration: 2 hours Affected Components: OPC UA, 123Scada May 13, 18:00:00 GMT+0 - Identified - Mission Engineers are planning minimally disruptive updates to OPC-UA and the 123SCADA Platform. May 13, 18:00:01 GMT+0 - Identified - Maintenance is now in progress May 13, 19:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 2 hours

Affected Components: ,

<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Identified</strong> - Mission Engineers are planning minimally disruptive updates to OPC-UA and the 123SCADA Platform. .</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Wed, 13 May 2026 18:00:00 +0000 https://status.123scada.com/maintenance/cmp30sclo01yohks87r6j2anf https://status.123scada.com/maintenance/cmp30sclo01yohks87r6j2anf Carrier Outage Type: Incident Duration: 1 hour and 30 minutes Affected Components: Inbound, Legacy Portal, Verizon, Corporate Website, Email, Phone, Telenor, AT&T, SMS, 123Scada May 4, 23:34:15 GMT+0 - Identified - Mission is aware of an outage affecting some RTUs. We are working with the carrier to resolve the issue as soon as is possible. We appreciate your patience. May 5, 00:04:47 GMT+0 - Monitoring - Majority of devices are back online. The carrier continues to investigate root cause. May 5, 01:04:42 GMT+0 - Resolved - Carrier issues are resolved. Type: Incident

Duration: 1 hour and 30 minutes

Affected Components: , , , , , , , , ,

<p><small>May <var data-var='date'> 4</var>, <var data-var='time'>23:34:15</var> GMT+0</small><br><strong>Identified</strong> - Mission is aware of an outage affecting some RTUs. We are working with the carrier to resolve the issue as soon as is possible. We appreciate your patience..</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>00:04:47</var> GMT+0</small><br><strong>Monitoring</strong> - Majority of devices are back online. The carrier continues to investigate root cause. .</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>01:04:42</var> GMT+0</small><br><strong>Resolved</strong> - Carrier issues are resolved..</p> ]]> Mon, 4 May 2026 23:34:15 +0000 https://status.123scada.com/incident/cmoru6awb024c979lvclzfgwu https://status.123scada.com/incident/cmoru6awb024c979lvclzfgwu Inbound Data Delays Type: Incident Duration: 24 minutes Affected Components: Intertie, Inbound, Tank & Well, Bulk Water Meter May 4, 15:17:00 GMT+0 - Investigating - Mission Engineers are investigating an issue with Inbound data and are working to resolve. May 4, 15:20:00 GMT+0 - Identified - Mission Engineers have identified an issue with Inbound data and are working to resolve. May 4, 15:40:46 GMT+0 - Resolved - Mission Engineers have implemented fixes and are monitoring data ingress. Type: Incident

Duration: 24 minutes

Affected Components: , , ,

<p><small>May <var data-var='date'> 4</var>, <var data-var='time'>15:17:00</var> GMT+0</small><br><strong>Investigating</strong> - Mission Engineers are investigating an issue with Inbound data and are working to resolve..</p> <p><small>May <var data-var='date'> 4</var>, <var data-var='time'>15:20:00</var> GMT+0</small><br><strong>Identified</strong> - Mission Engineers have identified an issue with Inbound data and are working to resolve..</p> <p><small>May <var data-var='date'> 4</var>, <var data-var='time'>15:40:46</var> GMT+0</small><br><strong>Resolved</strong> - Mission Engineers have implemented fixes and are monitoring data ingress. .</p> ]]> Mon, 4 May 2026 15:17:00 +0000 https://status.123scada.com/incident/cmorcxldl00gs141wrusuqquz https://status.123scada.com/incident/cmorcxldl00gs141wrusuqquz Infrastructure Upgrades Type: Maintenance Duration: 24 minutes Affected Components: Inbound, Tank & Well Apr 14, 14:15:00 GMT+0 - Identified - Mission engineers will be performing infrastructure upgrades Tuesday, April 14th from 10:15 to 11:15 AM Eastern. No impact to RTUs or alarms are expected. We will provide updates as available. Apr 14, 14:15:01 GMT+0 - Identified - Maintenance is now in progress Apr 14, 14:39:09 GMT+0 - Completed - Maintenance has been completed successfully and Mission Engineers are monitoring all systems. No impacts to RTU were observed. Type: Maintenance

Duration: 24 minutes

Affected Components: ,

<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>14:15:00</var> GMT+0</small><br><strong>Identified</strong> - Mission engineers will be performing infrastructure upgrades Tuesday, April 14th from 10:15 to 11:15 AM Eastern. No impact to RTUs or alarms are expected. We will provide updates as available. .</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>14:15:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>14:39:09</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has been completed successfully and Mission Engineers are monitoring all systems. No impacts to RTU were observed..</p> ]]> Tue, 14 Apr 2026 14:15:00 +0000 https://status.123scada.com/maintenance/cmnyoozfp001m6i6qy2ea3duy https://status.123scada.com/maintenance/cmnyoozfp001m6i6qy2ea3duy Monitoring Inbound Data Delays Type: Incident Duration: 20 minutes Affected Components: Intertie, Inbound, Tank & Well, Bulk Water Meter, OPC UA, , 123Scada, Automated Remote Control → Apr 2, 15:36:00 GMT+0 - Identified - Mission Engineers identified a delay to inbound data starting at 11:36am Eastern. Apr 2, 15:56:00 GMT+0 - Resolved - Mission Engineers have confirmed the delays to inbound data have been resolved. Type: Incident

Duration: 20 minutes

Affected Components: , , , , , ,

<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>15:36:00</var> GMT+0</small><br><strong>Identified</strong> - Mission Engineers identified a delay to inbound data starting at 11:36am Eastern..</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>15:56:00</var> GMT+0</small><br><strong>Resolved</strong> - Mission Engineers have confirmed the delays to inbound data have been resolved. .</p> ]]> Thu, 2 Apr 2026 15:36:00 +0000 https://status.123scada.com/incident/cmnhnt5af03pco5fnra01pald https://status.123scada.com/incident/cmnhnt5af03pco5fnra01pald Carrier Issue - Telenor Type: Incident Duration: 2 hours and 34 minutes Affected Components: Telenor Mar 25, 07:00:06 GMT+0 - Investigating - Mission is investigating issues reported on select wireless carriers. Mar 25, 07:46:06 GMT+0 - Identified - Mission is aware of an upstream carrier issue that is affecting some RTUs. We are working with the carrier to resolve the issue as soon as is possible. At this time, only devices using Telenor are impacted and direct ATT and Verizon continue to operate normally. Mar 25, 09:20:28 GMT+0 - Monitoring - Mission Engineers are observing an improvement in registrations and connections. Mission will continue to monitor for device reconnection and connection stability. Mar 25, 09:33:46 GMT+0 - Resolved - This incident has been resolved. Mission Engineers continue to monitor for platform stability. Type: Incident

Duration: 2 hours and 34 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>07:00:06</var> GMT+0</small><br><strong>Investigating</strong> - Mission is investigating issues reported on select wireless carriers..</p> <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>07:46:06</var> GMT+0</small><br><strong>Identified</strong> - Mission is aware of an upstream carrier issue that is affecting some RTUs. We are working with the carrier to resolve the issue as soon as is possible. At this time, only devices using Telenor are impacted and direct ATT and Verizon continue to operate normally..</p> <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>09:20:28</var> GMT+0</small><br><strong>Monitoring</strong> - Mission Engineers are observing an improvement in registrations and connections. Mission will continue to monitor for device reconnection and connection stability..</p> <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>09:33:46</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Mission Engineers continue to monitor for platform stability. .</p> ]]> Wed, 25 Mar 2026 07:00:06 +0000 https://status.123scada.com/incident/cmn5rw0mi00itdbixkyb8dq1h https://status.123scada.com/incident/cmn5rw0mi00itdbixkyb8dq1h Corporate Website Maintenance Type: Incident Duration: 2 hours and 10 minutes Affected Components: Corporate Website Aug 23, 21:10:00 GMT+0 - Identified - We are aware of Maintenance taking place on our Corporate Website and are redirecting users to the login page. No 123SCADA components are impacted. Aug 23, 23:19:59 GMT+0 - Resolved - The maintenance for our Corporate Website is resolved. Type: Incident

Duration: 2 hours and 10 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>21:10:00</var> GMT+0</small><br><strong>Identified</strong> - We are aware of Maintenance taking place on our Corporate Website and are redirecting users to the login page. No 123SCADA components are impacted. .</p> <p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>23:19:59</var> GMT+0</small><br><strong>Resolved</strong> - The maintenance for our Corporate Website is resolved. .</p> ]]> Sat, 23 Aug 2025 21:10:00 +0000 https://status.123scada.com/incident/cmeouc1mt0061y9jamm8vtdy2 https://status.123scada.com/incident/cmeouc1mt0061y9jamm8vtdy2 AT&T Connectivity Type: Incident Duration: 1 day, 18 hours and 47 minutes Affected Components: AT&T Aug 2, 17:30:00 GMT+0 - Identified - Mission Engineers have identified the issue outside of our network and are working with the carrier to resolve. Less than 1% of devices are impacted. Aug 2, 17:20:00 GMT+0 - Investigating - Mission Engineers are aware of an issue impacting a small subset of AT&T Devices and are investigating the root cause. Aug 4, 12:07:10 GMT+0 - Resolved - Mission Engineers have confirmed that upstream work has corrected the connectivity issue. Type: Incident

Duration: 1 day, 18 hours and 47 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Identified</strong> - Mission Engineers have identified the issue outside of our network and are working with the carrier to resolve. Less than 1% of devices are impacted..</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br><strong>Investigating</strong> - Mission Engineers are aware of an issue impacting a small subset of AT&T Devices and are investigating the root cause..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>12:07:10</var> GMT+0</small><br><strong>Resolved</strong> - Mission Engineers have confirmed that upstream work has corrected the connectivity issue. .</p> ]]> Sat, 2 Aug 2025 17:20:00 +0000 https://status.123scada.com/incident/cmdux5unl000sjntiho2s7cn2 https://status.123scada.com/incident/cmdux5unl000sjntiho2s7cn2 Mission SCADA System Restored Type: Incident Duration: 3 hours and 34 minutes Affected Components: Telenor, 123Scada, SMS, Phone, Corporate Website, Email, AT&T, Verizon, Inbound, Bulk Water Meter, Intertie, Tank & Well, Legacy Portal May 16, 18:35:07 GMT+0 - Identified - Dear Valued Customer, We want to provide you with an update regarding the ongoing system network issue. Our Engineering team is continuing to work diligently to resolve the problem and restore full functionality to our services. Please be assured that resolving this issue remains our top priority, and we will continue to monitor the situation closely until the system is stable. We will share additional updates as new information becomes available. For updates, please follow our X (formerly Twitter) account: @123mc. If you have any questions or need assistance, please contact our Technical Support team at 1-877-993-1911\. We appreciate your continued patience and understanding as we work toward a resolution. Thank you, Mission Communications May 16, 22:09:35 GMT+0 - Resolved - Mission SCADA System Restored Dear Valued Customer, We are pleased to inform you that the Mission SCADA system is fully operational again. Remote monitoring and control have been restored, and our Engineering team will continue to monitor system performance over the next 72 hours to ensure stability. Thank you for your patience and understanding over the past day as we restored services. If you have any questions, please contact our Technical Support team at 1-877-993-1911\. For future updates, follow us on X (formerly Twitter): [@123mc](https://twitter.com/123mc). Kind regards, Mission Communications Type: Incident

Duration: 3 hours and 34 minutes

Affected Components: , , , , , , , , , , , ,

<p><small>May <var data-var='date'> 16</var>, <var data-var='time'>18:35:07</var> GMT+0</small><br><strong>Identified</strong> - Dear Valued Customer, We want to provide you with an update regarding the ongoing system network issue. Our Engineering team is continuing to work diligently to resolve the problem and restore full functionality to our services. Please be assured that resolving this issue remains our top priority, and we will continue to monitor the situation closely until the system is stable. We will share additional updates as new information becomes available. For updates, please follow our X (formerly Twitter) account: @123mc. If you have any questions or need assistance, please contact our Technical Support team at 1-877-993-1911\. We appreciate your continued patience and understanding as we work toward a resolution. Thank you, Mission Communications .</p> <p><small>May <var data-var='date'> 16</var>, <var data-var='time'>22:09:35</var> GMT+0</small><br><strong>Resolved</strong> - Mission SCADA System Restored Dear Valued Customer, We are pleased to inform you that the Mission SCADA system is fully operational again. Remote monitoring and control have been restored, and our Engineering team will continue to monitor system performance over the next 72 hours to ensure stability. Thank you for your patience and understanding over the past day as we restored services. If you have any questions, please contact our Technical Support team at 1-877-993-1911\. For future updates, follow us on X (formerly Twitter): [@123mc](https://twitter.com/123mc). Kind regards, Mission Communications .</p> ]]> Fri, 16 May 2025 18:35:07 +0000 https://status.123scada.com/incident/cmar51wzp002b2jv0c8agdv4o https://status.123scada.com/incident/cmar51wzp002b2jv0c8agdv4o Mission Communications Inbound Phone System - Investigating Type: Incident Affected Components: Phone Apr 4, 17:08:40 GMT+0 - Resolved - The upstream issues have been resolved and the phone system is functioning normally. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>17:08:40</var> GMT+0</small><br><strong>Resolved</strong> - The upstream issues have been resolved and the phone system is functioning normally. .</p> ]]> Thu, 4 Apr 2024 17:08:40 +0000 https://status.123scada.com/incident/clulhr17l24578b9oim9ajxrb0 https://status.123scada.com/incident/clulhr17l24578b9oim9ajxrb0