DNS response history for ns2.ovrfitness.com

ns2.ovrfitness.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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 207 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.ovrfitness.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

207 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.140.156.13

Most recently resolved hosting IP on selected date

Successful Responses

28

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

Showing DNS history for 2026-08-25 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
28 2026-08-25 09:43 639232471861770303
323 ms 165.140.156.13
27 2026-08-25 09:26 639232461630217327
322 ms 165.140.156.13
26 2026-08-25 09:08 639232451282965990
4 ms 165.140.156.13
25 2026-08-25 08:51 639232440814614938
3 ms 165.140.156.13
24 2026-08-25 08:34 639232430410720425
327 ms 165.140.156.13
23 2026-08-25 08:16 639232420003096185
2231 ms 165.140.156.13
22 2026-08-25 07:59 639232409467287444
3 ms 165.140.156.13
21 2026-08-25 07:42 639232399077195997
4 ms 165.140.156.13
20 2026-08-25 07:24 639232388731528337
3 ms 165.140.156.13
19 2026-08-25 07:07 639232378288598612
4 ms 165.140.156.13
18 2026-08-25 06:13 639232346196373643
327 ms 165.140.156.13
17 2026-08-25 05:56 639232336112370741
358 ms 165.140.156.13
16 2026-08-25 05:40 639232326146508970
354 ms 165.140.156.13
15 2026-08-25 05:23 639232316189381720
326 ms 165.140.156.13
14 2026-08-25 05:07 639232306217998913
7 ms 165.140.156.13
13 2026-08-25 04:50 639232296255744174
3 ms 165.140.156.13
12 2026-08-25 04:33 639232286095760789
329 ms 165.140.156.13
11 2026-08-25 04:16 639232276086186273
4 ms 165.140.156.13
10 2026-08-25 03:59 639232265900986425
159 ms 165.140.156.13
9 2026-08-25 03:42 639232255723518075
2 ms 165.140.156.13
8 2026-08-25 03:25 639232245484452890
3 ms 165.140.156.13
7 2026-08-25 03:08 639232235157175331
4 ms 165.140.156.13
6 2026-08-25 02:15 639232203197189095
165 ms 165.140.156.13
5 2026-08-25 01:58 639232192844564298
347 ms 165.140.156.13
4 2026-08-25 01:41 639232182496008942
170 ms 165.140.156.13
3 2026-08-25 01:23 639232172197053132
3 ms 165.140.156.13
2 2026-08-25 00:30 639232140250307418
2 ms 165.140.156.13
1 2026-08-25 00:13 639232129927860324
3 ms 165.140.156.13