DNS response history for ns2.indo-mim.net

ns2.indo-mim.net 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 31 DNS check records, 31 successful responses, 0 failed responses, and 319 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.indo-mim.net.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

319 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.205.142.122

Most recently resolved hosting IP on selected date

Successful Responses

31

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.indo-mim.net

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
31 2026-08-25 11:11 639232524938080723
238 ms 103.205.142.122
30 2026-08-25 10:17 639232492740373468
266 ms 103.205.142.122
29 2026-08-25 10:00 639232482235303141
240 ms 103.205.142.122
28 2026-08-25 09:42 639232471861770303
10 ms 103.205.142.122
27 2026-08-25 09:25 639232461630217327
7 ms 103.205.142.122
26 2026-08-25 09:08 639232451282965990
249 ms 103.205.142.122
25 2026-08-25 08:51 639232440814614938
11 ms 103.205.142.122
24 2026-08-25 08:33 639232430410720425
268 ms 103.205.142.122
23 2026-08-25 08:16 639232420003096185
273 ms 103.205.142.122
22 2026-08-25 07:59 639232409467287444
239 ms 103.205.142.122
21 2026-08-25 07:41 639232399077195997
129 ms 103.205.142.122
20 2026-08-25 07:24 639232388731528337
245 ms 103.205.142.122
19 2026-08-25 07:06 639232378288598612
252 ms 103.205.142.122
18 2026-08-25 06:13 639232346196373643
2146 ms 103.205.142.122
17 2026-08-25 05:56 639232336112370741
2205 ms 103.205.142.122
16 2026-08-25 05:39 639232326146508970
149 ms 103.205.142.122
15 2026-08-25 05:23 639232316189381720
3 ms 103.205.142.122
14 2026-08-25 05:06 639232306217998913
117 ms 103.205.142.122
13 2026-08-25 04:50 639232296255744174
246 ms 103.205.142.122
12 2026-08-25 04:33 639232286095760789
140 ms 103.205.142.122
11 2026-08-25 04:16 639232276086186273
237 ms 103.205.142.122
10 2026-08-25 03:59 639232265900986425
238 ms 103.205.142.122
9 2026-08-25 03:42 639232255723518075
275 ms 103.205.142.122
8 2026-08-25 03:25 639232245484452890
237 ms 103.205.142.122
7 2026-08-25 03:08 639232235157175331
182 ms 103.205.142.122
6 2026-08-25 02:15 639232203197189095
235 ms 103.205.142.122
5 2026-08-25 01:58 639232192844564298
235 ms 103.205.142.122
4 2026-08-25 01:40 639232182496008942
284 ms 103.205.142.122
3 2026-08-25 01:23 639232172197053132
146 ms 103.205.142.122
2 2026-08-25 00:30 639232140250307418
157 ms 103.205.142.122
1 2026-08-25 00:13 639232129927860324
236 ms 103.205.142.122