DNS response history for n1.btmandiri.com

n1.btmandiri.com 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 36 DNS check records, 36 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 n1.btmandiri.com.
Records on Selected Date

36

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 12:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.127.136.250

Most recently resolved hosting IP on selected date

Successful Responses

36

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 n1.btmandiri.com

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
36 2026-08-25 12:40 639232576780683689
177 ms 103.127.136.250
35 2026-08-25 12:23 639232566381512620
336 ms 103.127.136.250
34 2026-08-25 12:06 639232556111768563
345 ms 103.127.136.250
33 2026-08-25 11:48 639232545839529039
169 ms 103.127.136.250
32 2026-08-25 11:31 639232535349285207
346 ms 103.127.136.250
31 2026-08-25 11:14 639232524938080723
172 ms 103.127.136.250
30 2026-08-25 10:20 639232492740373468
189 ms 103.127.136.250
29 2026-08-25 10:03 639232482235303141
347 ms 103.127.136.250
28 2026-08-25 09:45 639232471861770303
173 ms 103.127.136.250
27 2026-08-25 09:28 639232461630217327
192 ms 103.127.136.250
26 2026-08-25 09:11 639232451282965990
171 ms 103.127.136.250
25 2026-08-25 08:54 639232440814614938
181 ms 103.127.136.250
24 2026-08-25 08:36 639232430410720425
353 ms 103.127.136.250
23 2026-08-25 08:19 639232420003096185
344 ms 103.127.136.250
22 2026-08-25 08:02 639232409467287444
188 ms 103.127.136.250
21 2026-08-25 07:44 639232399077195997
182 ms 103.127.136.250
20 2026-08-25 07:27 639232388731528337
338 ms 103.127.136.250
19 2026-08-25 07:09 639232378288598612
189 ms 103.127.136.250
18 2026-08-25 06:16 639232346196373643
344 ms 103.127.136.250
17 2026-08-25 05:59 639232336112370741
221 ms 103.127.136.250
16 2026-08-25 05:42 639232326146508970
333 ms 103.127.136.250
15 2026-08-25 05:26 639232316189381720
335 ms 103.127.136.250
14 2026-08-25 05:09 639232306217998913
332 ms 103.127.136.250
13 2026-08-25 04:52 639232296255744174
169 ms 103.127.136.250
12 2026-08-25 04:36 639232286095760789
167 ms 103.127.136.250
11 2026-08-25 04:19 639232276086186273
338 ms 103.127.136.250
10 2026-08-25 04:02 639232265900986425
340 ms 103.127.136.250
9 2026-08-25 03:45 639232255723518075
167 ms 103.127.136.250
8 2026-08-25 03:28 639232245484452890
342 ms 103.127.136.250
7 2026-08-25 03:11 639232235157175331
2182 ms 103.127.136.250
6 2026-08-25 02:17 639232203197189095
168 ms 103.127.136.250
5 2026-08-25 02:00 639232192844564298
333 ms 103.127.136.250
4 2026-08-25 01:43 639232182496008942
185 ms 103.127.136.250
3 2026-08-25 01:26 639232172197053132
223 ms 103.127.136.250
2 2026-08-25 00:32 639232140250307418
336 ms 103.127.136.250
1 2026-08-25 00:15 639232129927860324
335 ms 103.127.136.250