In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 04, 2025 - 08:00 CET
Scheduled - Dear User,

We are sending this communication to inform you about a planned change activity.
Customer action may be required

Work performed on: CDRX (Connected-mode Discontinuous Reception) in Sweden NB-IoT RAN

Traffic disturbance is expected due to this change.
Impact expected due to this change.

Start time of maintenance: 2025-11-04 08:00:00 CE(S)T
End time of maintenance: 2025-11-04 18:00:00 CE(S)T
Enterprise disturbance time: 10 sec
Enterprise impact:
North of Sweden, during activation the NB-IoT cell will be locket/unlocked which takes some seconds up to 10 seconds).
IoT modems with Qualcomm MDM9206 chipset are known to have a problem with cDRX enabled in NB-IoT RAN (cDRX Information Element in RRC) causing the device to crash continuously, or similar.

Examples of IoT devices having the mentioned Qualcomm chipset include Quectel BG96, Telit ME910, Simcom SIM7000, u-blox SARA R410 and R412.

There exists a remedy from Qualcomm and the IoT device vendors need to act in order to have solution in place for their customers.

Depending on the device in question, the issue can be fixed via a firmware upgrade, or via a special device specific AT-command.


Worst case scenario:
IoT modems with Qualcomm MDM9206 chipset are known to have a problem with cDRX enabled in NB-IoT RAN (cDRX Information Element in RRC) causing the device to crash continuously.

Location of works:
Impacted Country: SE North

Change reason:
Telia is to enable NB-IoT cDRX feature in Sweden for reduced power consumption of battery driven NB-IoT devices. This feature is already enabled in Telia Estonia and Telia Lithuania networks.
CDRX stands for Connected-mode Discontinuous Reception. It’s a power-saving feature used in mobile networks like LTE and 5G to reduce battery consumption in devices such as smartphones while maintaining a connection to the network.

Benefits
Improved battery life: reduced power consumption of battery driven NB-IoT devices

In case of any further problems, please log an incident in the IoT Portal.

We are sorry for any inconvenience caused.

Best regards,
Telia

Nov 4, 2025 08:00-18:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 29, 2025 - 18:00 CET
Update - We will be undergoing scheduled maintenance during this time.
Oct 29, 2025 18:00 - Nov 28, 2025 18:00 CET
Update - We will be undergoing scheduled maintenance during this time.
Oct 29, 2025 18:00 - Nov 28, 2025 18:00 CET
Scheduled - Planned work information: Managed IoT Connectivity - change in the use of public IP-pools towards Internet

We are sending this communication to inform you about a planned change activity.

We announced on the new public IP-ranges for IoT internet facing APNs on Feb 2025. The current public IP-ranges are
- 193.181.245.0/24 (older subnet)
- 193.181.246.0/24 (older subnet)
- 130.195.194.0/24 (newer subnet)
- 130.195.195.0/24 (newer subnet)

The above newer subnets are now increasingly taken into use while the older subnets shall eventually disappear from the use.

Thereby please verify that your setup supports those newer IP-ranges including
1. if you use IP filtering in your backend system
2. if you perform the IP geolocation lookup, please note that these newer IP-ranges were reallocated from U.S. to Sweden during 2024 and thereby please ensure that your related databases are up to date. Please note that even in ripe.net the newer IP-ranges are Sweden based, some lookup providers seem to indicate those being from Netherlands.

Best regards,
Telia

Oct 29, 2025 18:00 - Nov 28, 2025 18:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 20, 2025 - 09:15 CEST
Scheduled - Hello,

The 2G network in Norway will be phased out starting August 2025. This change is part of our ongoing efforts to modernize our network and improve service quality with 4G and 5G technologies.

Important dates:
August 2025: Buskerud and parts of Innlandet
September 2025: Telemark, Agder, and southern Rogaland
October 2025: Trøndelag, Møre og Romsdal, and northern regions
November 2025: Rogaland, Vestland, and Akershus
December 2025: Oslo, Drammen, Vestfold, and Østfold

Your subscriptions have already been upgraded with 4G-access. If your devices support 4G, you don’t have to do anything.
If you have devices that only support 2G, please upgrade to 4G or 5G compatible devices before the shutdown.

For device-related questions, your hardware supplier can support you best.
For more information, check: https://www.telia.no/nett/2g-utfasing/
Thanks,
Telia

Aug 20, 2025 09:15 - Jan 13, 2026 04:15 CET

About This Site

Welcome to the Status Portal for Telia IoT. Here you can monitor the availability of your service’s network and components. You can also subscribe to receive notifications about status changes via email, SMS, webhooks and RRS feeds. Select the following components for your service:

IoT Solutions.
• Telia IoT Portal
• IoT Platform
• Public REST API
• Data Ingress and Egress

IoT Connectivity.
• Managed IoT Connectivity
• Relevant Mobile network components

SPT - Smart Public Transport.
• DMWeb
• Relevant components

Smart Building.

Get more information in the Telia IoT Customer Handbook

IoT User Interfaces Operational
Telia IoT Portal Operational
IoT Solution Operational
IoT Platform Operational
IoT Solution – Data Ingress Operational
Device API (CoAP) Operational
Azure IoT Hub Operational
IoT Solution – Data Egress Operational
Push to Azure Event Hub Operational
IoT Solution – API Operational
Public REST API Operational
Managed IoT Connectivity ? Operational
Telia IoT Service Portal Operational
2G + 3G ? Operational
Sweden Operational
Norway Operational
Finland Operational
Denmark Operational
4G ? Operational
Sweden Operational
Norway Operational
Finland Operational
Denmark Operational
LTE-M ? Operational
Sweden Operational
Norway Operational
Finland Operational
Denmark Operational
NB-IoT ? Under Maintenance
Sweden Under Maintenance
Norway Under Maintenance
Finland Under Maintenance
Denmark Under Maintenance
SPT - Smart Public Transport Operational
DMWeb ? Operational
Apps Portal ? Operational
Positioning ? Operational
APC ? Operational
VoIP ? Operational
IOB ? Operational
TDM ? Operational
VCM ? Operational
Pluginsoftware API ? Operational
Journey Information ? Operational
Smart Building Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Planned Work Information - Internet Onboard Service Nov 4, 2025 10:00-12:00 CET

Scheduled - We plan to carry out a software upgrade for the Internet OnBoard service on Tuesday, November 4th, between 10:00 AM and 12:00 PM. During this time, the IOB portal will be unavailable.
Oct 21, 2025 - 16:50 CEST

Planned work information: Managed IoT Connectivity - activating CDRX - South of Sweden - CHGSE0038606 Nov 5, 2025 08:00-18:00 CET

Dear User,

We are sending this communication to inform you about a planned change activity.
Customer action may be required

Work performed on: CDRX (Connected-mode Discontinuous Reception) in Sweden NB-IoT RAN

Traffic disturbance is expected due to this change.
Impact expected due to this change.

Start time of maintenance: 2025-11-05 08:00:00 CE(S)T
End time of maintenance: 2025-11-05 18:00:00 CE(S)T
Enterprise disturbance time: 10 sec
Enterprise impact:
South of Sweden, during activation the NB-IoT cell will be locket/unlocked which takes some seconds up to 10 seconds).
IoT modems with Qualcomm MDM9206 chipset are known to have a problem with cDRX enabled in NB-IoT RAN (cDRX Information Element in RRC) causing the device to crash continuously, or similar.

Examples of IoT devices having the mentioned Qualcomm chipset include Quectel BG96, Telit ME910, Simcom SIM7000, u-blox SARA R410 and R412.

There exists a remedy from Qualcomm and the IoT device vendors need to act in order to have solution in place for their customers.

Depending on the device in question, the issue can be fixed via a firmware upgrade, or via a special device specific AT-command.


Worst case scenario:
IoT modems with Qualcomm MDM9206 chipset are known to have a problem with cDRX enabled in NB-IoT RAN (cDRX Information Element in RRC) causing the device to crash continuously.

Location of works:
Impacted Country: SE South

Change reason:
Telia is to enable NB-IoT cDRX feature in Sweden for reduced power consumption of battery driven NB-IoT devices. This feature is already enabled in Telia Estonia and Telia Lithuania networks.
CDRX stands for Connected-mode Discontinuous Reception. It’s a power-saving feature used in mobile networks like LTE and 5G to reduce battery consumption in devices such as smartphones while maintaining a connection to the network.

Benefits
Improved battery life: reduced power consumption of battery driven NB-IoT devices

In case of any further problems, please log an incident in the IoT Portal.

We are sorry for any inconvenience caused.

Best regards,
Telia

Posted on Oct 17, 2025 - 09:32 CEST

Planned work information: Managed IoT Connectivity - activating CDRX - Middle of Sweden - CHGSE0038607 Nov 6, 2025 08:00-18:00 CET

Dear User,

We are sending this communication to inform you about a planned change activity.
Customer action may be required

Work performed on: CDRX (Connected-mode Discontinuous Reception) in Sweden NB-IoT RAN

Traffic disturbance is expected due to this change.
Impact expected due to this change.

Start time of maintenance: 2025-11-06 08:00:00 CE(S)T
End time of maintenance: 2025-11-06 18:00:00 CE(S)T
Enterprise disturbance time: 10 sec
Enterprise impact:
Middle of Sweden, during activation the NB-IoT cell will be locket/unlocked which takes some seconds up to 10 seconds).
IoT modems with Qualcomm MDM9206 chipset are known to have a problem with cDRX enabled in NB-IoT RAN (cDRX Information Element in RRC) causing the device to crash continuously, or similar.

Examples of IoT devices having the mentioned Qualcomm chipset include Quectel BG96, Telit ME910, Simcom SIM7000, u-blox SARA R410 and R412.

There exists a remedy from Qualcomm and the IoT device vendors need to act in order to have solution in place for their customers.

Depending on the device in question, the issue can be fixed via a firmware upgrade, or via a special device specific AT-command.


Worst case scenario:
IoT modems with Qualcomm MDM9206 chipset are known to have a problem with cDRX enabled in NB-IoT RAN (cDRX Information Element in RRC) causing the device to crash continuously.

Location of works:
Impacted Country: SE Middle of Sweden

Change reason:
Telia is to enable NB-IoT cDRX feature in Sweden for reduced power consumption of battery driven NB-IoT devices. This feature is already enabled in Telia Estonia and Telia Lithuania networks.
CDRX stands for Connected-mode Discontinuous Reception. It’s a power-saving feature used in mobile networks like LTE and 5G to reduce battery consumption in devices such as smartphones while maintaining a connection to the network.

Benefits
Improved battery life: reduced power consumption of battery driven NB-IoT devices

In case of any further problems, please log an incident in the IoT Portal.

We are sorry for any inconvenience caused.

Best regards,
Telia

Posted on Oct 17, 2025 - 09:34 CEST
Nov 4, 2025

Unresolved incident: Planned work information: Managed IoT Connectivity - activating CDRX - Northen Sweden - CHGSE0038605.

Nov 3, 2025

No incidents reported.

Nov 2, 2025

No incidents reported.

Nov 1, 2025

No incidents reported.

Oct 31, 2025

No incidents reported.

Oct 30, 2025
Resolved - We could see azure front door stable for last 5hrs also one portal availability also 100%. No issues have been observed for last 5hrs.
Hence moving the ticket to resolved state.

Oct 30, 05:38 CET
Monitoring - Current Status :
We would like to inform you that the Azure global outage ( AFD ) issue has now been almost resolved.

The One-Portal is now running with 100% availability.

We have not received any intermittent alerts for nearly 2 hours—indicating that the issue has been effectively mitigated.

We will continue to closely monitor the Azure Portal and associated resources over the next few hours to ensure complete stability. A final update will be provided shortly once we confirm full resolution and sustained service health.

Oct 30, 01:49 CET
Identified - Current status:
Microsoft initiated the deployment of our ‘last known good’ configuration, which has now successfully completed. We are currently recovering nodes and re-routing traffic through healthy nodes.

We can see that the One-Portal health is gradually recovering. As the recovery progresses, some requests may still be routed to unhealthy nodes, which could result in intermittent failures or alerts until more nodes are fully restored.

This recovery effort involves reloading configurations and rebalancing traffic across a large volume of nodes to restore full operational scale. We expect continued improvement across affected regions.

Customer configuration changes remain temporarily blocked to prevent new deployments that could interfere with recovery. We will notify once this block has been lifted.

Full recovery and mitigation expect to happen by 23:20 UTC on 29 October 2025.

Oct 29, 23:33 CET
Update - Current Status :

Traffic rerouting and node recovery are ongoing. Microsoft expects full mitigation within the next few hours, but intermittent issues may persist.

Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted.

At this stage, Microsoft anticipate full mitigation within the next four hours as we continue to recover nodes.
This means we expect recovery to happen by 23:20 UTC on 29 October 2025.

Oct 29, 22:00 CET
Update - Current Status :
We would like to share an update regarding the ongoing Azure outage impacting the Portal and Azure Front Door (AFD) services.
Microsoft has deployed the 'last known good' configuration, and recovery is currently in progress. Node restoration and traffic routing through healthy nodes are underway, with continued improvements expected.

Please note that customer configuration changes remain temporarily blocked during this mitigation phase. Azure Portal access has been rerouted and is largely functional, though some endpoints (such as Marketplace) may still experience intermittent issues.

We continue to monitor the situation closely and will keep you informed of any significant updates.

Oct 29, 20:39 CET
Update - Azure Front Door (AFD) is experiencing service disruptions due to an unintended config change.
Microsoft has blocked all AFD changes and is rolling back to a stable state.

Oct 29, 19:26 CET
Update - We are continuing to investigate this issue.
Oct 29, 18:27 CET
Update - We are experiencing issues with https://oneportal.teliaiot.com
Oct 29, 18:18 CET
Investigating - We are currently investigating this issue.
Oct 29, 18:02 CET
Oct 29, 2025

Unresolved incident: Managed IoT Connectivity - change in the use of public IP-pools towards Internet.

Oct 28, 2025

No incidents reported.

Oct 27, 2025

No incidents reported.

Oct 26, 2025
Completed - The scheduled maintenance has been completed.
Oct 26, 21:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 26, 18:00 CET
Scheduled - Dear User, and sorry for the short notice

We are sending this communication to inform you about a planned change activity.
CUSTOMER ACTION MAY BE REQUIRED

Work performed on: PS core - offloading traffic from one of the MMEs.

Traffic disturbance can occur due to this change. But for most customers is it not expected

Start time of maintenance: 2025-10-26 18:00 CE(S)T
End time of maintenance: 2025-10-26 21:00 CE(S)T
Enterprise disturbance time: 5h 00 min

Expected behavior: During the offload, devices are automatically requested by core node to reattach and connect to another node.

Enterprise impact: Traffic offload actions are performed before all PS Core upgrades and thus if customer has not earlier been affected by such action, they should not expect to get impacted this time either. Certain NB-IoT devices do not respond well to such offloads, and may need to be restarted to regain connectivity.

Worst case scenario:
Units stop communicating and needs a restart
If your devices haven't been affected before by offloading, you should expect no impact

Location of works:
Impacted Country: DK

Change reason:
Telia is doing a planned work in PS Core and for that is offloading traffic from one of the MMEs.
Changes of parameter settings with the purpose to optimize functionality or correct node or customer problems

If you experience problems after the change, please restart your device.
In case of any further problems, please log an incident in your portal for IoT services.

We are sorry for any inconvenience caused.

Best regards

Oct 22, 15:32 CEST
Oct 25, 2025

No incidents reported.

Oct 24, 2025

No incidents reported.

Oct 23, 2025
Completed - The scheduled maintenance has been completed.
Oct 23, 00:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 22, 19:00 CEST
Scheduled - Dear User, and sorry for the short notice

We are sending this communication to inform you about a planned change activity.
CUSTOMER ACTION MAY BE REQUIRED

Work performed on: PS core - offloading traffic from one of the MMEs.

Traffic disturbance can occur due to this change. But for most customers is it not expected

Start time of maintenance: 2025-10-22 19:00 CE(S)T
End time of maintenance: 2025-10-22 24:00 CE(S)T
Enterprise disturbance time: 5h 00 min

Expected behavior: During the offload, devices are automatically requested by core node to reattach and connect to another node.

Enterprise impact: Traffic offload actions are performed before all PS Core upgrades and thus if customer has not earlier been affected by such action, they should not expect to get impacted this time either. Certain NB-IoT devices do not respond well to such offloads, and may need to be restarted to regain connectivity.

Worst case scenario:
Units stop communicating and needs a restart
If your devices haven't been affected before by offloading, you should expect no impact

Location of works:
Impacted Country: SE

Change reason:
Telia is doing a planned work in PS Core and for that is offloading traffic from one of the MMEs.
Changes of parameter settings with the purpose to optimize functionality or correct node or customer problems

If you experience problems after the change, please restart your device.
In case of any further problems, please log an incident in your portal for IoT services.

We are sorry for any inconvenience caused.

Best regards

Oct 22, 14:30 CEST
Oct 22, 2025
Oct 21, 2025
Completed - The scheduled maintenance has been completed.
Oct 21, 21:30 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 21, 14:00 CEST
Scheduled - Dear User,

We are sending this communication to inform you about a planned change activity.
CUSTOMER ACTION MAY BE REQUIRED

Work performed on:

Traffic disturbance is expected due to this change.
Impact expected due to this change.

Start time of maintenance: 2025-10-21 14:00 CE(S)T
End time of maintenance: 2025-10-21 21:30 CE(S)T
Enterprise disturbance time:
Cut over will happen 17:30 17:40 CEST
Approximately 10sec disturbance, new session request during that time may be lost

Enterprise impact:

Inter-Chassis Redundancy (ICR) switchover is scheduled to occur between 17:30 and 17:40 CET. During this operation, a brief network impact is expected
Affected services: Temporary disruption in IP network routing

Worst case scenario:
Stop in IP traffic

Rollback possible?:
yes, 5min

Location of works:
Impacted Country: SE, NO, DK, FI

Change reason:
To transition traffic from DCP2vEPG3 to DCP1vEPG3 via a manual ICR switchover

If you experience problems after the change, please log an incident in your portal for IoT services.

We are sorry for any inconvenience caused.

Best regards,
Telia

Oct 10, 16:22 CEST