tag:status.nofence.no,2005:/historyNofence Status - Incident History2024-03-29T06:23:06+01:00Nofencetag:status.nofence.no,2005:Incident/190023312023-11-02T18:28:00+01:002023-11-02T18:37:59+01:00Issues with push notifications for Android<p><small>Nov <var data-var='date'> 2</var>, <var data-var='time'>18:28</var> CET</small><br><strong>Resolved</strong> - We've had reports from customers on Android devices that push messages weren't coming through.<br />The issue has been found and fixed, and push messages should be coming through now. <br />Apologies for the inconvenience.</p>tag:status.nofence.no,2005:Incident/176272862023-06-20T15:05:45+02:002023-06-20T15:05:45+02:00Mobile network outage<p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>15:05</var> CEST</small><br><strong>Resolved</strong> - Connectivity should now be restored for all collars.</p><p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>13:46</var> CEST</small><br><strong>Update</strong> - Service is now being restored and we already see a large increase in connected collars, we expect the issue to be resolved fairly soon.</p><p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>12:31</var> CEST</small><br><strong>Update</strong> - We have not received any further news and are unfortunately still not seeing any improvement. Unless there is a new development we will next update this status at 16:00 CEST.</p><p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>11:31</var> CEST</small><br><strong>Update</strong> - Our network operator have made some progress and are starting to gradually enable SIMs. We will update again in one hour or if we get new information.</p><p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>10:13</var> CEST</small><br><strong>Update</strong> - Our mobile network operator is still working on fixing the problem. We will next update this status in 1 hour or if there are any new developments.</p><p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>08:17</var> CEST</small><br><strong>Investigating</strong> - Our mobile network operator is experiencing an ongoing incident and as a result we have seen about 20% of our collars lose connectivity. The fence functionality is working as normal, but you may experience problems monitoring and managing your collars.</p>tag:status.nofence.no,2005:Incident/163912842023-03-08T19:54:40+01:002023-03-08T19:54:40+01:00Problems with our app, but GPS is still working<p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>19:54</var> CET</small><br><strong>Resolved</strong> - We have restored service and both my.nofence.no and the app are back up again, apologies for the inconvenience.</p><p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>18:38</var> CET</small><br><strong>Investigating</strong> - We are experiencing problems with our cloud services. At the moment it's not possible to get into the app or my.nofence.no. The collars are also not able to send updates to the cloud. The virtual fence is not affected and the animals should stay within their boundary, but it is not possible to update the pasture at this time.</p>tag:status.nofence.no,2005:Incident/104563382022-07-02T20:28:53+02:002022-07-02T20:28:53+02:00Slow response times<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>20:28</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>17:23</var> CEST</small><br><strong>Investigating</strong> - You can experience slow response times in the app or collars missing reports. <br />If possible, it could be wise to not update the pastures while this issue is still ongoing.<br />All collars will still operate as normal in the given pasture.<br />We are currently working on fixing the issue.</p>tag:status.nofence.no,2005:Incident/104523762022-07-01T22:52:39+02:002022-07-01T22:52:39+02:00Slow response times<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>22:52</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>21:35</var> CEST</small><br><strong>Identified</strong> - You can experience slow response times in the app or collars missing reports. <br />If possible, it could be wise to not update the pastures while this issue is still ongoing.<br />All collars will still operate as normal in the given pasture.<br />We are currently working on fixing the issue.</p><p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>21:08</var> CEST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.nofence.no,2005:Incident/98329162022-04-22T06:00:00+02:002022-04-22T09:12:21+02:00Mobile Network Issue<p><small>Apr <var data-var='date'>22</var>, <var data-var='time'>06:00</var> CEST</small><br><strong>Resolved</strong> - We saw a drop in connectivity between 6:00 and 9:00 CET. Connectivity is restored to normal now. We are working with our mobile network provider to understand the root cause.</p>tag:status.nofence.no,2005:Incident/97157082022-04-06T09:23:43+02:002022-04-06T09:23:43+02:00Mobile Network Issue<p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>09:23</var> CEST</small><br><strong>Resolved</strong> - The latest update from our mobile network provider is that they're seeing mobile clients recovering. <br />Nofence is seeing collars reporting normally.</p><p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>07:45</var> CEST</small><br><strong>Monitoring</strong> - Our mobile network provider has identified the issue, but they are reporting degraded service.<br /><br />We will keep monitoring the situation.</p><p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>00:24</var> CEST</small><br><strong>Update</strong> - Our mobile network provider is still working to restore service. <br />Nofence will not be actively monitoring the situation through the night, but the collars will automatically start reporting again once service is restored.</p><p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>21:25</var> CEST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>18:55</var> CEST</small><br><strong>Investigating</strong> - We've been notified by our mobile network provider that they have major disruptions to their service, starting around 18:54:14 CEST. <br /><br />Due to this disruption our collars are currently unable to report back, but the virtual fence will work as normal.<br /><br />We will report on further news from our provider.</p>tag:status.nofence.no,2005:Incident/79979622021-09-15T12:55:15+02:002021-09-15T12:55:15+02:00Slow response times<p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>12:55</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>10:04</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>09:52</var> CEST</small><br><strong>Investigating</strong> - We're experiencing slow response times and timeouts in the app and my.nofence.no.<br /><br />The collars are unaffected by this problem and the virtual fence functionality continues to work as normal.</p>tag:status.nofence.no,2005:Incident/79467832021-09-08T18:03:05+02:002021-09-08T18:03:05+02:00High load on server causing requests to fail<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>18:03</var> CEST</small><br><strong>Resolved</strong> - Load has fallen back to normal levels</p><p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>17:26</var> CEST</small><br><strong>Investigating</strong> - We are experiencing high load on our servers and as a result you might get an error when visiting my.nofence.no or when using the app.</p>tag:status.nofence.no,2005:Incident/77810442021-08-17T12:33:27+02:002021-08-17T12:33:27+02:00High load on servers causing poor performance and loss of functionality<p><small>Aug <var data-var='date'>17</var>, <var data-var='time'>12:33</var> CEST</small><br><strong>Resolved</strong> - The servers are stable again</p><p><small>Aug <var data-var='date'>17</var>, <var data-var='time'>11:45</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the result</p><p><small>Aug <var data-var='date'>17</var>, <var data-var='time'>11:36</var> CEST</small><br><strong>Investigating</strong> - We are experiencing high load on our servers and as a result the app will appear slow and some customers will also experience that they get an empty set of collars and pastures in the app. Not to worry, the pastures and collars are there, but the app isn't able to retrieve them from the server.</p>tag:status.nofence.no,2005:Incident/75008972021-07-14T11:07:56+02:002021-07-14T11:07:56+02:00Service degradation in the NetCom Norways network, partial service available for Nofence customers using NetCom.<p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>11:07</var> CEST</small><br><strong>Resolved</strong> - All systems are reporting normally. The cause of the incident was a due to a change in tele2's network which has been rolled back.</p><p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>10:55</var> CEST</small><br><strong>Monitoring</strong> - An issue has been fix by our mobile network provide and we're seeing a normal number of collars reporting back. We'll monitor for a while before resolving.</p><p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>09:40</var> CEST</small><br><strong>Update</strong> - NOTE: The collar units will continue to provide virtual fencing normally, it's only the data link back to my.nofence.no and the application that might be affected at the moment. The data will be available once the incident is resolved.</p><p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>09:14</var> CEST</small><br><strong>Investigating</strong> - Our mobile provider is investigating. The outage affects those collars on the NetCom network in Norway.</p>tag:status.nofence.no,2005:Incident/73110732021-06-23T12:57:32+02:002021-06-23T12:57:32+02:00No new data from collars and problem updating pasture<p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>12:57</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>11:19</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>10:21</var> CEST</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>10:20</var> CEST</small><br><strong>Identified</strong> - Some collars are not reporting new data, and if they are assigned to a new pasture the pasture cannot be loaded.</p>tag:status.nofence.no,2005:Incident/72503172021-06-14T23:00:02+02:002021-06-16T13:45:42+02:00Degraded app and website performance<p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>23:00</var> CEST</small><br><strong>Resolved</strong> - At 23:00 CEST we identified and deployed a fix for the problem and performance has been restored.</p><p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>14:00</var> CEST</small><br><strong>Investigating</strong> - The Nofence app and my.nofence.no website are experiencing degraded performance with many requests timing out</p>tag:status.nofence.no,2005:Incident/72057802021-05-29T11:06:00+02:002021-06-16T13:45:42+02:00Mobile network<p><small>May <var data-var='date'>29</var>, <var data-var='time'>11:06</var> CEST</small><br><strong>Resolved</strong> - The mobile network is currently down so the the collars cannot contact the server and the app will not receive updated information from the collars. The collars are still working as normal.</p>