Hi everyone,
we’re running a fleet of Teltonika TRB140 LTE gateways on the Deutsche Telekom M2M network across multiple industrial sites in Europe. On June 28, 2026, Telekom had a nationwide M2M network outage. Telekom confirmed the outage was resolved the same evening, with residual congestion through June 29.
Since then, 10 out of 106 devices have been stuck offline and won’t recover on their own.
Symptom
Affected devices show:
- Operator state: “limited service”
- Modem in permanent network search — never connects
- No self-recovery, even days after the outage or power cycles
Hardware & firmware
- Device: Teltonika TRB140
- Modem: Quectel EC25-EU
Affected devices run two different modem firmware versions:
- EC25EUGAR06A05M4G_BETA1108_01.005.00.000 (Beta A05)
- EC25EUGAR06A08M4G_01.200.00.000 (A08)
No correlation between firmware version and whether a device is affected — both versions appear in offline and working devices alike.
Workaround
A SIM swap (swapping SIMs between two devices and swapping back) forces a modem re-initialization and restores connectivity. This worked at most sites.
Questions
- Is there a known bug in the Quectel EC25-EU firmware (A05/A08) related to “limited service” / loss of network registration after network events?
- What is the latest stable modem firmware for the EC25-EU module used in TRB140?
- How do you update the modem firmware on TRB140 — is this possible via the WebUI, CLI, or does it require a factory procedure?
Any insights appreciated — especially if others have seen similar behavior after carrier-side outages.
Thanks
Mike