Nabto Status - Incident history https://status.nabto.com Nabto Thu, 9 Jul 2026 19:17:35 +0000 Nabto TURN services outage Type: Incident Duration: 5 minutes Affected Components: Nabto ICE Services (STUN/TURN) Jul 9, 19:17:35 GMT+0 - Investigating - Nabto TURN services cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 9, 19:22:35 GMT+0 - Resolved - Nabto TURN services is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>19:17:35</var> GMT+0</small><br><strong>Investigating</strong> - Nabto TURN services cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>19:22:35</var> GMT+0</small><br><strong>Resolved</strong> - Nabto TURN services is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 9 Jul 2026 19:17:35 +0000 https://status.nabto.com/incident/cmrdw2gff03uu1as53fufp8d8 https://status.nabto.com/incident/cmrdw2gff03uu1as53fufp8d8 Nabto TURN services outage Type: Incident Duration: 5 minutes Affected Components: Nabto ICE Services (STUN/TURN) Jul 5, 19:17:35 GMT+0 - Investigating - Nabto TURN services cannot be accessed at the moment. This incident was created by an automated monitoring service. Jul 5, 19:22:35 GMT+0 - Resolved - Nabto TURN services is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>19:17:35</var> GMT+0</small><br><strong>Investigating</strong> - Nabto TURN services cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>19:22:35</var> GMT+0</small><br><strong>Resolved</strong> - Nabto TURN services is now operational! This update was created by an automated monitoring service..</p> ]]> Sun, 5 Jul 2026 19:17:35 +0000 https://status.nabto.com/incident/cmr86b1770bg90rqg3qqgzooy https://status.nabto.com/incident/cmr86b1770bg90rqg3qqgzooy WebRTC signaling outage Type: Incident Duration: 5 minutes Affected Components: Nabto WebRTC Signaling SaaS Jun 15, 07:34:49 GMT+0 - Postmortem - This incident was not caused by the monitoring system detecting a service interruption, but rather monitoring data temporarily not reaching the alert system. Currently, we have no indication of any service interruptions during this incident. Jun 12, 20:05:12 GMT+0 - Investigating - Automatic tests of Nabto WebRTC Signaling failed, some features may experience problems. This incident was created by an automated monitoring service. Jun 12, 20:10:12 GMT+0 - Resolved - WebRTC signaling is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>07:34:49</var> GMT+0</small><br><strong>Postmortem</strong> - This incident was not caused by the monitoring system detecting a service interruption, but rather monitoring data temporarily not reaching the alert system. Currently, we have no indication of any service interruptions during this incident..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:05:12</var> GMT+0</small><br><strong>Investigating</strong> - Automatic tests of Nabto WebRTC Signaling failed, some features may experience problems. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:10:12</var> GMT+0</small><br><strong>Resolved</strong> - WebRTC signaling is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 12 Jun 2026 20:05:12 +0000 https://status.nabto.com/incident/cmqbcvocr006dqro4yegi9co0 https://status.nabto.com/incident/cmqbcvocr006dqro4yegi9co0 Nabto TURN services outage Type: Incident Duration: 5 minutes Affected Components: Nabto ICE Services (STUN/TURN) Jun 15, 07:34:40 GMT+0 - Postmortem - This incident was not caused by the monitoring system detecting a service interruption, but rather monitoring data temporarily not reaching the alert system. Currently, we have no indication of any service interruptions during this incident. Jun 12, 20:05:07 GMT+0 - Investigating - Nabto TURN services cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 12, 20:10:08 GMT+0 - Resolved - Nabto TURN services is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>07:34:40</var> GMT+0</small><br><strong>Postmortem</strong> - This incident was not caused by the monitoring system detecting a service interruption, but rather monitoring data temporarily not reaching the alert system. Currently, we have no indication of any service interruptions during this incident..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:05:07</var> GMT+0</small><br><strong>Investigating</strong> - Nabto TURN services cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:10:08</var> GMT+0</small><br><strong>Resolved</strong> - Nabto TURN services is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 12 Jun 2026 20:05:07 +0000 https://status.nabto.com/incident/cmqbcvl49006ipa6ju9k5180b https://status.nabto.com/incident/cmqbcvl49006ipa6ju9k5180b Nabto Edge outage Type: Incident Duration: 5 minutes Affected Components: Nabto Edge Basestation SaaS Jun 15, 07:34:30 GMT+0 - Postmortem - This incident was not caused by the monitoring system detecting a service interruption, but rather monitoring data temporarily not reaching the alert system. Currently, we have no indication of any service interruptions during this incident. Jun 12, 20:05:07 GMT+0 - Investigating - Automatic tests of Nabto Edge failed, some features may experience problems. This incident was created by an automated monitoring service. Jun 12, 20:10:07 GMT+0 - Resolved - Nabto Edge is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>07:34:30</var> GMT+0</small><br><strong>Postmortem</strong> - This incident was not caused by the monitoring system detecting a service interruption, but rather monitoring data temporarily not reaching the alert system. Currently, we have no indication of any service interruptions during this incident..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:05:07</var> GMT+0</small><br><strong>Investigating</strong> - Automatic tests of Nabto Edge failed, some features may experience problems. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:10:07</var> GMT+0</small><br><strong>Resolved</strong> - Nabto Edge is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 12 Jun 2026 20:05:07 +0000 https://status.nabto.com/incident/cmqbcvkg90067qro4m1k19wt1 https://status.nabto.com/incident/cmqbcvkg90067qro4m1k19wt1 Nabto Micro outage Type: Incident Duration: 5 minutes Affected Components: Nabto 4/uNabto Basestation SaaS Jun 15, 07:34:05 GMT+0 - Postmortem - This incident was not caused by the monitoring system detecting a service interruption, but rather monitoring data temporarily not reaching the alert system. Currently, we have no indication of any service interruptions during this incident. Jun 12, 20:05:04 GMT+0 - Investigating - Automatic tests of Nabto 4/Micro failed, some features may experience problems. This incident was created by an automated monitoring service. Jun 12, 20:10:04 GMT+0 - Resolved - Nabto Micro is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>07:34:05</var> GMT+0</small><br><strong>Postmortem</strong> - This incident was not caused by the monitoring system detecting a service interruption, but rather monitoring data temporarily not reaching the alert system. Currently, we have no indication of any service interruptions during this incident..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:05:04</var> GMT+0</small><br><strong>Investigating</strong> - Automatic tests of Nabto 4/Micro failed, some features may experience problems. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:10:04</var> GMT+0</small><br><strong>Resolved</strong> - Nabto Micro is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 12 Jun 2026 20:05:04 +0000 https://status.nabto.com/incident/cmqbcvij4005lqrox63nqol2z https://status.nabto.com/incident/cmqbcvij4005lqrox63nqol2z Nabto Edge outage Type: Incident Duration: 10 minutes Affected Components: Nabto Edge Basestation SaaS May 6, 12:52:36 GMT+0 - Postmortem - A Nabto Edge Basestation update triggered a latent failure mode under high concurrent connection load, causing affected Basestations in the EU region to restart. The update was rolled back shortly after the issue was identified. As devices reconnected en masse following the restart, backend services experienced sustained elevated load, which extended the time to fully restored normal operation. May 6, 12:42:34 GMT+0 - Investigating - Automatic tests of Nabto Edge failed, some features may experience problems. This incident was created by an automated monitoring service. May 6, 12:52:35 GMT+0 - Resolved - Nabto Edge is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 10 minutes

Affected Components:

<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>12:52:36</var> GMT+0</small><br><strong>Postmortem</strong> - A Nabto Edge Basestation update triggered a latent failure mode under high concurrent connection load, causing affected Basestations in the EU region to restart. The update was rolled back shortly after the issue was identified. As devices reconnected en masse following the restart, backend services experienced sustained elevated load, which extended the time to fully restored normal operation. .</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>12:42:34</var> GMT+0</small><br><strong>Investigating</strong> - Automatic tests of Nabto Edge failed, some features may experience problems. This incident was created by an automated monitoring service..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>12:52:35</var> GMT+0</small><br><strong>Resolved</strong> - Nabto Edge is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 6 May 2026 12:42:34 +0000 https://status.nabto.com/incident/cmou1rxph02ttzpea15t4n6ag https://status.nabto.com/incident/cmou1rxph02ttzpea15t4n6ag Nabto Edge outage Type: Incident Duration: 45 minutes Affected Components: Nabto Edge Basestation SaaS Dec 2, 07:25:02 GMT+0 - Postmortem - This was an issue related to the deployment of a new monitoring system. No Edge systems were actually impacted by this incident. Dec 1, 10:02:34 GMT+0 - Investigating - Automatic tests of Nabto Edge failed, some features may experience problems. This incident was created by an automated monitoring service. Dec 1, 10:47:34 GMT+0 - Resolved - Nabto Edge is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 45 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>07:25:02</var> GMT+0</small><br><strong>Postmortem</strong> - This was an issue related to the deployment of a new monitoring system. No Edge systems were actually impacted by this incident..</p> <p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>10:02:34</var> GMT+0</small><br><strong>Investigating</strong> - Automatic tests of Nabto Edge failed, some features may experience problems. This incident was created by an automated monitoring service..</p> <p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>10:47:34</var> GMT+0</small><br><strong>Resolved</strong> - Nabto Edge is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 1 Dec 2025 10:02:34 +0000 https://status.nabto.com/incident/cmimzda4q0jmuoyqjr29axzdn https://status.nabto.com/incident/cmimzda4q0jmuoyqjr29axzdn Nabto Micro outage Type: Incident Duration: 1 hour and 20 minutes Affected Components: Nabto 4/uNabto Basestation SaaS Nov 30, 01:42:02 GMT+0 - Resolved - Nabto Micro is now operational! This update was created by an automated monitoring service. Dec 2, 07:24:45 GMT+0 - Postmortem - This was an issue related to the deployment of a new monitoring system. No Nabto 4/Micro systems were actually impacted by this incident. Nov 30, 00:22:32 GMT+0 - Investigating - Automatic tests of Nabto 4/Micro failed, some features may experience problems. This incident was created by an automated monitoring service. Type: Incident

Duration: 1 hour and 20 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 30</var>, <var data-var='time'>01:42:02</var> GMT+0</small><br><strong>Resolved</strong> - Nabto Micro is now operational! This update was created by an automated monitoring service..</p> <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>07:24:45</var> GMT+0</small><br><strong>Postmortem</strong> - This was an issue related to the deployment of a new monitoring system. No Nabto 4/Micro systems were actually impacted by this incident..</p> <p><small>Nov <var data-var='date'> 30</var>, <var data-var='time'>00:22:32</var> GMT+0</small><br><strong>Investigating</strong> - Automatic tests of Nabto 4/Micro failed, some features may experience problems. This incident was created by an automated monitoring service..</p> ]]> Sun, 30 Nov 2025 00:22:32 +0000 https://status.nabto.com/incident/cmikz7hvn003410d3iu0zaxdk https://status.nabto.com/incident/cmikz7hvn003410d3iu0zaxdk Nabto Edge outage Type: Incident Duration: 50 minutes Affected Components: Nabto Edge Basestation SaaS Dec 2, 07:23:56 GMT+0 - Postmortem - This was an issue related to the deployment of a new monitoring system. No Edge systems were actually impacted by this incident. Nov 29, 19:02:34 GMT+0 - Investigating - Automatic tests of Nabto Edge failed, some features may experience problems. This incident was created by an automated monitoring service. Nov 29, 19:52:35 GMT+0 - Resolved - Nabto Edge is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 50 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>07:23:56</var> GMT+0</small><br><strong>Postmortem</strong> - This was an issue related to the deployment of a new monitoring system. No Edge systems were actually impacted by this incident..</p> <p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>19:02:34</var> GMT+0</small><br><strong>Investigating</strong> - Automatic tests of Nabto Edge failed, some features may experience problems. This incident was created by an automated monitoring service..</p> <p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>19:52:35</var> GMT+0</small><br><strong>Resolved</strong> - Nabto Edge is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 29 Nov 2025 19:02:34 +0000 https://status.nabto.com/incident/cmikns16704miiqjx07mtdexh https://status.nabto.com/incident/cmikns16704miiqjx07mtdexh