DNS response history for ns1.inelmy.com

ns1.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-27. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 72 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 ns1.inelmy.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

72 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:06

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

28

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 ns1.inelmy.com

Showing DNS history for 2026-08-27 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
28 2026-08-27 09:06 639234181105879568
56 ms 103.76.129.177
27 2026-08-27 08:49 639234170713214496
97 ms 103.76.129.177
26 2026-08-27 08:32 639234160341037652
92 ms 103.76.129.177
25 2026-08-27 08:14 639234149799404224
79 ms 103.76.129.177
24 2026-08-27 07:57 639234139553286469
43 ms 103.76.129.177
23 2026-08-27 07:03 639234107183588293
65 ms 103.76.129.177
22 2026-08-27 06:46 639234096905435724
48 ms 103.76.129.177
21 2026-08-27 06:29 639234086579410775
77 ms 103.76.129.177
20 2026-08-27 06:12 639234076291157956
70 ms 103.76.129.177
19 2026-08-27 05:55 639234065981939454
94 ms 103.76.129.177
18 2026-08-27 05:37 639234055548642997
81 ms 103.76.129.177
17 2026-08-27 05:20 639234045267979603
104 ms 103.76.129.177
16 2026-08-27 05:03 639234034999717463
42 ms 103.76.129.177
15 2026-08-27 04:46 639234024739225358
73 ms 103.76.129.177
14 2026-08-27 04:28 639234014311170162
63 ms 103.76.129.177
13 2026-08-27 04:11 639234003806017640
41 ms 103.76.129.177
12 2026-08-27 03:53 639233993356203030
69 ms 103.76.129.177
11 2026-08-27 03:00 639233961301716608
67 ms 103.76.129.177
10 2026-08-27 02:43 639233950834200647
86 ms 103.76.129.177
9 2026-08-27 02:25 639233940431849026
85 ms 103.76.129.177
8 2026-08-27 02:08 639233930110596398
75 ms 103.76.129.177
7 2026-08-27 01:51 639233919705434540
71 ms 103.76.129.177
6 2026-08-27 01:34 639233909452807845
111 ms 103.76.129.177
5 2026-08-27 01:16 639233899096420820
74 ms 103.76.129.177
4 2026-08-27 00:59 639233888707824939
72 ms 103.76.129.177
3 2026-08-27 00:42 639233878461203802
81 ms 103.76.129.177
2 2026-08-27 00:25 639233868060868209
51 ms 103.76.129.177
1 2026-08-27 00:07 639233857450922991
53 ms 103.76.129.177