DNS response history for ns2.sybexlab.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

227 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.201.110.210

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.sybexlab.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
36 2026-08-26 12:09 639233424567558554
220 ms 199.201.110.210
35 2026-08-26 11:52 639233414056832719
209 ms 199.201.110.210
34 2026-08-26 11:34 639233403515141099
104 ms 199.201.110.210
33 2026-08-26 10:40 639233370841350248
237 ms 199.201.110.210
32 2026-08-26 10:22 639233360361507238
191 ms 199.201.110.210
31 2026-08-26 10:05 639233350067824371
101 ms 199.201.110.210
30 2026-08-26 09:48 639233339545274518
191 ms 199.201.110.210
29 2026-08-26 09:30 639233329214918079
249 ms 199.201.110.210
28 2026-08-26 09:13 639233318749762337
108 ms 199.201.110.210
27 2026-08-26 08:56 639233308387917838
197 ms 199.201.110.210
26 2026-08-26 08:38 639233297961740122
190 ms 199.201.110.210
25 2026-08-26 08:21 639233287487159094
202 ms 199.201.110.210
24 2026-08-26 08:04 639233276995531707
101 ms 199.201.110.210
23 2026-08-26 07:46 639233266521568229
186 ms 199.201.110.210
22 2026-08-26 07:29 639233256081047431
190 ms 199.201.110.210
21 2026-08-26 06:35 639233223620132921
187 ms 199.201.110.210
20 2026-08-26 06:17 639233213287814244
191 ms 199.201.110.210
19 2026-08-26 06:00 639233202925983161
195 ms 199.201.110.210
18 2026-08-26 05:43 639233192644780696
204 ms 199.201.110.210
17 2026-08-26 05:26 639233182401183833
193 ms 199.201.110.210
16 2026-08-26 05:09 639233172074181051
161 ms 199.201.110.210
15 2026-08-26 04:51 639233161808421455
154 ms 199.201.110.210
14 2026-08-26 04:34 639233151357344052
124 ms 199.201.110.210
13 2026-08-26 04:17 639233141034116946
96 ms 199.201.110.210
12 2026-08-26 04:00 639233130828334142
2102 ms 199.201.110.210
11 2026-08-26 03:43 639233120373450007
193 ms 199.201.110.210
10 2026-08-26 03:25 639233110066216193
110 ms 199.201.110.210
9 2026-08-26 02:32 639233078065410564
194 ms 199.201.110.210
8 2026-08-26 02:15 639233067787457832
213 ms 199.201.110.210
7 2026-08-26 01:58 639233057501801162
201 ms 199.201.110.210
6 2026-08-26 01:40 639233047089431703
183 ms 199.201.110.210
5 2026-08-26 01:23 639233036754790688
191 ms 199.201.110.210
4 2026-08-26 01:06 639233026412602472
100 ms 199.201.110.210
3 2026-08-26 00:49 639233016064066127
183 ms 199.201.110.210
2 2026-08-26 00:31 639233005922655772
199 ms 199.201.110.210
1 2026-08-26 00:14 639232995672256907
107 ms 199.201.110.210