DNS response history for dns2.optimalweb.com

dns2.optimalweb.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 390 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 dns2.optimalweb.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

390 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.111.137.106

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 dns2.optimalweb.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:37 639232576780683689
183 ms 23.111.137.106
35 2026-08-25 12:19 639232566381512620
194 ms 23.111.137.106
34 2026-08-25 12:02 639232556111768563
197 ms 23.111.137.106
33 2026-08-25 11:45 639232545839529039
208 ms 23.111.137.106
32 2026-08-25 11:28 639232535349285207
94 ms 23.111.137.106
31 2026-08-25 11:10 639232524938080723
182 ms 23.111.137.106
30 2026-08-25 10:16 639232492740373468
180 ms 23.111.137.106
29 2026-08-25 09:59 639232482235303141
758 ms 23.111.137.106
28 2026-08-25 09:42 639232471861770303
89 ms 23.111.137.106
27 2026-08-25 09:25 639232461630217327
188 ms 23.111.137.106
26 2026-08-25 09:07 639232451282965990
232 ms 23.111.137.106
25 2026-08-25 08:50 639232440814614938
181 ms 23.111.137.106
24 2026-08-25 08:33 639232430410720425
183 ms 23.111.137.106
23 2026-08-25 08:15 639232420003096185
3 ms 23.111.137.106
22 2026-08-25 07:58 639232409467287444
183 ms 23.111.137.106
21 2026-08-25 07:40 639232399077195997
181 ms 23.111.137.106
20 2026-08-25 07:23 639232388731528337
94 ms 23.111.137.106
19 2026-08-25 07:06 639232378288598612
205 ms 23.111.137.106
18 2026-08-25 06:12 639232346196373643
182 ms 23.111.137.106
17 2026-08-25 05:55 639232336112370741
137 ms 23.111.137.106
16 2026-08-25 05:39 639232326146508970
98 ms 23.111.137.106
15 2026-08-25 05:22 639232316189381720
179 ms 23.111.137.106
14 2026-08-25 05:06 639232306217998913
179 ms 23.111.137.106
13 2026-08-25 04:49 639232296255744174
202 ms 23.111.137.106
12 2026-08-25 04:32 639232286095760789
184 ms 23.111.137.106
11 2026-08-25 04:15 639232276086186273
22 ms 23.111.137.106
10 2026-08-25 03:59 639232265900986425
2108 ms 23.111.137.106
9 2026-08-25 03:42 639232255723518075
175 ms 23.111.137.106
8 2026-08-25 03:24 639232245484452890
176 ms 23.111.137.106
7 2026-08-25 03:07 639232235157175331
180 ms 23.111.137.106
6 2026-08-25 02:14 639232203197189095
90 ms 23.111.137.106
5 2026-08-25 01:57 639232192844564298
97 ms 23.111.137.106
4 2026-08-25 01:40 639232182496008942
2010 ms 23.111.137.106
3 2026-08-25 01:22 639232172197053132
180 ms 23.111.137.106
2 2026-08-25 00:29 639232140250307418
4108 ms 23.111.137.106
1 2026-08-25 00:12 639232129927860324
192 ms 23.111.137.106