DNS response history for ns2.drshalinieyespecialist.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

389 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.106.136.36

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 ns2.drshalinieyespecialist.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
36 2026-08-27 12:04 639234286253196126
231 ms 158.106.136.36
35 2026-08-27 11:10 639234253963286387
226 ms 158.106.136.36
34 2026-08-27 10:53 639234243654907465
113 ms 158.106.136.36
33 2026-08-27 10:36 639234233269654413
229 ms 158.106.136.36
32 2026-08-27 10:19 639234222943951923
222 ms 158.106.136.36
31 2026-08-27 10:01 639234212558002823
220 ms 158.106.136.36
30 2026-08-27 09:44 639234202117531850
115 ms 158.106.136.36
29 2026-08-27 09:26 639234191649612722
118 ms 158.106.136.36
28 2026-08-27 09:09 639234181105879568
256 ms 158.106.136.36
27 2026-08-27 08:51 639234170713214496
223 ms 158.106.136.36
26 2026-08-27 08:34 639234160341037652
221 ms 158.106.136.36
25 2026-08-27 08:17 639234149799404224
110 ms 158.106.136.36
24 2026-08-27 08:00 639234139553286469
254 ms 158.106.136.36
23 2026-08-27 07:06 639234107183588293
31 ms 158.106.136.36
22 2026-08-27 06:49 639234096905435724
218 ms 158.106.136.36
21 2026-08-27 06:31 639234086579410775
7 ms 158.106.136.36
20 2026-08-27 06:14 639234076291157956
123 ms 158.106.136.36
19 2026-08-27 05:57 639234065981939454
2228 ms 158.106.136.36
18 2026-08-27 05:40 639234055548642997
224 ms 158.106.136.36
17 2026-08-27 05:22 639234045267979603
113 ms 158.106.136.36
16 2026-08-27 05:05 639234034999717463
214 ms 158.106.136.36
15 2026-08-27 04:48 639234024739225358
111 ms 158.106.136.36
14 2026-08-27 04:31 639234014311170162
215 ms 158.106.136.36
13 2026-08-27 04:14 639234003806017640
123 ms 158.106.136.36
12 2026-08-27 03:56 639233993356203030
2124 ms 158.106.136.36
11 2026-08-27 03:03 639233961301716608
116 ms 158.106.136.36
10 2026-08-27 02:45 639233950834200647
124 ms 158.106.136.36
9 2026-08-27 02:28 639233940431849026
222 ms 158.106.136.36
8 2026-08-27 02:11 639233930110596398
4037 ms 158.106.136.36
7 2026-08-27 01:53 639233919705434540
220 ms 158.106.136.36
6 2026-08-27 01:36 639233909452807845
217 ms 158.106.136.36
5 2026-08-27 01:19 639233899096420820
107 ms 158.106.136.36
4 2026-08-27 01:02 639233888707824939
221 ms 158.106.136.36
3 2026-08-27 00:45 639233878461203802
227 ms 158.106.136.36
2 2026-08-27 00:27 639233868060868209
7 ms 158.106.136.36
1 2026-08-27 00:10 639233857450922991
229 ms 158.106.136.36