Tencent Cloud EdgeOne
- Release Notes and Announcements
- Security Announcement
- Announcements
- Product Introduction
- Purchase Guide
- Billing Items
- Basic Service Fees
- Value-added Service Fees
- Instructions for overdue and refunds
- Getting Started
- Domain Service&Origin Configuration
- Domain Service
- Hosting DNS Records
- Domain Connection
- Traffic Scheduling
- HTTPS Certificate
- HTTPS Configuration
- SSL/TLS Security Configuration
- Origin Configuration
- Load Balancing
- Related References
- Origin-pull configuration
- Related References
- Site Acceleration
- Access Control
- Cache Configuration
- EdgeOne Cache Rules
- Cache Configuration
- Clear and Preheat Cach
- File Optimization
- Network Optimization
- HTTP/3(QUIC)
- QUIC SDK
- Modifying Header
- Modify the response content
- Rule Engine
- Related References
- Request and Response Actions
- DDoS & Web Protection
- DDoS Protection
- Configuration of Exclusive DDoS protection Rules
- Related References
- Web Protection
- Rate Limiting
- Bot Management
- Related References
- Related References
- Image&Video Processing
- Edge Functions
- Runtime APIs
- Streams
- Images
- Sample Functions
- Best Practices
- L4 Proxy
- Obtaining Real Client IPs
- Obtaining Real Client IPs Through Protocol V1/V2
- Data Analysis&Log Service
- Log Service
- Real-time Logs
- Data Analysis
- Alarm Service
- Version Management
- Site and Billing Management
- Site Management
- General Policy
- Terraform
- Practical Tutorial
- Automatic Warm-up/Cache Purge
- Resource Abuse/hotlinking Protection Practical
- HTTPS Related Practices
- Acceleration Optimization
- Scheduling Traffic
- Origin-pull Based On User IP/geolocation
- APK Dynamic Packaging
- Data Analysis and Alerting
- API Documentation
- Making API Requests
- Site APIs
- Acceleration Domain Management APIs
- Site Acceleration Configuration APIs
- Edge Function APIs
- Alias Domain APIs
- Security Configuration APIs
- Layer 4 Application Proxy APIs
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- DNS Record APIs
- Content Identifier APIs
- Old Version APIs
- Version Management APIs
- Common Guidelines
- FAQs
- Troubleshooting
- Tool Guide
- Speed Test Tools
- Diagnostic Tool
- Agreements
Plan Fees
Last updated: 2024-05-08 21:37:18
EdgeOne Pricing
EdgeOne offers four types of plans, including EdgeOne Personal, EdgeOne Basic, EdgeOne Standard and EdgeOne Enterprise. For details, see Comparison of EdgeOne Plans.
Type | Price | Billing mode | Billing cycle | Traffic quota | Request quota |
Personal | 4.2 USD/plan/month | Prepaid | Monthly | 50 GB | 3 million |
Basic | 57 USD/plan/month | Prepaid | Monthly | 500 GB | 20 million |
Standard | 590 USD/plan/month | Prepaid | Monthly | 3 TB | 50 million |
Enterprise | Contact us for quotation. | Pay-as-you-go | Monthly | Custom | Custom |
Calculation of consumption of the traffic provided in the prepaid plan (Personal/Basic/Standard) varies for different billing areas.
If a user actually consume 1 GB of traffic in a region, the traffic deducted from the plan quota is as follows: | | | | | | | | |
Chinese Mainland (CN) | North America (NA) | Europe (EU) | Asia Pacific Zone 1 (AP1) | Asia Pacific Zone 2 (AP2) | Asia Pacific Zone 3 (AP3) | Middle East (ME) | Africa (AA) | South America (SA) |
1 GB | 1.71 GB | 1.71 GB | 2.49 GB | 2.68 GB | 2.78 GB | 2.91 GB | 2.91 GB | 2.91 GB |
Notes
The billing area is determined by the geolocation of the EdgeOne node serving end users of the customer. For details about the mapping, see Billing Areas.
Billing Samples
A user subscribes an EdgeOne Personal plan at 00:00:00 on January 5, which contains 50 GB of traffic.
During 00:00:00 - 00:05:00 on January 5, 30 GB is consumed in the Chinese mainland. The remaining traffic quota is 50 GB - 30 x 1 GB = 20 GB;
During 00:05:00 - 00:10:00 on January 5, 10 GB is consumed in North America. The remaining traffic quota is 20 GB - 10 x 1.71 GB = 2.9 GB;
During 00:10:00 - 00:15:00 on January 5, 1 GB is consumed in Europe and Asia Pacific Zone 1 respectively. According to the calculation method, 1.71 GB and 2.49 GB of traffic is consumed in Europe and Asia Pacific Zone 1 respectively, with the total consumed traffic of 4.2 GB. But the remaining traffic in the plan is only 2.9 GB, so the consumption of traffic is calculated according to the deduction ratio:
For Europe, the traffic deducted from the plan is
2.9 x 1.71/(1.71+2.49)=1.18 GB, and the out-of-plan traffic is 1.71-1.18=0.53 GB;For Asia Pacific Zone 1, the traffic deducted from the plan is
2.9 x 2.49/(1.71+2.49)=1.72 GB, and the out-of-plan traffic is 2.49-1.72=0.77 GB.Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No