DNS response history for ns2.neofitnessgym.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

47 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.46.65.247

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

Showing DNS history for 2026-08-27 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-27 10:31 639234233269654413
59 ms 78.46.65.247
32 2026-08-27 10:14 639234222943951923
72 ms 78.46.65.247
31 2026-08-27 09:56 639234212558002823
26 ms 78.46.65.247
30 2026-08-27 09:39 639234202117531850
47 ms 78.46.65.247
29 2026-08-27 09:21 639234191649612722
58 ms 78.46.65.247
28 2026-08-27 09:04 639234181105879568
59 ms 78.46.65.247
27 2026-08-27 08:47 639234170713214496
60 ms 78.46.65.247
26 2026-08-27 08:29 639234160341037652
36 ms 78.46.65.247
25 2026-08-27 08:12 639234149799404224
70 ms 78.46.65.247
24 2026-08-27 07:55 639234139553286469
52 ms 78.46.65.247
23 2026-08-27 07:01 639234107183588293
61 ms 78.46.65.247
22 2026-08-27 06:44 639234096905435724
20 ms 78.46.65.247
21 2026-08-27 06:26 639234086579410775
20 ms 78.46.65.247
20 2026-08-27 06:09 639234076291157956
43 ms 78.46.65.247
19 2026-08-27 05:52 639234065981939454
15 ms 78.46.65.247
18 2026-08-27 05:35 639234055548642997
67 ms 78.46.65.247
17 2026-08-27 05:18 639234045267979603
56 ms 78.46.65.247
16 2026-08-27 05:00 639234034999717463
33 ms 78.46.65.247
15 2026-08-27 04:43 639234024739225358
31 ms 78.46.65.247
14 2026-08-27 04:26 639234014311170162
56 ms 78.46.65.247
13 2026-08-27 04:08 639234003806017640
22 ms 78.46.65.247
12 2026-08-27 03:51 639233993356203030
86 ms 78.46.65.247
11 2026-08-27 02:58 639233961301716608
51 ms 78.46.65.247
10 2026-08-27 02:40 639233950834200647
61 ms 78.46.65.247
9 2026-08-27 02:23 639233940431849026
45 ms 78.46.65.247
8 2026-08-27 02:06 639233930110596398
12 ms 78.46.65.247
7 2026-08-27 01:48 639233919705434540
29 ms 78.46.65.247
6 2026-08-27 01:31 639233909452807845
54 ms 78.46.65.247
5 2026-08-27 01:14 639233899096420820
38 ms 78.46.65.247
4 2026-08-27 00:57 639233888707824939
58 ms 78.46.65.247
3 2026-08-27 00:40 639233878461203802
65 ms 78.46.65.247
2 2026-08-27 00:22 639233868060868209
53 ms 78.46.65.247
1 2026-08-27 00:04 639233857450922991
34 ms 78.46.65.247