DNS response history for ns2.syedlaw.com

ns2.syedlaw.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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 198 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.syedlaw.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

198 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.162.200.168

Most recently resolved hosting IP on selected date

Successful Responses

30

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.syedlaw.com

Showing DNS history for 2026-08-26 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
30 2026-08-26 09:49 639233339545274518
226 ms 23.162.200.168
29 2026-08-26 09:32 639233329214918079
221 ms 23.162.200.168
28 2026-08-26 09:14 639233318749762337
236 ms 23.162.200.168
27 2026-08-26 08:57 639233308387917838
223 ms 23.162.200.168
26 2026-08-26 08:40 639233297961740122
135 ms 23.162.200.168
25 2026-08-26 08:22 639233287487159094
224 ms 23.162.200.168
24 2026-08-26 08:05 639233276995531707
220 ms 23.162.200.168
23 2026-08-26 07:47 639233266521568229
219 ms 23.162.200.168
22 2026-08-26 07:30 639233256081047431
223 ms 23.162.200.168
21 2026-08-26 06:36 639233223620132921
108 ms 23.162.200.168
20 2026-08-26 06:19 639233213287814244
217 ms 23.162.200.168
19 2026-08-26 06:01 639233202925983161
134 ms 23.162.200.168
18 2026-08-26 05:44 639233192644780696
220 ms 23.162.200.168
17 2026-08-26 05:27 639233182401183833
115 ms 23.162.200.168
16 2026-08-26 05:10 639233172074181051
216 ms 23.162.200.168
15 2026-08-26 04:53 639233161808421455
114 ms 23.162.200.168
14 2026-08-26 04:35 639233151357344052
221 ms 23.162.200.168
13 2026-08-26 04:18 639233141034116946
229 ms 23.162.200.168
12 2026-08-26 04:01 639233130828334142
217 ms 23.162.200.168
11 2026-08-26 03:44 639233120373450007
219 ms 23.162.200.168
10 2026-08-26 03:26 639233110066216193
216 ms 23.162.200.168
9 2026-08-26 02:33 639233078065410564
220 ms 23.162.200.168
8 2026-08-26 02:16 639233067787457832
110 ms 23.162.200.168
7 2026-08-26 01:59 639233057501801162
221 ms 23.162.200.168
6 2026-08-26 01:42 639233047089431703
226 ms 23.162.200.168
5 2026-08-26 01:24 639233036754790688
219 ms 23.162.200.168
4 2026-08-26 01:07 639233026412602472
213 ms 23.162.200.168
3 2026-08-26 00:50 639233016064066127
228 ms 23.162.200.168
2 2026-08-26 00:33 639233005922655772
226 ms 23.162.200.168
1 2026-08-26 00:16 639232995672256907
126 ms 23.162.200.168