DNS response history for ns2.inmode.com

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

39

Historical checks stored for this nameserver on selected date

Average Latency

206 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.27.42.207

Most recently resolved hosting IP on selected date

Successful Responses

39

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.inmode.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
39 2026-08-25 13:30 639232608016476376
246 ms 69.27.42.207
38 2026-08-25 13:13 639232597643611557
245 ms 69.27.42.207
37 2026-08-25 12:56 639232587225721862
247 ms 69.27.42.207
36 2026-08-25 12:38 639232576780683689
242 ms 69.27.42.207
35 2026-08-25 12:21 639232566381512620
127 ms 69.27.42.207
34 2026-08-25 12:04 639232556111768563
250 ms 69.27.42.207
33 2026-08-25 11:47 639232545839529039
121 ms 69.27.42.207
32 2026-08-25 11:29 639232535349285207
127 ms 69.27.42.207
31 2026-08-25 11:12 639232524938080723
250 ms 69.27.42.207
30 2026-08-25 10:18 639232492740373468
238 ms 69.27.42.207
29 2026-08-25 10:01 639232482235303141
121 ms 69.27.42.207
28 2026-08-25 09:43 639232471861770303
235 ms 69.27.42.207
27 2026-08-25 09:26 639232461630217327
253 ms 69.27.42.207
26 2026-08-25 09:09 639232451282965990
131 ms 69.27.42.207
25 2026-08-25 08:52 639232440814614938
239 ms 69.27.42.207
24 2026-08-25 08:34 639232430410720425
254 ms 69.27.42.207
23 2026-08-25 08:17 639232420003096185
139 ms 69.27.42.207
22 2026-08-25 08:00 639232409467287444
248 ms 69.27.42.207
21 2026-08-25 07:42 639232399077195997
146 ms 69.27.42.207
20 2026-08-25 07:25 639232388731528337
126 ms 69.27.42.207
19 2026-08-25 07:07 639232378288598612
266 ms 69.27.42.207
18 2026-08-25 06:14 639232346196373643
244 ms 69.27.42.207
17 2026-08-25 05:57 639232336112370741
129 ms 69.27.42.207
16 2026-08-25 05:40 639232326146508970
249 ms 69.27.42.207
15 2026-08-25 05:24 639232316189381720
235 ms 69.27.42.207
14 2026-08-25 05:07 639232306217998913
239 ms 69.27.42.207
13 2026-08-25 04:50 639232296255744174
244 ms 69.27.42.207
12 2026-08-25 04:34 639232286095760789
235 ms 69.27.42.207
11 2026-08-25 04:17 639232276086186273
140 ms 69.27.42.207
10 2026-08-25 04:00 639232265900986425
240 ms 69.27.42.207
9 2026-08-25 03:43 639232255723518075
254 ms 69.27.42.207
8 2026-08-25 03:26 639232245484452890
234 ms 69.27.42.207
7 2026-08-25 03:09 639232235157175331
241 ms 69.27.42.207
6 2026-08-25 02:16 639232203197189095
251 ms 69.27.42.207
5 2026-08-25 01:58 639232192844564298
136 ms 69.27.42.207
4 2026-08-25 01:41 639232182496008942
125 ms 69.27.42.207
3 2026-08-25 01:24 639232172197053132
235 ms 69.27.42.207
2 2026-08-25 00:30 639232140250307418
240 ms 69.27.42.207
1 2026-08-25 00:14 639232129927860324
119 ms 69.27.42.207