How Usage Monitoring Sustains MLBB-Stats and API-PDDIKTI


Following a previous announcement regarding potential API shutdowns, mlbb-stats.ridwaanhall.com and api-pddikti.ridwaanhall.com will be available again on 28 August 2025, or sooner if we receive support with a minimum of 25 USD.
Each API monitors core resource usage—Function Duration, Edge Requests, Image Optimization, and more. If usage approaches a defined limit (e.g., 85% of quota), the service is flagged for temporary deactivation. Unlike automated systems, activation and deactivation are manually managed via backend logic, providing flexibility while maintaining stability.
This manual switching process does not disrupt active requests or user experience. It allows the APIs to remain responsive under heavy load, while administrators monitor usage patterns and adjust service availability as needed.
Below is the current usage snapshot used to monitor thresholds:
Metric | Open (≤40%) | Close (85%) | Max Quota |
---|---|---|---|
Function Duration | ≤ 40 GB-Hrs | 85 GB-Hrs | 100 GB-Hrs |
Edge Requests | ≤ 400K | 850K | 1M |
Function Invocations | ≤ 400K | 850K | 1M |
Fast Origin Transfer | ≤ 4 GB | 8.5 GB | 10 GB |
ISR Reads | ≤ 400K | 850K | 1M |
Fast Data Transfer | ≤ 40 GB | 85 GB | 100 GB |
Image Optimization - Transformations | ≤ 2K | 4.25K | 5K |
Edge Middleware Invocations | ≤ 400K | 850K | 1M |
Image Optimization - Cache Writes | ≤ 40K | 85K | 100K |
Image Optimization - Cache Reads | ≤ 120K | 255K | 300K |
Explanation of the table columns:
- Metric: The specific resource or operation being monitored (e.g., Function Duration, Edge Requests).
- Open (≤40%): After a metric reaches the Close threshold (85%) and the API is deactivated, it will only be reactivated (Open) once usage drops back to 40% or below. This ensures the API remains stable and prevents rapid toggling.
- Close (85%): Usage threshold at which the API is flagged for potential temporary deactivation to prevent overuse.
- Max Quota: The absolute maximum allowed usage for the metric within the billing period.
Thresholds are set at 85% of the maximum quota to ensure healthy operation. As long as usage remains below these limits, the APIs remain online and stable. APIs are considered fully accessible when usage is at or below 40% of the quota.
If you find these APIs useful and would like to support ongoing development and maintenance, you can support me via:
Suggestion: To save API usage, you can use caching in your application or browser. With caching, reloading the page will not always fetch data directly from the API, which helps reduce your API usage limits.