DNS response history for ns2.fulywebrd.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

239 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.225.201.68

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

Showing DNS history for 2026-08-30 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-30 11:50 639236867916029489
32 ms 66.225.201.68
35 2026-08-30 11:33 639236858088772005
7 ms 66.225.201.68
34 2026-08-30 11:16 639236848158742395
227 ms 66.225.201.68
33 2026-08-30 11:00 639236838137395574
230 ms 66.225.201.68
32 2026-08-30 10:43 639236827967386881
224 ms 66.225.201.68
31 2026-08-30 10:26 639236817708615077
221 ms 66.225.201.68
30 2026-08-30 09:33 639236785770651804
11 ms 66.225.201.68
29 2026-08-30 09:16 639236775820686373
113 ms 66.225.201.68
28 2026-08-30 08:59 639236765768339082
2160 ms 66.225.201.68
27 2026-08-30 08:42 639236755602384085
225 ms 66.225.201.68
26 2026-08-30 08:25 639236745600094925
8 ms 66.225.201.68
25 2026-08-30 08:09 639236735311262753
119 ms 66.225.201.68
24 2026-08-30 07:51 639236724996745235
115 ms 66.225.201.68
23 2026-08-30 07:34 639236714839899761
110 ms 66.225.201.68
22 2026-08-30 07:18 639236704748431488
227 ms 66.225.201.68
21 2026-08-30 07:00 639236694430128550
10 ms 66.225.201.68
20 2026-08-30 06:43 639236684143292417
7 ms 66.225.201.68
19 2026-08-30 06:26 639236673972499943
3 ms 66.225.201.68
18 2026-08-30 05:33 639236642126522802
31 ms 66.225.201.68
17 2026-08-30 05:16 639236632183518198
3 ms 66.225.201.68
16 2026-08-30 05:00 639236622289312589
237 ms 66.225.201.68
15 2026-08-30 04:43 639236612490676525
218 ms 66.225.201.68
14 2026-08-30 04:27 639236602582494852
3 ms 66.225.201.68
13 2026-08-30 04:11 639236592511706469
218 ms 66.225.201.68
12 2026-08-30 03:54 639236582441006869
110 ms 66.225.201.68
11 2026-08-30 03:37 639236572478785089
218 ms 66.225.201.68
10 2026-08-30 03:20 639236562556749999
227 ms 66.225.201.68
9 2026-08-30 03:04 639236552353482281
229 ms 66.225.201.68
8 2026-08-30 02:47 639236542188881607
214 ms 66.225.201.68
7 2026-08-30 02:29 639236531885440105
110 ms 66.225.201.68
6 2026-08-30 01:36 639236499922985383
157 ms 66.225.201.68
5 2026-08-30 01:19 639236489713594431
112 ms 66.225.201.68
4 2026-08-30 01:03 639236479750443901
2121 ms 66.225.201.68
3 2026-08-30 00:46 639236469719936375
112 ms 66.225.201.68
2 2026-08-30 00:29 639236459579244885
7 ms 66.225.201.68
1 2026-08-30 00:12 639236449582837549
226 ms 66.225.201.68