<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.nabto.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.nabto.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.nabto.com/history.atom"/>
  <title>Nabto Status - Incident history</title>
  <updated>2026-07-09T19:17:35.785+00:00</updated>
  <author>
    <name>Nabto</name>
  </author>
  
<entry>
  <id>tag:status.nabto.com,2005:Incident/cmrdw2gff03uu1as53fufp8d8</id>
  <published>2026-07-09T19:17:35.785+00:00</published>
  <updated>2026-07-09T19:17:35.794+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmrdw2gff03uu1as53fufp8d8"/>
  <title>Nabto TURN services outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> Nabto ICE Services (STUN/TURN)</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nabto.com,2005:Incident/cmr86b1770bg90rqg3qqgzooy</id>
  <published>2026-07-05T19:17:35.057+00:00</published>
  <updated>2026-07-05T19:17:35.070+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmr86b1770bg90rqg3qqgzooy"/>
  <title>Nabto TURN services outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> Nabto ICE Services (STUN/TURN)</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nabto.com,2005:Incident/cmqbcvocr006dqro4yegi9co0</id>
  <published>2026-06-12T20:05:12.075+00:00</published>
  <updated>2026-06-15T07:34:49.177+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmqbcvocr006dqro4yegi9co0"/>
  <title>WebRTC signaling outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> Nabto WebRTC Signaling SaaS</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nabto.com,2005:Incident/cmqbcvl49006ipa6ju9k5180b</id>
  <published>2026-06-12T20:05:07.880+00:00</published>
  <updated>2026-06-15T07:34:40.409+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmqbcvl49006ipa6ju9k5180b"/>
  <title>Nabto TURN services outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> Nabto ICE Services (STUN/TURN)</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nabto.com,2005:Incident/cmqbcvkg90067qro4m1k19wt1</id>
  <published>2026-06-12T20:05:07.017+00:00</published>
  <updated>2026-06-15T07:34:30.593+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmqbcvkg90067qro4m1k19wt1"/>
  <title>Nabto Edge outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> Nabto Edge Basestation SaaS</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nabto.com,2005:Incident/cmqbcvij4005lqrox63nqol2z</id>
  <published>2026-06-12T20:05:04.527+00:00</published>
  <updated>2026-06-15T07:34:05.377+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmqbcvij4005lqrox63nqol2z"/>
  <title>Nabto Micro outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> Nabto 4/uNabto Basestation SaaS</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nabto.com,2005:Incident/cmou1rxph02ttzpea15t4n6ag</id>
  <published>2026-05-06T12:42:34.468+00:00</published>
  <updated>2026-05-06T12:52:36.373+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmou1rxph02ttzpea15t4n6ag"/>
  <title>Nabto Edge outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> Nabto Edge Basestation SaaS</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nabto.com,2005:Incident/cmimzda4q0jmuoyqjr29axzdn</id>
  <published>2025-12-01T10:02:34.266+00:00</published>
  <updated>2025-12-02T07:25:02.038+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmimzda4q0jmuoyqjr29axzdn"/>
  <title>Nabto Edge outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 45 minutes</p>
    <p><strong>Affected Components:</strong> Nabto Edge Basestation SaaS</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nabto.com,2005:Incident/cmikz7hvn003410d3iu0zaxdk</id>
  <published>2025-11-30T00:22:32.034+00:00</published>
  <updated>2025-11-30T01:42:02.893+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmikz7hvn003410d3iu0zaxdk"/>
  <title>Nabto Micro outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 20 minutes</p>
    <p><strong>Affected Components:</strong> Nabto 4/uNabto Basestation SaaS</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.nabto.com,2005:Incident/cmikns16704miiqjx07mtdexh</id>
  <published>2025-11-29T19:02:34.765+00:00</published>
  <updated>2025-12-02T07:23:56.925+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.nabto.com/incident/cmikns16704miiqjx07mtdexh"/>
  <title>Nabto Edge outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> Nabto Edge Basestation SaaS</p>
    <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>

        ]]>
  </content>
</entry>

</feed>