Nabto - Notice history

This issue was generated by our automated monitoring service. The cause was purely in the monitoring service, not in the TURN service, so it had no impact on service availability. We confirmed this through manual tests of the TURN service during the incident. Since the issue was isolated to the monitoring layer with no customer impact, and it occurred during the summer vacation period, we scheduled the fix for after the vacation rather than handling it as an emergency change. This is the reason for the long incident duration and for the multiple related incidents during this period.

This issue was generated by our automated monitoring service. The cause was purely in the monitoring service, not in the TURN service, so it had no impact on service availability. We confirmed this through manual tests of the TURN service during the incident. Since the issue was isolated to the monitoring layer with no customer impact, and it occurred during the summer vacation period, we scheduled the fix for after the vacation rather than handling it as an emergency change. This is the reason for the long incident duration and for the multiple related incidents during this period.

This issue was generated by our automated monitoring service. The cause was purely in the monitoring service, not in the TURN service, so it had no impact on service availability. We confirmed this through manual tests of the TURN service during the incident. Since the issue was isolated to the monitoring layer with no customer impact, and it occurred during the summer vacation period, we scheduled the fix for after the vacation rather than handling it as an emergency change. This is the reason for the long incident duration and for the multiple related incidents during this period.

This issue was generated by our automated monitoring service. The cause was purely in the monitoring service, not in the TURN service, so it had no impact on service availability. We confirmed this through manual tests of the TURN service during the incident. Since the issue was isolated to the monitoring layer with no customer impact, and it occurred during the summer vacation period, we scheduled the fix for after the vacation rather than handling it as an emergency change. This is the reason for the long incident duration and for the multiple related incidents during this period.

This issue was generated by our automated monitoring service. The cause was purely in the monitoring service, not in the TURN service, so it had no impact on service availability. We confirmed this through manual tests of the TURN service during the incident. Since the issue was isolated to the monitoring layer with no customer impact, and it occurred during the summer vacation period, we scheduled the fix for after the vacation rather than handling it as an emergency change. This is the reason for the long incident duration and for the multiple related incidents during this period.

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.

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.

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.

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.

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.