DNS response history for ns1.websyred.com

ns1.websyred.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-24. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 322 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 ns1.websyred.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

322 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.225.201.67

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns1.websyred.com

Showing DNS history for 2026-08-24 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
31 2026-08-24 13:14 639231735407682062
228 ms 66.225.201.67
30 2026-08-24 12:21 639231703815441688
238 ms 66.225.201.67
29 2026-08-24 12:05 639231693747052549
4 ms 66.225.201.67
28 2026-08-24 11:48 639231683712487276
227 ms 66.225.201.67
27 2026-08-24 11:31 639231673513573868
136 ms 66.225.201.67
26 2026-08-24 10:38 639231641791249939
232 ms 66.225.201.67
25 2026-08-24 10:22 639231631866211033
136 ms 66.225.201.67
24 2026-08-24 10:05 639231621644955316
232 ms 66.225.201.67
23 2026-08-24 09:48 639231611478799259
237 ms 66.225.201.67
22 2026-08-24 08:55 639231579923718211
20 ms 66.225.201.67
21 2026-08-24 08:38 639231569810702936
4 ms 66.225.201.67
20 2026-08-24 08:21 639231559762411619
3 ms 66.225.201.67
19 2026-08-24 08:05 639231549663595407
146 ms 66.225.201.67
18 2026-08-24 07:12 639231518076817246
3 ms 66.225.201.67
17 2026-08-24 06:56 639231508078650885
2238 ms 66.225.201.67
16 2026-08-24 06:39 639231498210697093
223 ms 66.225.201.67
15 2026-08-24 06:22 639231488109699360
219 ms 66.225.201.67
14 2026-08-24 05:30 639231456772510692
223 ms 66.225.201.67
13 2026-08-24 05:14 639231447084631185
3 ms 66.225.201.67
12 2026-08-24 04:57 639231437208519473
16 ms 66.225.201.67
11 2026-08-24 04:41 639231427209627490
2015 ms 66.225.201.67
10 2026-08-24 03:48 639231395791246644
170 ms 66.225.201.67
9 2026-08-24 03:32 639231386075551458
262 ms 66.225.201.67
8 2026-08-24 03:16 639231376208713791
9 ms 66.225.201.67
7 2026-08-24 02:59 639231366170589276
2135 ms 66.225.201.67
6 2026-08-24 02:07 639231334732159368
106 ms 66.225.201.67
5 2026-08-24 01:50 639231325035670078
36 ms 66.225.201.67
4 2026-08-24 01:34 639231315132253837
2 ms 66.225.201.67
3 2026-08-24 01:17 639231305014280808
123 ms 66.225.201.67
2 2026-08-24 00:25 639231273779380675
123 ms 66.225.201.67
1 2026-08-24 00:09 639231264180839154
233 ms 66.225.201.67