This topic provides answers to some commonly asked questions about the billing of ApsaraMQ for MQTT.
Why are fees deducted from my account balance after I send messages by using a subscription ApsaraMQ for MQTT instance?
Your payment for a subscription ApsaraMQ for MQTT instance can be used to deduct only the fees that are incurred when you send and store messages in ApsaraMQ for MQTT.
If you use the data inbound rules or data outbound rules of ApsaraMQ for MQTT to communicate with ApsaraMQ for RocketMQ, you are charged for calling messaging API operations or using topics in ApsaraMQ for RocketMQ. These fees are billed to your ApsaraMQ for RocketMQ instance.
How am I charged fees for exporting client status events from ApsaraMQ for MQTT to ApsaraMQ for RocketMQ?
If you export client status events from ApsaraMQ for MQTT to ApsaraMQ for RocketMQ, fees are billed only to ApsaraMQ for RocketMQ.
Why are fees deducted from my account balance even though no running ApsaraMQ for MQTT instance exists in the console?
If no running ApsaraMQ for MQTT instance exists, no fees are billed to ApsaraMQ for MQTT. If fees are deducted from your account in this case, check whether the fees are for the previous calendar day. The billing cycle of pay-as-you-go ApsaraMQ for MQTT instances is 24 hours. The bill for a calendar day is generated and fees are deducted from your account on the next calendar day.