DNS response history for ns2.purefitnessremedy.com

ns2.purefitnessremedy.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-29. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 181 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.purefitnessremedy.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

181 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 11:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

213.111.149.246

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 ns2.purefitnessremedy.com

Showing DNS history for 2026-08-29 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-29 11:32 639235997602806960
43 ms 213.111.149.246
32 2026-08-29 11:15 639235987487833458
4 ms 213.111.149.246
31 2026-08-29 10:58 639235977211002296
27 ms 213.111.149.246
30 2026-08-29 10:41 639235966864596836
3 ms 213.111.149.246
29 2026-08-29 10:24 639235956590882003
79 ms 213.111.149.246
28 2026-08-29 09:30 639235924465736791
3 ms 213.111.149.246
27 2026-08-29 09:13 639235914430611197
3 ms 213.111.149.246
26 2026-08-29 08:56 639235904343784853
67 ms 213.111.149.246
25 2026-08-29 08:40 639235894201078068
79 ms 213.111.149.246
24 2026-08-29 08:23 639235884233447452
72 ms 213.111.149.246
23 2026-08-29 08:06 639235874142207309
63 ms 213.111.149.246
22 2026-08-29 07:49 639235863974652466
27 ms 213.111.149.246
21 2026-08-29 07:32 639235853716243436
77 ms 213.111.149.246
20 2026-08-29 07:15 639235843614494759
37 ms 213.111.149.246
19 2026-08-29 06:58 639235833401459551
103 ms 213.111.149.246
18 2026-08-29 06:41 639235823220464528
100 ms 213.111.149.246
17 2026-08-29 06:24 639235812997510905
4076 ms 213.111.149.246
16 2026-08-29 05:31 639235781101962521
23 ms 213.111.149.246
15 2026-08-29 05:15 639235771207673260
79 ms 213.111.149.246
14 2026-08-29 04:58 639235761047429642
77 ms 213.111.149.246
13 2026-08-29 04:41 639235750964347246
96 ms 213.111.149.246
12 2026-08-29 04:24 639235740923490874
38 ms 213.111.149.246
11 2026-08-29 04:07 639235730842894399
91 ms 213.111.149.246
10 2026-08-29 03:51 639235720760084717
68 ms 213.111.149.246
9 2026-08-29 03:34 639235710843666743
85 ms 213.111.149.246
8 2026-08-29 03:17 639235700733510561
66 ms 213.111.149.246
7 2026-08-29 03:00 639235690509906192
77 ms 213.111.149.246
6 2026-08-29 02:43 639235680156673501
86 ms 213.111.149.246
5 2026-08-29 02:25 639235669720606443
71 ms 213.111.149.246
4 2026-08-29 01:32 639235637451417084
114 ms 213.111.149.246
3 2026-08-29 01:15 639235627307383453
49 ms 213.111.149.246
2 2026-08-29 00:57 639235616906386856
14 ms 213.111.149.246
1 2026-08-29 00:40 639235606582912691
67 ms 213.111.149.246