DNS response history for ns1.fylepyle.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

208 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.6.171.104

Most recently resolved hosting IP on selected date

Successful Responses

32

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.fylepyle.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
32 2026-08-26 10:22 639233360361507238
296 ms 50.6.171.104
31 2026-08-26 10:05 639233350067824371
198 ms 50.6.171.104
30 2026-08-26 09:47 639233339545274518
218 ms 50.6.171.104
29 2026-08-26 09:30 639233329214918079
7 ms 50.6.171.104
28 2026-08-26 09:13 639233318749762337
209 ms 50.6.171.104
27 2026-08-26 08:55 639233308387917838
123 ms 50.6.171.104
26 2026-08-26 08:38 639233297961740122
202 ms 50.6.171.104
25 2026-08-26 08:20 639233287487159094
103 ms 50.6.171.104
24 2026-08-26 08:03 639233276995531707
106 ms 50.6.171.104
23 2026-08-26 07:45 639233266521568229
2109 ms 50.6.171.104
22 2026-08-26 07:28 639233256081047431
83 ms 50.6.171.104
21 2026-08-26 06:34 639233223620132921
204 ms 50.6.171.104
20 2026-08-26 06:17 639233213287814244
152 ms 50.6.171.104
19 2026-08-26 05:59 639233202925983161
197 ms 50.6.171.104
18 2026-08-26 05:42 639233192644780696
197 ms 50.6.171.104
17 2026-08-26 05:25 639233182401183833
196 ms 50.6.171.104
16 2026-08-26 05:08 639233172074181051
195 ms 50.6.171.104
15 2026-08-26 04:51 639233161808421455
116 ms 50.6.171.104
14 2026-08-26 04:34 639233151357344052
197 ms 50.6.171.104
13 2026-08-26 04:16 639233141034116946
104 ms 50.6.171.104
12 2026-08-26 03:59 639233130828334142
200 ms 50.6.171.104
11 2026-08-26 03:42 639233120373450007
198 ms 50.6.171.104
10 2026-08-26 03:25 639233110066216193
123 ms 50.6.171.104
9 2026-08-26 02:31 639233078065410564
10 ms 50.6.171.104
8 2026-08-26 02:14 639233067787457832
4 ms 50.6.171.104
7 2026-08-26 01:57 639233057501801162
4 ms 50.6.171.104
6 2026-08-26 01:40 639233047089431703
198 ms 50.6.171.104
5 2026-08-26 01:23 639233036754790688
197 ms 50.6.171.104
4 2026-08-26 01:05 639233026412602472
7 ms 50.6.171.104
3 2026-08-26 00:48 639233016064066127
210 ms 50.6.171.104
2 2026-08-26 00:31 639233005922655772
198 ms 50.6.171.104
1 2026-08-26 00:14 639232995672256907
106 ms 50.6.171.104