DNS response history for ns3.cryptpay3.com

ns3.cryptpay3.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 34 DNS check records, 34 successful responses, 0 failed responses, and 334 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 ns3.cryptpay3.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

334 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

205.251.199.105

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns3.cryptpay3.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
34 2026-08-26 11:26 639233403515141099
27 ms 205.251.199.105
33 2026-08-26 10:32 639233370841350248
32 ms 205.251.199.105
32 2026-08-26 10:14 639233360361507238
41 ms 205.251.199.105
31 2026-08-26 09:57 639233350067824371
24 ms 205.251.199.105
30 2026-08-26 09:40 639233339545274518
16 ms 205.251.199.105
29 2026-08-26 09:22 639233329214918079
19 ms 205.251.199.105
28 2026-08-26 09:05 639233318749762337
62 ms 205.251.199.105
27 2026-08-26 08:48 639233308387917838
36 ms 205.251.199.105
26 2026-08-26 08:30 639233297961740122
31 ms 205.251.199.105
25 2026-08-26 08:13 639233287487159094
24 ms 205.251.199.105
24 2026-08-26 07:55 639233276995531707
47 ms 205.251.199.105
23 2026-08-26 07:38 639233266521568229
2067 ms 205.251.199.105
22 2026-08-26 07:21 639233256081047431
55 ms 205.251.199.105
21 2026-08-26 06:26 639233223620132921
42 ms 205.251.199.105
20 2026-08-26 06:09 639233213287814244
2056 ms 205.251.199.105
19 2026-08-26 05:52 639233202925983161
25 ms 205.251.199.105
18 2026-08-26 05:35 639233192644780696
23 ms 205.251.199.105
17 2026-08-26 05:18 639233182401183833
4058 ms 205.251.199.105
16 2026-08-26 05:01 639233172074181051
31 ms 205.251.199.105
15 2026-08-26 04:44 639233161808421455
2051 ms 205.251.199.105
14 2026-08-26 04:26 639233151357344052
62 ms 205.251.199.105
13 2026-08-26 04:09 639233141034116946
40 ms 205.251.199.105
12 2026-08-26 03:52 639233130828334142
41 ms 205.251.199.105
11 2026-08-26 03:34 639233120373450007
13 ms 205.251.199.105
10 2026-08-26 03:17 639233110066216193
19 ms 205.251.199.105
9 2026-08-26 02:24 639233078065410564
77 ms 205.251.199.105
8 2026-08-26 02:07 639233067787457832
34 ms 205.251.199.105
7 2026-08-26 01:50 639233057501801162
19 ms 205.251.199.105
6 2026-08-26 01:32 639233047089431703
40 ms 205.251.199.105
5 2026-08-26 01:15 639233036754790688
38 ms 205.251.199.105
4 2026-08-26 00:58 639233026412602472
27 ms 205.251.199.105
3 2026-08-26 00:41 639233016064066127
31 ms 205.251.199.105
2 2026-08-26 00:24 639233005922655772
99 ms 205.251.199.105
1 2026-08-26 00:07 639232995672256907
32 ms 205.251.199.105