DNS response history for ns2.inelmy.com

ns2.inelmy.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 29 DNS check records, 29 successful responses, 0 failed responses, and 408 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.inelmy.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

408 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.76.129.177

Most recently resolved hosting IP on selected date

Successful Responses

29

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.inelmy.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
29 2026-08-25 09:58 639232482235303141
29 ms 103.76.129.177
28 2026-08-25 09:40 639232471861770303
83 ms 103.76.129.177
27 2026-08-25 09:23 639232461630217327
9 ms 103.76.129.177
26 2026-08-25 09:06 639232451282965990
37 ms 103.76.129.177
25 2026-08-25 08:48 639232440814614938
33 ms 103.76.129.177
24 2026-08-25 08:31 639232430410720425
66 ms 103.76.129.177
23 2026-08-25 08:14 639232420003096185
92 ms 103.76.129.177
22 2026-08-25 07:56 639232409467287444
85 ms 103.76.129.177
21 2026-08-25 07:39 639232399077195997
51 ms 103.76.129.177
20 2026-08-25 07:22 639232388731528337
2103 ms 103.76.129.177
19 2026-08-25 07:04 639232378288598612
43 ms 103.76.129.177
18 2026-08-25 06:11 639232346196373643
75 ms 103.76.129.177
17 2026-08-25 05:54 639232336112370741
2066 ms 103.76.129.177
16 2026-08-25 05:37 639232326146508970
74 ms 103.76.129.177
15 2026-08-25 05:21 639232316189381720
69 ms 103.76.129.177
14 2026-08-25 05:04 639232306217998913
2069 ms 103.76.129.177
13 2026-08-25 04:47 639232296255744174
71 ms 103.76.129.177
12 2026-08-25 04:31 639232286095760789
46 ms 103.76.129.177
11 2026-08-25 04:14 639232276086186273
75 ms 103.76.129.177
10 2026-08-25 03:57 639232265900986425
77 ms 103.76.129.177
9 2026-08-25 03:40 639232255723518075
35 ms 103.76.129.177
8 2026-08-25 03:23 639232245484452890
95 ms 103.76.129.177
7 2026-08-25 03:06 639232235157175331
80 ms 103.76.129.177
6 2026-08-25 02:12 639232203197189095
106 ms 103.76.129.177
5 2026-08-25 01:55 639232192844564298
74 ms 103.76.129.177
4 2026-08-25 01:38 639232182496008942
2041 ms 103.76.129.177
3 2026-08-25 01:21 639232172197053132
40 ms 103.76.129.177
2 2026-08-25 00:27 639232140250307418
2039 ms 103.76.129.177
1 2026-08-25 00:10 639232129927860324
81 ms 103.76.129.177