DNS response history for ns2.jose.fitness

ns2.jose.fitness 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 32 DNS check records, 32 successful responses, 0 failed responses, and 225 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.jose.fitness.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

225 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

88.198.39.248

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 ns2.jose.fitness

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
32 2026-08-27 10:16 639234222943951923
523 ms 88.198.39.248
31 2026-08-27 09:59 639234212558002823
346 ms 88.198.39.248
30 2026-08-27 09:42 639234202117531850
74 ms 88.198.39.248
29 2026-08-27 09:24 639234191649612722
77 ms 88.198.39.248
28 2026-08-27 09:07 639234181105879568
168 ms 88.198.39.248
27 2026-08-27 08:49 639234170713214496
57 ms 88.198.39.248
26 2026-08-27 08:32 639234160341037652
118 ms 88.198.39.248
25 2026-08-27 08:15 639234149799404224
316 ms 88.198.39.248
24 2026-08-27 07:58 639234139553286469
182 ms 88.198.39.248
23 2026-08-27 07:04 639234107183588293
77 ms 88.198.39.248
22 2026-08-27 06:46 639234096905435724
183 ms 88.198.39.248
21 2026-08-27 06:29 639234086579410775
115 ms 88.198.39.248
20 2026-08-27 06:12 639234076291157956
225 ms 88.198.39.248
19 2026-08-27 05:55 639234065981939454
233 ms 88.198.39.248
18 2026-08-27 05:38 639234055548642997
64 ms 88.198.39.248
17 2026-08-27 05:20 639234045267979603
100 ms 88.198.39.248
16 2026-08-27 05:03 639234034999717463
86 ms 88.198.39.248
15 2026-08-27 04:46 639234024739225358
216 ms 88.198.39.248
14 2026-08-27 04:29 639234014311170162
437 ms 88.198.39.248
13 2026-08-27 04:11 639234003806017640
95 ms 88.198.39.248
12 2026-08-27 03:54 639233993356203030
64 ms 88.198.39.248
11 2026-08-27 03:01 639233961301716608
193 ms 88.198.39.248
10 2026-08-27 02:43 639233950834200647
64 ms 88.198.39.248
9 2026-08-27 02:26 639233940431849026
84 ms 88.198.39.248
8 2026-08-27 02:09 639233930110596398
354 ms 88.198.39.248
7 2026-08-27 01:51 639233919705434540
95 ms 88.198.39.248
6 2026-08-27 01:34 639233909452807845
53 ms 88.198.39.248
5 2026-08-27 01:17 639233899096420820
76 ms 88.198.39.248
4 2026-08-27 01:00 639233888707824939
93 ms 88.198.39.248
3 2026-08-27 00:42 639233878461203802
58 ms 88.198.39.248
2 2026-08-27 00:25 639233868060868209
2291 ms 88.198.39.248
1 2026-08-27 00:07 639233857450922991
94 ms 88.198.39.248