Running
The broker accepts connections. If one device still fails, check that device's endpoint, credentials, and topic policy.
STATUS GUIDE
Understand your broker status
This guide explains the states shown in your RunMQTT workspace; it is not a live service-status page. Use the checks below to rule out account, usage, and connection issues.
STATUS MEANINGS
What each status means
Transient setup states normally resolve without intervention. Abnormal states need a short check before escalation.
Activating
The broker service is being activated. This normally completes within a few minutes.
Checkout required
The broker has not been activated yet. Complete checkout to create its connection endpoints.
Stopped
The broker is unavailable. Check subscription state, billing, and plan usage first.
Payment overdue
A payment needs attention. Review the invoice and payment method in billing.
Subscription ended
The subscription has ended. Review billing or choose a plan before reconnecting the broker.
Needs attention
Setup or a recent operation did not complete. Review recent account and connection changes, then retry once.
Status unavailable
The current state could not be confirmed. Refresh the page, then follow the checks below if it persists.
SELF-CHECK
Check the likely causes in order
Start with account-wide conditions, then narrow the problem to the broker or client.
- 01
Billing and subscription
Confirm the subscription is active and the payment method does not need attention.
- 02
Plan usage
Check whether connection or message usage has reached the plan limit.
- 03
Connection settings
Use the endpoint shown in RunMQTT, then verify the transport, port, credentials, and topic policy.
Still blocked after these checks?
Contact technical support with the broker name, the time of the failure, and a sanitized client error. Never include passwords or private payloads.