> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/welcome/cn/elastic-compute/networking/01-overview/04-flat-rate.md).

# 包月带宽计费

## 简介

包月带宽是最简单的计量方式：您选择一个 **Mbps 带宽上限**，并按月支付固定费用。没有按 GB 的计费项、没有 95th percentile 计算，也没有套餐。一个 EIP，一个上限，账单上一条固定金额记录。

适合吞吐量稳定且大的场景——视频源站、转码工作节点、持续运行的复制管道。您为管道付费，无需关注流量形状对成本的影响。

***

## 工作原理

创建使用包月带宽计费的 EIP 时，您选择一个 Mbps 带宽上限。该上限既是您付费的依据，也是 EIP 可推送的最大吞吐量。选择 100 Mbps，您就为当月 100 Mbps 付费——即使日均使用量只有 10 Mbps。流量在达到上限时被截断，不允许突发超出上限。

带宽大小在 Console 上以 **Mbps** 为单位设置，实际最小值为 1 Mbps。

***

## 方向不对称

入方向和出方向的上限可以独立设置——例如，媒体服务 EIP 可设置 1 Gbps 出方向和仅 10 Mbps 入方向。Console 通常显示一个对称值；API 允许分别设置。

***

## 适合选择包月带宽的场景

* **高且持续的利用率。** 如果您的 EIP 大部分时间接近峰值，包月带宽的固定价格优于任何按字节或 95 计费方案。
* **成本可预测。** 账单金额不随流量形状变化——适合需要预测账单的场景。
* **单个工作负载，单个 EIP。** 无需追求聚合收益，无需共享。

## 不适合使用包月带宽的场景

* **大部分时间空闲，偶有峰值突发。** 即使不使用也需为上限付费——[流量计费](/welcome/cn/elastic-compute/networking/01-overview/03-data-transfer.md)会更划算。
* **多个 EIP 且峰值不重叠。** 各 EIP 上限之和几乎总是高于覆盖所有 EIP 的一个[聚合 95 计费](/welcome/cn/elastic-compute/networking/01-overview/05-aggregated-95th.md)承诺量。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.console.zenlayer.com/welcome/cn/elastic-compute/networking/01-overview/04-flat-rate.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.