LINK Mobility incident

Unscheduled Disturbance - Swedish & Norwegian Region

Minor Resolved View vendor source →

LINK Mobility experienced a minor incident on October 20, 2026 affecting SMS api.linkmobility.com and Link InTouch Web and 1 more component, lasting 9h 9m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2026, 08:54 AM UTC
Resolved
Oct 20, 2026, 06:03 PM UTC
Duration
9h 9m
Detected by Pingoru
Oct 20, 2026, 08:54 AM UTC

Affected components

SMS api.linkmobility.comLink InTouch WebSMS MOSMS MTDLRAddressLookup

Update timeline

  1. investigating Oct 20, 2026, 08:54 AM UTC

    We are currently investigating an issue affecting message traffic. Customers may experience delays in the processing and delivery of SMS traffic, including Mobile Originated (MO), Mobile Terminated (MT), and Delivery Receipts (DLRs). Our teams are actively working with an external network provider to identify the root cause and mitigate the impact. Measures have already been implemented to improve service performance while the investigation continues. At this time, the impact is limited to desinations towards Sweden. We will provide further updates as soon as additional information becomes available. We apologize for any inconvenience and appreciate your patience while we work to resolve the issue.

  2. investigating Oct 20, 2026, 09:15 AM UTC

    We have identified additional customer impact. This issue also impacts traffic to destinations in Norway. Customers may experience delays with SMS delivery (MO, MT, and DLRs) towards both Sweden and Norway. We are actively working to mitigate the impact and will provide further updates shortly

  3. investigating Oct 20, 2026, 10:00 AM UTC

    We have identified additional customer impact. This issue also impacts AddressLookup. Customers may experience slow service performance or timeouts.. We are actively working to mitigate the impact and will provide further updates shortly

  4. investigating Oct 20, 2026, 11:19 AM UTC

    We are continuing to investigate this issue.

  5. identified Oct 20, 2026, 11:58 AM UTC

    Our network provider has identified the root cause of the issue affecting network stability and impacting a subset of our services. The issue has been traced to a cable break within the provider's network infrastructure, and repair work is currently underway. While one network connection was impacted by the cable break, connectivity remains available through a secondary connection. We have successfully mitigated the service impact, and message traffic is currently flowing normally with no significant queue build-up observed. The vast majority of messages are being processed successfully. We continue to monitor the situation closely and remain in regular contact with our network provider throughout the recovery process. We will provide further updates as additional information becomes available. We sincerely apologize for any inconvenience this incident may have caused and appreciate your patience and understanding.

  6. monitoring Oct 20, 2026, 02:03 PM UTC

    Currently, no service impact or network instability is being observed. Message traffic is flowing normally, and no significant queue build-up has been detected. We will maintain enhanced monitoring over the next 4 hours to ensure continued service stability and verify that the issue remains fully mitigated. Further updates will be provided should any changes occur.

  7. resolved Oct 20, 2026, 06:03 PM UTC

    Dear Customer / Partner, We would like to notify you that the disturbance is now closed. If you experience any further issues or delays do not hesitate to contact your local support. Thank you for your patience and understanding.