DNS response history for ns2.bpm.net.id

ns2.bpm.net.id is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-25. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 312 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.bpm.net.id.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

312 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.231.201.102

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.bpm.net.id

Showing DNS history for 2026-08-25 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
27 2026-08-25 09:26 639232461630217327
5 ms 103.231.201.102
26 2026-08-25 09:09 639232451282965990
8 ms 103.231.201.102
25 2026-08-25 08:51 639232440814614938
15 ms 103.231.201.102
24 2026-08-25 08:34 639232430410720425
6 ms 103.231.201.102
23 2026-08-25 08:17 639232420003096185
3 ms 103.231.201.102
22 2026-08-25 07:59 639232409467287444
40 ms 103.231.201.102
21 2026-08-25 07:42 639232399077195997
17 ms 103.231.201.102
20 2026-08-25 07:24 639232388731528337
72 ms 103.231.201.102
19 2026-08-25 07:07 639232378288598612
10 ms 103.231.201.102
18 2026-08-25 06:13 639232346196373643
2008 ms 103.231.201.102
17 2026-08-25 05:56 639232336112370741
7 ms 103.231.201.102
16 2026-08-25 05:40 639232326146508970
337 ms 103.231.201.102
15 2026-08-25 05:23 639232316189381720
326 ms 103.231.201.102
14 2026-08-25 05:07 639232306217998913
177 ms 103.231.201.102
13 2026-08-25 04:50 639232296255744174
174 ms 103.231.201.102
12 2026-08-25 04:33 639232286095760789
182 ms 103.231.201.102
11 2026-08-25 04:16 639232276086186273
162 ms 103.231.201.102
10 2026-08-25 04:00 639232265900986425
169 ms 103.231.201.102
9 2026-08-25 03:43 639232255723518075
178 ms 103.231.201.102
8 2026-08-25 03:26 639232245484452890
338 ms 103.231.201.102
7 2026-08-25 03:08 639232235157175331
366 ms 103.231.201.102
6 2026-08-25 02:15 639232203197189095
2433 ms 103.231.201.102
5 2026-08-25 01:58 639232192844564298
182 ms 103.231.201.102
4 2026-08-25 01:41 639232182496008942
343 ms 103.231.201.102
3 2026-08-25 01:23 639232172197053132
345 ms 103.231.201.102
2 2026-08-25 00:30 639232140250307418
333 ms 103.231.201.102
1 2026-08-25 00:13 639232129927860324
181 ms 103.231.201.102