The uptime figures here are computed from the incident history over the last 90 days, not typed in by hand. Scheduled maintenance is not counted as downtime — counting it that way only encourages people to postpone maintenance.
Prototype: monitoring probes are not running yet. The incidents on this page come from sample data, and the uptime is computed from them. A3.17Resolved incidents stay on the page. A status page that can only ever say “all normal” tells you nothing about reliability.
Peningkatan kapasitas penyimpanan objek. Unduhan tetap dilayani dari penyimpanan cadangan selama pemeliharaan; berkas besar dapat melambat.
Indeks pencarian tumbuh melampaui ambang perencanaan sehingga latensi p95 naik dari 180 ms ke 640 ms. Indeks dibangun ulang dan latensi kembali normal.
Penyimpanan utama tidak dapat dijangkau dari satu wilayah jaringan. Unduhan dialihkan otomatis ke penyimpanan cadangan; sebagian pengguna mengalami pelambatan pada berkas besar.
Pemutakhiran master wilayah ke versi 2024.1 memicu validasi ulang seluruh dataset geospasial sekaligus. Antrean tertahan sekitar tiga jam; tidak ada hasil validasi yang salah, hanya tertunda.
The SLA a provider promises sits next to the uptime DataDiti’s probes actually measured. The measured number is the one that applies to buyers.
| API | SLA promised | Measured | p95 latency |
|---|---|---|---|
| API Harga Komoditas Real-time | 99,50% | 98,72% · Below promise | 165 ms |
| API Cuaca Titik Koordinat | 99,50% | 99,31% · Below promise | 205 ms |
| API Geocoding Alamat Indonesia | 99,50% | 99,61% | 340 ms |
| API Validasi NIK dan Domisili | 99,50% | 99,88% | 72 ms |
| API Padanan Kode Wilayah | 99,50% | 99,94% | 88 ms |