---
title: "How Usage Monitoring Sustains MLBB and API-PDDIKTI"
url: "https://ridwaanhall.com/blog/how-usage-monitoring-sustains-mlbb-and-api-pddikti"
markdown: "https://ridwaanhall.com/blog/how-usage-monitoring-sustains-mlbb-and-api-pddikti.md"
summary: "Two open APIs remain online through a robust threshold system and manual code-based controls, ensuring sustainable performance and reliability."
---

# How Usage Monitoring Sustains MLBB and API-PDDIKTI

> Two open APIs remain online through a robust threshold system and manual code-based controls, ensuring sustainable performance and reliability.

- By Ridwan Halim, Jul 9, 2025
- Technology & Community; 2 min read
- Tags: Threshold System, Manual Control, API Sustainability, Open Data

Following a previous announcement regarding potential API shutdowns, **mlbb.rone.dev** and **api-pddikti.rone.dev** 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:

MetricOpen (≤40%)Close (85%)Max QuotaFunction Duration≤ 40 GB-Hrs85 GB-Hrs100 GB-HrsEdge Requests≤ 400K850K1MFunction Invocations≤ 400K850K1MFast Origin Transfer≤ 4 GB8.5 GB10 GBISR Reads≤ 400K850K1MFast Data Transfer≤ 40 GB85 GB100 GBImage Optimization - Transformations≤ 2K4.25K5KEdge Middleware Invocations≤ 400K850K1MImage Optimization - Cache Writes≤ 40K85K100KImage Optimization - Cache Reads≤ 120K255K300K
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:

- [GitHub Sponsors](https://github.com/sponsors/ridwaanhall)
- [Saweria](https://saweria.co/ridwaanhall)
- [Sociabuzz](https://sociabuzz.com/ridwaanhall/support)

**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.

## Elsewhere

- This page for people: https://ridwaanhall.com/blog/how-usage-monitoring-sustains-mlbb-and-api-pddikti
- Index of every page as Markdown: [llms.txt](https://ridwaanhall.com/llms.txt)