Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / Keuangan
Pengecekan berhasil, laporan pengguna mendekati normal, dan halaman status vendor tidak menunjukkan masalah.
Diagnosis langsung
Menunjukkan lapisan yang paling mungkin (layanan, ISP atau areamu, DNS, atau Wi-Fi-mu) dan memberi dua langkah untuk dicoba.
Tekan Jalankan tesBrowsermu menguji situs tersebut, server kami, dan dua resolver DNS publik. Kami tidak pernah menyimpan IP-mu; hanya hitungan anonim per jaringan dan wilayah.
Tidak ada laporan dalam 24 jam terakhir.
Titik mewakili seluruh negara bagian, provinsi, atau negara, bukan lokasi persis. Kami tidak pernah menyimpan alamat IP. Setiap laporan dengan tempat yang diketahui dapat muncul di peta. Diperbarui setiap menit.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Dapat dijangkau
Last checked 7 min ago. Last stored result reached it in 536 ms.
Semua normal
All Systems Operational Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| 00:15 | 0 | 0.0 | 327 ms | 0 |
| 00:30 | 0 | 0.0 | 350 ms | 0 |
| 00:45 | 0 | 0.0 | 614 ms | 0 |
| 01:00 | 0 | 0.0 | 352 ms | 0 |
| 01:15 | 0 | 0.0 | 356 ms | 0 |
| 01:30 | 0 | 0.0 | 320 ms | 0 |
| 01:45 | 0 | 0.0 | 619 ms | 0 |
| 02:00 | 0 | 0.0 | 377 ms | 0 |
| 02:15 | 0 | 0.0 | 353 ms | 0 |
| 02:30 | 0 | 0.0 | 297 ms | 0 |
| 02:45 | 0 | 0.0 | 452 ms | 0 |
| 03:00 | 0 | 0.0 | 380 ms | 0 |
| 03:15 | 0 | 0.0 | 512 ms | 0 |
| 03:30 | 0 | 0.0 | 495 ms | 0 |
| 03:45 | 0 | 0.0 | 337 ms | 0 |
| 04:00 | 0 | 0.0 | 580 ms | 0 |
| 04:15 | 0 | 0.0 | 277 ms | 0 |
| 04:30 | 0 | 0.0 | 278 ms | 0 |
| 04:45 | 0 | 0.0 | 435 ms | 0 |
| 05:00 | 0 | 0.0 | 429 ms | 0 |
| 05:15 | 0 | 0.0 | 322 ms | 0 |
| 05:30 | 0 | 0.0 | 312 ms | 0 |
| 05:45 | 0 | 0.0 | 588 ms | 0 |
| 06:00 | 0 | 0.0 | 313 ms | 0 |
| 06:15 | 0 | 0.0 | 441 ms | 0 |
| 06:30 | 0 | 0.0 | 456 ms | 0 |
| 06:45 | 0 | 0.0 | 458 ms | 0 |
| 07:00 | 0 | 0.0 | 319 ms | 0 |
| 07:15 | 0 | 0.0 | 298 ms | 0 |
| 07:30 | 0 | 0.0 | 317 ms | 0 |
| 07:45 | 0 | 0.0 | 583 ms | 0 |
| 08:00 | 0 | 0.0 | 366 ms | 0 |
| 08:15 | 0 | 0.0 | 500 ms | 0 |
| 08:30 | 0 | 0.0 | 272 ms | 0 |
| 08:45 | 0 | 0.0 | 385 ms | 0 |
| 09:00 | 0 | 0.0 | 326 ms | 0 |
| 09:15 | 0 | 0.0 | 279 ms | 0 |
| 09:30 | 0 | 0.0 | 490 ms | 0 |
| 09:45 | 0 | 0.0 | 395 ms | 0 |
| 10:00 | 0 | 0.0 | 447 ms | 0 |
| 10:15 | 0 | 0.0 | 399 ms | 0 |
| 10:30 | 0 | 0.0 | 480 ms | 0 |
| 10:45 | 0 | 0.0 | 503 ms | 0 |
| 11:00 | 0 | 0.0 | 338 ms | 0 |
| 11:15 | 0 | 0.0 | 362 ms | 0 |
| 11:30 | 0 | 0.0 | 467 ms | 0 |
| 11:45 | 0 | 0.0 | 467 ms | 0 |
| 12:00 | 0 | 0.0 | 351 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 12 days of data so far, so the 90-day numbers fill in over time.
.UA Registry Maintenance
During this scheduled system maintenance by the registry, the following services may be unavailable: Availability Checks Whois Services Domain Purchases Domain Renewals Domain Updates Services may be interrupted for up to 20 minutes during the window.
.COM/.NET Registry maintenance
During this scheduled system maintenance by the registry, the following services may be unavailable: Availability Checks Whois Services Domain Purchases Domain Renewals Domain Updates
Identity Digital Registry Maintenance
During this scheduled system maintenance by the registry, the following services may be unavailable: Availability Checks Whois Services Domain Purchases Domain Renewals Domain Updates For a list of affected TLD's, please look the registry up in the following spreadsheet: http://opensrs.help/chart
.CN, .TW Registry Maintenance
During this scheduled system maintenance by the registry, the following services may be unavailable: Availability Checks Whois Services Domain Purchases Domain Renewals Domain Updates For a list of affected TLD's, please look the registry up in the following spreadsheet: http://opensrs.help/chart
DENIC (.DE) Registry Maintenance
During a scheduled system maintenance window by OpenSRS, connectivity to the Denic registry will be temporarily disrupted for the TLD listed below: .de During the maintenance window, you may experience temporary interruption to the following services: • Availability checks • Whois service • Domain purchases • Domain renewals • Domain updates • Domain Transfer This maintenance may also result in…
PIR (.ORG) Registry Maintenance
During this scheduled system maintenance by the registry, the following services may be unavailable: Availability Checks Whois Services Domain Purchases Domain Renewals Domain Updates For a list of affected TLD's, please look the registry up in the following spreadsheet: http://opensrs.help/chart
Nominet Registry Maintenance
During this scheduled system maintenance by the registry, the following services may be unavailable: Availability Checks Whois Services Domain Purchases Domain Renewals Domain Updates For a list of affected TLD's, please look the registry up in the following spreadsheet: http://opensrs.help/chart
Pemeliharaan terencana bukan gangguan. Waktu dan kata-katanya berasal dari vendor. Outage Weather →
Belum ada catatan gangguan untuk Opensrs. Gangguan selama 10 menit atau lebih mendapat halaman sendiri di sini.
Satu laporan per layanan setiap 10 menit dari jaringan ini. Tanpa akun.
Dapatkan email saat Opensrs down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan Opensrs ke Slack, Discord, atau webhook — gratis.
Opensrs terdaftar di kategori Keuangan kami dan dicek di opensrs.com.
Opensrs menerbitkan halaman status resmi di opensrsstatus.com; jika dapat kami baca, tingkat insidennya ikut diperhitungkan dalam status yang ditampilkan di sini.
Masalah umum pada layanan Keuangan: masalah login dan verifikasi dua langkah, pembayaran atau transfer gagal, dan galat aplikasi.
Uptime terukur dari pengecekan kami: 100% selama 12 hari pengecekan. Tidak ada insiden publik yang tercatat sejak pemantauan dimulai 12 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 429 ms, rentang 231–802 ms dari 181 pengecekan yang berhasil.
Pengecekan berhasil, laporan pengguna mendekati normal, dan halaman status vendor tidak menunjukkan masalah.
Kami belum mencatat insiden publik Opensrs sejak pemantauan dimulai 12 hari lalu.
Dari pengecekan kami sendiri: 100% selama 12 hari pengecekan.
Rata-rata 429 ms selama 24 jam terakhir (231–802 ms).
Ya, di https://www.opensrsstatus.com.
Biasanya masalahnya lokal: coba browser lain atau aplikasinya, beralih antara Wi-Fi dan data seluler, lalu hapus cache. Untuk layanan Keuangan, perhatikan masalah login dan verifikasi dua langkah, pembayaran atau transfer gagal, dan galat aplikasi. Jika banyak orang melaporkan Opensrs di sini secara bersamaan, masalahnya ada di pihak Opensrs.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Community comments
Share what you are seeing with Opensrs. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.