Why a device gets suspended

If a device repeatedly exceeds your plan's rate limits, its messages are dropped and violations accumulate. Enough violations lead to a temporary suspension:

Suspensions escalate on repeat: 1 hour, then 6 hours, then 24 hours. They lift automatically when the timer expires (you'll see a quota/restored event), or an admin can lift one early.

To avoid suspensions, slow the device's publish rate or upgrade your plan. See understanding rate limits.

More in Devices
Devices vs. gateways
When you need a gateway, and when a device can talk to us directly.
Device parameters (tags) explained
Tags are the named measurements a device reports — what widgets bind to.
How device online/offline status works
A device is online if we've seen a message in the last 90 seconds.
Alert thresholds (and the yellow dot)
Set a high/low range on a tag; the device dot turns yellow when a reading goes out of range.
Editing, moving, and deleting a device
Change a device's name, connection settings, gateway, or remove it.
Pause a device's reads & change its read interval
Temporarily stop polling a device (3 modes) or change how often it's read — no re-provisioning.