Mero Technologies Status - Incident history https://status.mero.co Mero Technologies Sat, 22 Nov 2025 14:00:00 +0000 Scheduled maintenance for Mero Control Center. Type: Maintenance Duration: 1 hour and 54 minutes Affected Components: API, Mero Control Centre Nov 22, 14:00:00 GMT+0 - Identified - We are planning for a large infrastructure upgrade to the Mero Control Center over the weekend. We will do our best to keep interruptions minimal over this period. For updates, go to [status.mero.co](http://status.mero.co). We will send another email when maintenance is completed. Nov 24, 01:07:41 GMT+0 - Identified - Maintenance is now in progress. Nov 24, 03:01:31 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 1 hour and 54 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 22</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a large infrastructure upgrade to the Mero Control Center over the weekend. We will do our best to keep interruptions minimal over this period. For updates, go to [status.mero.co](http://status.mero.co). We will send another email when maintenance is completed. .</p> <p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>01:07:41</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>03:01:31</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Sat, 22 Nov 2025 14:00:00 +0000 https://status.mero.co/maintenance/cmi9asu7y002l63oecq8iw5c2 https://status.mero.co/maintenance/cmi9asu7y002l63oecq8iw5c2 Visit Processing Delay - October 20, 2025 Type: Incident Duration: 5 hours and 54 minutes Affected Components: Mero Control Centre, API Oct 20, 15:00:00 GMT+0 - Identified - We're experiencing a temporary delay in processing cleaner visit records. All data is being collected safely and will be processed automatically. No action needed on your end. We'll notify you once resolved. Oct 20, 17:58:46 GMT+0 - Identified - Our team continues to work on the issue. No visit records appear to be lost but there is a delay. Oct 20, 20:53:58 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 5 hours and 54 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - We're experiencing a temporary delay in processing cleaner visit records. All data is being collected safely and will be processed automatically. No action needed on your end. We'll notify you once resolved..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>17:58:46</var> GMT+0</small><br><strong>Identified</strong> - Our team continues to work on the issue. No visit records appear to be lost but there is a delay. .</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>20:53:58</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 20 Oct 2025 15:00:00 +0000 https://status.mero.co/incident/cmgzh0vae052eap0l9iubmxz6 https://status.mero.co/incident/cmgzh0vae052eap0l9iubmxz6 Scheduled Maintenance for IOT Connectivity Type: Maintenance Duration: 3 hours Affected Components: Third-Party Cellular Provider Jul 14, 04:30:23 GMT+0 - Completed - Maintenance has completed successfully. Jul 14, 01:30:00 GMT+0 - Identified - We are performing scheduled maintenance on our IoT infrastructure to improve system performance and reliability. A small subset of customers may experience temporary router connectivity issues. Service will be restored automatically as work is completed. Type: Maintenance

Duration: 3 hours

Affected Components:

<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>04:30:23</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>01:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are performing scheduled maintenance on our IoT infrastructure to improve system performance and reliability. A small subset of customers may experience temporary router connectivity issues. Service will be restored automatically as work is completed..</p> ]]> Mon, 14 Jul 2025 01:30:00 +0000 https://status.mero.co/maintenance/cmd2ekr4800audk1z3v16qe53 https://status.mero.co/maintenance/cmd2ekr4800audk1z3v16qe53 Network Connectivity Issue – Identified Type: Incident Duration: 7 hours and 25 minutes Affected Components: Third-Party Cellular Provider Jun 24, 00:33:09 GMT+0 - Identified - We’ve confirmed a connectivity issue affecting Mero gateways that use Rogers IoT SIMs. Rogers has acknowledged a broad outage on their network and is actively working to resolve it as soon as possible. We’ll continue to keep you updated as we receive more information from Rogers. Thank you for your understanding and patience. Jun 24, 00:16:56 GMT+0 - Identified - We’re currently experiencing connectivity issues affecting Mero gateways that rely specifically on the Rogers network. The Mero platform itself is fully operational — this issue is isolated to a subset of devices using Rogers cellular connectivity. We’re working closely with Rogers to investigate and resolve the issue. We’ll continue to share updates as we learn more. Thank you for your understanding. Jun 24, 04:10:40 GMT+0 - Monitoring - We’re seeing signs of recovery, with many Mero gateways beginning to reconnect. However, we have not yet received official confirmation from Rogers that the issue is fully resolved. We’re continuing to monitor the situation closely and are in contact with Rogers to ensure full restoration. We’ll provide a final update once confirmation is received. Thank you for your continued patience and understanding. Jun 24, 07:41:35 GMT+0 - Resolved - Rogers has confirmed that the network issue affecting their cellular services has been fully resolved. Mero gateways using Rogers connectivity are now coming back online and operating as expected. Our team will continue to monitor to ensure full stability. Thank you for your patience and understanding throughout this incident. Jun 24, 02:28:49 GMT+0 - Monitoring - Mero has received the following update from Rogers: "The Rogers networking team has implemented a workaround that appears to have resolved the issue for the majority of impacted users. While progress is positive, we are aware that some devices have yet to re-establish connection. Efforts are ongoing to address the remaining impact, and the situation continues to be closely monitored. Updates will be shared as they become available." Type: Incident

Duration: 7 hours and 25 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>00:33:09</var> GMT+0</small><br><strong>Identified</strong> - We’ve confirmed a connectivity issue affecting Mero gateways that use Rogers IoT SIMs. Rogers has acknowledged a broad outage on their network and is actively working to resolve it as soon as possible. We’ll continue to keep you updated as we receive more information from Rogers. Thank you for your understanding and patience..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>00:16:56</var> GMT+0</small><br><strong>Identified</strong> - We’re currently experiencing connectivity issues affecting Mero gateways that rely specifically on the Rogers network. The Mero platform itself is fully operational — this issue is isolated to a subset of devices using Rogers cellular connectivity. We’re working closely with Rogers to investigate and resolve the issue. We’ll continue to share updates as we learn more. Thank you for your understanding..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>04:10:40</var> GMT+0</small><br><strong>Monitoring</strong> - We’re seeing signs of recovery, with many Mero gateways beginning to reconnect. However, we have not yet received official confirmation from Rogers that the issue is fully resolved. We’re continuing to monitor the situation closely and are in contact with Rogers to ensure full restoration. We’ll provide a final update once confirmation is received. Thank you for your continued patience and understanding..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>07:41:35</var> GMT+0</small><br><strong>Resolved</strong> - Rogers has confirmed that the network issue affecting their cellular services has been fully resolved. Mero gateways using Rogers connectivity are now coming back online and operating as expected. Our team will continue to monitor to ensure full stability. Thank you for your patience and understanding throughout this incident..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>02:28:49</var> GMT+0</small><br><strong>Monitoring</strong> - Mero has received the following update from Rogers: "The Rogers networking team has implemented a workaround that appears to have resolved the issue for the majority of impacted users. While progress is positive, we are aware that some devices have yet to re-establish connection. Efforts are ongoing to address the remaining impact, and the situation continues to be closely monitored. Updates will be shared as they become available.".</p> ]]> Tue, 24 Jun 2025 00:16:56 +0000 https://status.mero.co/incident/cmc9rzv3j001i6boj8ltnr7i6 https://status.mero.co/incident/cmc9rzv3j001i6boj8ltnr7i6 Data Loading Issue Type: Incident Duration: 15 minutes Affected Components: Mero Control Centre May 22, 14:00:56 GMT+0 - Resolved - The incident has been resolved. May 22, 13:45:29 GMT+0 - Identified - We are currently experiencing an issue affecting data loading in the Mero Control Centre for some customers. Our team is actively investigating and working to resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience. We’ll provide an update as soon as the issue is resolved. Type: Incident

Duration: 15 minutes

Affected Components:

<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>14:00:56</var> GMT+0</small><br><strong>Resolved</strong> - The incident has been resolved. .</p> <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>13:45:29</var> GMT+0</small><br><strong>Identified</strong> - We are currently experiencing an issue affecting data loading in the Mero Control Centre for some customers. Our team is actively investigating and working to resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience. We’ll provide an update as soon as the issue is resolved..</p> ]]> Thu, 22 May 2025 13:45:29 +0000 https://status.mero.co/incident/cmazfckgz000u13ytxe0jsdo2 https://status.mero.co/incident/cmazfckgz000u13ytxe0jsdo2 Sample Outage Type: Incident Duration: 11 hours and 52 minutes Affected Components: API, Mero Control Centre, Third-Party LoRA Network Provider, Third-Party Cellular Provider Jun 26, 16:02:54 GMT+0 - Resolved - The networking issue has been fully resolved. The outage lasted from June 25th at 10:30PM to June 26th at 9:32AM ET. Below is the following post-mortem summary from Rogers: "... Rogers teams identified that last night around 10:30 PM ET there was a spike in traffic... Rogers teams identified a VPN tunnel dropped at that time which led teams to suspect this was the cause and immediately failed over the firewall. Once this failed over was completed, teams immediately saw that traffic began to normalize." Jun 26, 14:02:54 GMT+0 - Monitoring - The issue with our networking provider, Rogers, has been identified and resolved. Devices are starting to regain their cellular connection. We are continuing to monitor the situation and will provide further updates here. We were able to narrow down the issue to an outage within the Rogers Cellular Network, specifically affecting their IoT infrastructure (Jasper). This issue was completely isolated from Mero’s systems. We are waiting for Rogers to conduct a post-mortem analysis on the issue and will update our status page (https://status.mero.co/) with more information as it becomes available. Jun 26, 12:46:01 GMT+0 - Identified - We've identified the issue to an outage with our 3rd Party Cellular Provider, Rogers/Jasper. We are in contact with Support Engineers at Rogers and they are working to fix the issue. Jun 26, 04:11:00 GMT+0 - Investigating - We are currently not receiving samples from some sites due to a potential outage with our LoRA/Sensor Network Provider. We are investigating the cause. Type: Incident

Duration: 11 hours and 52 minutes

Affected Components: , , ,

<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>16:02:54</var> GMT+0</small><br><strong>Resolved</strong> - The networking issue has been fully resolved. The outage lasted from June 25th at 10:30PM to June 26th at 9:32AM ET. Below is the following post-mortem summary from Rogers: "... Rogers teams identified that last night around 10:30 PM ET there was a spike in traffic... Rogers teams identified a VPN tunnel dropped at that time which led teams to suspect this was the cause and immediately failed over the firewall. Once this failed over was completed, teams immediately saw that traffic began to normalize.".</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>14:02:54</var> GMT+0</small><br><strong>Monitoring</strong> - The issue with our networking provider, Rogers, has been identified and resolved. Devices are starting to regain their cellular connection. We are continuing to monitor the situation and will provide further updates here. We were able to narrow down the issue to an outage within the Rogers Cellular Network, specifically affecting their IoT infrastructure (Jasper). This issue was completely isolated from Mero’s systems. We are waiting for Rogers to conduct a post-mortem analysis on the issue and will update our status page (https://status.mero.co/) with more information as it becomes available..</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>12:46:01</var> GMT+0</small><br><strong>Identified</strong> - We've identified the issue to an outage with our 3rd Party Cellular Provider, Rogers/Jasper. We are in contact with Support Engineers at Rogers and they are working to fix the issue. .</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>04:11:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently not receiving samples from some sites due to a potential outage with our LoRA/Sensor Network Provider. We are investigating the cause. .</p> ]]> Wed, 26 Jun 2024 04:11:00 +0000 https://status.mero.co/incident/clxvqmdn03248bhoockq3rqkd https://status.mero.co/incident/clxvqmdn03248bhoockq3rqkd Sample Processing Issue Type: Incident Duration: 11 hours and 30 minutes Affected Components: API, Mero Control Centre May 29, 03:50:00 GMT+0 - Identified - Samples/beacon data is unable to be processed. This means that data will not be showing on the dashboard. We are continuing to work on a fix for this incident. May 29, 15:20:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 11 hours and 30 minutes

Affected Components: ,

<p><small>May <var data-var='date'> 29</var>, <var data-var='time'>03:50:00</var> GMT+0</small><br><strong>Identified</strong> - Samples/beacon data is unable to be processed. This means that data will not be showing on the dashboard. We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 29</var>, <var data-var='time'>15:20:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 29 May 2024 03:50:00 +0000 https://status.mero.co/incident/clwrvxk5a51326bfn36f5zyfkc https://status.mero.co/incident/clwrvxk5a51326bfn36f5zyfkc Sample Outage Type: Incident Duration: 14 days, 8 hours and 22 minutes Affected Components: API, Mero Control Centre Apr 23, 05:24:21 GMT+0 - Resolved - The issue is resolved. Samples are coming into the system. No data was lost Apr 22, 23:40:00 GMT+0 - Investigating - We are currently investigating this incident. Sensor Data is unable to reach the Mero product at this time Type: Incident

Duration: 14 days, 8 hours and 22 minutes

Affected Components: ,

<p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>05:24:21</var> GMT+0</small><br><strong>Resolved</strong> - The issue is resolved. Samples are coming into the system. No data was lost.</p> <p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>23:40:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Sensor Data is unable to reach the Mero product at this time.</p> ]]> Mon, 22 Apr 2024 23:40:00 +0000 https://status.mero.co/incident/clvbw4yqa13146bdoj3f9b98dc https://status.mero.co/incident/clvbw4yqa13146bdoj3f9b98dc Temporary Disruption Due to IoT Provider Type: Incident Affected Components: API, Mero Control Centre Jan 24, 16:56:55 GMT+0 - Resolved - We are currently experiencing a temporary disruption in our services due to rate limiting imposed by our IoT provider. This has resulted in a temporary network outage. We are currently investigating this incident and have contacted our provider. Type: Incident

Affected Components: ,

<p><small>Jan <var data-var='date'> 24</var>, <var data-var='time'>16:56:55</var> GMT+0</small><br><strong>Resolved</strong> - We are currently experiencing a temporary disruption in our services due to rate limiting imposed by our IoT provider. This has resulted in a temporary network outage. We are currently investigating this incident and have contacted our provider..</p> ]]> Wed, 24 Jan 2024 16:56:55 +0000 https://status.mero.co/incident/clrs12fwo26051buoj23z3jnf4 https://status.mero.co/incident/clrs12fwo26051buoj23z3jnf4 Users are unable to login Type: Incident Duration: 20 hours and 47 minutes Affected Components: Mero Control Centre Sep 22, 19:32:31 GMT+0 - Resolved - The issue has been resolved. Logins are restored. Sep 22, 19:11:45 GMT+0 - Identified - We are continuing to work on a fix for this incident. Type: Incident

Duration: 20 hours and 47 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>19:32:31</var> GMT+0</small><br><strong>Resolved</strong> - The issue has been resolved. Logins are restored. .</p> <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>19:11:45</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> ]]> Fri, 22 Sep 2023 19:11:45 +0000 https://status.mero.co/incident/clmuza7ga48809bkn19hbcvlxo https://status.mero.co/incident/clmuza7ga48809bkn19hbcvlxo Data Transfer Outage Type: Incident Duration: 2 hours and 20 minutes Jun 2, 17:29:33 GMT+0 - Identified - We have narrowed down the issue to an issue with the AWS RedShift service. We are continuing to work to resolve this issue. Jun 2, 17:51:08 GMT+0 - Monitoring - We are currently monitoring the fix as the database restarts. We expect to be fully operational when the restart completes Jun 2, 16:49:45 GMT+0 - Investigating - Validation Dashboard is currently not displaying sensor data. We are currently investigating this incident. Sensor data is still being stored. We will update when we have more information. Jun 2, 19:01:58 GMT+0 - Monitoring - Mero continues to work with AWS' internal Engineering team to bring up our instance. We will continue to provide updates. Jun 2, 19:09:45 GMT+0 - Resolved - The issue has been resolved. Dashboard services are fully operational. We are conducting a post mortem with the AWS team to identify root cause and potential future mitigations Type: Incident

Duration: 2 hours and 20 minutes

<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>17:29:33</var> GMT+0</small><br><strong>Identified</strong> - We have narrowed down the issue to an issue with the AWS RedShift service. We are continuing to work to resolve this issue. .</p> <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>17:51:08</var> GMT+0</small><br><strong>Monitoring</strong> - We are currently monitoring the fix as the database restarts. We expect to be fully operational when the restart completes.</p> <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>16:49:45</var> GMT+0</small><br><strong>Investigating</strong> - Validation Dashboard is currently not displaying sensor data. We are currently investigating this incident. Sensor data is still being stored. We will update when we have more information. .</p> <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>19:01:58</var> GMT+0</small><br><strong>Monitoring</strong> - Mero continues to work with AWS' internal Engineering team to bring up our instance. We will continue to provide updates. .</p> <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>19:09:45</var> GMT+0</small><br><strong>Resolved</strong> - The issue has been resolved. Dashboard services are fully operational. We are conducting a post mortem with the AWS team to identify root cause and potential future mitigations .</p> ]]> Fri, 2 Jun 2023 16:49:45 +0000 https://status.mero.co/incident/cliesw79a59817trowlaxv0hrj https://status.mero.co/incident/cliesw79a59817trowlaxv0hrj DNS Settings Update Type: Incident Duration: 3 minutes Affected Components: API May 16, 17:10:00 GMT+0 - Identified - A change to Mero's DNS settings has caused a brief, unexpected period of downtime while propagation is completed. We are continuing to work on a fix for this incident. May 16, 17:13:00 GMT+0 - Resolved - DNS propagation has completed. Systems have restored. Mero is conducting a post-mortem and will adjust relevant procedures as a result. Type: Incident

Duration: 3 minutes

Affected Components:

<p><small>May <var data-var='date'> 16</var>, <var data-var='time'>17:10:00</var> GMT+0</small><br><strong>Identified</strong> - A change to Mero's DNS settings has caused a brief, unexpected period of downtime while propagation is completed. We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 16</var>, <var data-var='time'>17:13:00</var> GMT+0</small><br><strong>Resolved</strong> - DNS propagation has completed. Systems have restored. Mero is conducting a post-mortem and will adjust relevant procedures as a result. .</p> ]]> Tue, 16 May 2023 17:10:00 +0000 https://status.mero.co/incident/clhqjeavm250579b9ncd0ym7hmb https://status.mero.co/incident/clhqjeavm250579b9ncd0ym7hmb