Skip to main content
Call Eric:863-698-8266
CURRYCONTROLS.COMControls & Automation Knowledge Hub
TroubleshootingTroubleshootingTelemetryCommunicationsNetworkingSCADA

Data Plan or APN Problems

A modem that registers but has no data, or runs out mid-month: a wrong or changed APN, a capped or throttled plan, a module on the wrong plan or network, a missing static address, or polling that uses more data than planned. Sizing a plan, cutting traffic.

8 min readUpdated Sep 5, 2026Published Sep 5, 2026By Eric Sullivan

Symptom

The modem shows registered but no data session, or an address on the wrong network; data works early in the billing cycle and stops or slows later; a site is unreachable after a subscriber module or plan change; the carrier bill shows overages; several sites fail on the same day after a carrier change.

The short answer

Data Plan or APN Problems

The access point name tells the carrier which network and plan a modem should attach to, and the plan decides how much data the module may use and whether it receives a private static address. A modem with the wrong access point name registers on the radio network and never gets a usable data session, or gets a public address the utility tunnel cannot reach; a module on the wrong plan works until its cap is reached and is then throttled or suspended, often mid-month; a carrier that changes its access point names or its plan structure leaves sites that worked last year unreachable this year; and polling configured without regard to volume uses several times the data the plan allows. The access point name is verified against the carrier record and the modem configuration, the usage is read from the carrier portal and the modem counters, the plan is sized from the polling arithmetic with margin, and the traffic is reduced with report by exception, longer intervals, and fewer tags.

Key points

  • The access point name selects the network and the plan; wrong or missing, the modem registers and goes nowhere.
  • A private static address comes from the plan and the access point name; a public address means the wrong one.
  • Read the usage on the portal and the modem; a plan is sized from the polling arithmetic, not from a guess.
  • Throttling and suspension at the cap look like a link failure that begins mid-month.
  • Report by exception and sensible intervals cut data by an order of magnitude.

Possible causes and what to check

Possible causeWhat to check
Access point name wrong, missing, or with the wrong case or authenticationThe modem configuration against the carrier record; the data session state on the status page. Correct it exactly.
Carrier changed the access point name or the plan structureSeveral sites failing on one day; the carrier notice. Update every modem.
Module on the wrong plan: public instead of private, or consumer instead of the telemetry planThe address the modem received is public or on the wrong range; the carrier portal shows the plan. Move the module to the correct plan.
Data cap reached; throttled or suspendedUsage on the portal at the cap; the failure begins on the same day of the cycle each month. Reduce the traffic or increase the plan.
Polling volume far above the estimateThe modem byte counters per day against the plan; polls of many registers at short intervals, plus tunnel overhead. Reduce.
Static address not provisionedThe modem gets a dynamic address each session and the tunnel cannot find it. The plan with a static address, or a tunnel that tolerates dynamic addresses.
Tunnel or keepalive overhead dominatingBytes per day mostly from tunnel maintenance on a site that polls little; the keepalive interval and the tunnel type. Longer keepalives; a lighter tunnel.
Firmware or cloud features on the modem using dataA modem checking for updates, reporting telemetry to its vendor, or serving a remote management cloud. Disable what the utility does not use.
A device behind the modem generating trafficA camera, a laptop, or a controller with a chatty service on the site network; the modem counters by connection. Segment and remove.

Verify the access point name

  1. 1

    The record

    The access point name, the authentication, and the plan for the site, from the carrier account record the utility keeps.

  2. 2

    The modem

    The configured access point name character for character, the authentication type and credentials, and the technology and band settings.

  3. 3

    The result

    The data session state and the address the modem received: on the private range the tunnel expects, or public, or none.

  4. 4

    The carrier

    If the name is right and the session fails, the carrier confirms the module plan and the name provisioned for it.

The arithmetic

Bytes per month ≈ (polls per day × bytes per poll + keepalives per day × bytes per keepalive) × 30 × overhead

  • polls per day = the poll interval turned into a count; a 30-second poll is 2,880 per day
  • bytes per poll = request plus response including protocol headers, typically 100 to 500 bytes
  • keepalives per day = the tunnel keepalive interval turned into a count
  • overhead = the tunnel and transport overhead factor, often 1.5 to 3 for a VPN over cellular

A site polled every 30 seconds with 300-byte exchanges through a tunnel with a factor of 2 uses around 50 megabytes a month before keepalives; the same site polled every 10 seconds uses 150; a site that reports by exception with a five-minute integrity poll uses a few megabytes. Plans sized without the arithmetic run out in the third week, and the symptom is a site that fails on the twentieth of every month.

Reducing the traffic

  • Report by exception: the site sends changes with timestamps and the master polls rarely to confirm it is alive. The largest single reduction.
  • Longer intervals for values that change slowly, and short intervals only for the few that matter.
  • Fewer tags per poll: block reads of only the registers needed, not the whole map.
  • Keepalives as long as the timeouts allow.
  • Modem features that call home disabled.
  • Nothing on the site network but the controller; cameras and laptops on their own path.

Frequently asked questions

The modem shows an address and the site still cannot be reached.
The address is on the wrong network, usually a public or a carrier-private range rather than the utility private network, because the module is on the wrong plan or the access point name selects the wrong one. The tunnel expects the private address. Correct the plan and the name.
Why did five sites fail on the same day?
A carrier change: an access point name retired, a plan migrated, a network generation shut down, or an account-level suspension. The carrier notice, often sent to an address nobody reads, says which. Every modem is updated, and the notices go to a mailbox someone owns.
Is an unlimited plan the answer?
Unlimited telemetry plans are usually throttled after a threshold, and the throttled rate may be enough for polling or may not. The arithmetic and a plan with a cap above it, with usage alerts, is more predictable; an unlimited plan is a reasonable choice for a site with a camera.
Does the tunnel really double the data?
A tunnel adds headers to every packet, and small telemetry packets are mostly headers, so the overhead factor is large: often two or three times. A lighter tunnel protocol or a private carrier network that needs no tunnel reduces it; the arithmetic includes whatever is used.

Direct contact

Have a controls question?

Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.

Call Eric · 863-698-8266Contact Eric