DNS response history for ns1.wiledbytes.com

ns1.wiledbytes.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 33 DNS check records, 33 successful responses, 0 failed responses, and 302 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.wiledbytes.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

302 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.140.70.174

Most recently resolved hosting IP on selected date

Successful Responses

33

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.wiledbytes.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
33 2026-08-26 10:40 639233370841350248
254 ms 165.140.70.174
32 2026-08-26 10:23 639233360361507238
233 ms 165.140.70.174
31 2026-08-26 10:05 639233350067824371
151 ms 165.140.70.174
30 2026-08-26 09:48 639233339545274518
237 ms 165.140.70.174
29 2026-08-26 09:31 639233329214918079
238 ms 165.140.70.174
28 2026-08-26 09:13 639233318749762337
2136 ms 165.140.70.174
27 2026-08-26 08:56 639233308387917838
243 ms 165.140.70.174
26 2026-08-26 08:39 639233297961740122
231 ms 165.140.70.174
25 2026-08-26 08:21 639233287487159094
232 ms 165.140.70.174
24 2026-08-26 08:04 639233276995531707
248 ms 165.140.70.174
23 2026-08-26 07:46 639233266521568229
126 ms 165.140.70.174
22 2026-08-26 07:29 639233256081047431
242 ms 165.140.70.174
21 2026-08-26 06:35 639233223620132921
140 ms 165.140.70.174
20 2026-08-26 06:18 639233213287814244
122 ms 165.140.70.174
19 2026-08-26 06:00 639233202925983161
137 ms 165.140.70.174
18 2026-08-26 05:43 639233192644780696
147 ms 165.140.70.174
17 2026-08-26 05:26 639233182401183833
118 ms 165.140.70.174
16 2026-08-26 05:09 639233172074181051
235 ms 165.140.70.174
15 2026-08-26 04:52 639233161808421455
235 ms 165.140.70.174
14 2026-08-26 04:34 639233151357344052
232 ms 165.140.70.174
13 2026-08-26 04:17 639233141034116946
139 ms 165.140.70.174
12 2026-08-26 04:00 639233130828334142
215 ms 165.140.70.174
11 2026-08-26 03:43 639233120373450007
117 ms 165.140.70.174
10 2026-08-26 03:25 639233110066216193
2120 ms 165.140.70.174
9 2026-08-26 02:32 639233078065410564
126 ms 165.140.70.174
8 2026-08-26 02:15 639233067787457832
233 ms 165.140.70.174
7 2026-08-26 01:58 639233057501801162
234 ms 165.140.70.174
6 2026-08-26 01:40 639233047089431703
8 ms 165.140.70.174
5 2026-08-26 01:23 639233036754790688
231 ms 165.140.70.174
4 2026-08-26 01:06 639233026412602472
118 ms 165.140.70.174
3 2026-08-26 00:49 639233016064066127
132 ms 165.140.70.174
2 2026-08-26 00:32 639233005922655772
237 ms 165.140.70.174
1 2026-08-26 00:15 639232995672256907
125 ms 165.140.70.174