DNS response history for ns2.petsmonitorapp.com

ns2.petsmonitorapp.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 38 DNS check records, 38 successful responses, 0 failed responses, and 286 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.petsmonitorapp.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

286 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.92.25.70

Most recently resolved hosting IP on selected date

Successful Responses

38

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.petsmonitorapp.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
38 2026-08-25 13:10 639232597643611557
109 ms 66.92.25.70
37 2026-08-25 12:52 639232587225721862
223 ms 66.92.25.70
36 2026-08-25 12:35 639232576780683689
231 ms 66.92.25.70
35 2026-08-25 12:17 639232566381512620
224 ms 66.92.25.70
34 2026-08-25 12:00 639232556111768563
220 ms 66.92.25.70
33 2026-08-25 11:43 639232545839529039
215 ms 66.92.25.70
32 2026-08-25 11:26 639232535349285207
224 ms 66.92.25.70
31 2026-08-25 11:08 639232524938080723
156 ms 66.92.25.70
30 2026-08-25 10:15 639232492740373468
219 ms 66.92.25.70
29 2026-08-25 09:57 639232482235303141
217 ms 66.92.25.70
28 2026-08-25 09:40 639232471861770303
111 ms 66.92.25.70
27 2026-08-25 09:23 639232461630217327
220 ms 66.92.25.70
26 2026-08-25 09:06 639232451282965990
220 ms 66.92.25.70
25 2026-08-25 08:48 639232440814614938
217 ms 66.92.25.70
24 2026-08-25 08:31 639232430410720425
219 ms 66.92.25.70
23 2026-08-25 08:14 639232420003096185
8 ms 66.92.25.70
22 2026-08-25 07:56 639232409467287444
2103 ms 66.92.25.70
21 2026-08-25 07:39 639232399077195997
221 ms 66.92.25.70
20 2026-08-25 07:21 639232388731528337
218 ms 66.92.25.70
19 2026-08-25 07:04 639232378288598612
226 ms 66.92.25.70
18 2026-08-25 06:10 639232346196373643
224 ms 66.92.25.70
17 2026-08-25 05:54 639232336112370741
221 ms 66.92.25.70
16 2026-08-25 05:37 639232326146508970
221 ms 66.92.25.70
15 2026-08-25 05:20 639232316189381720
122 ms 66.92.25.70
14 2026-08-25 05:04 639232306217998913
110 ms 66.92.25.70
13 2026-08-25 04:47 639232296255744174
102 ms 66.92.25.70
12 2026-08-25 04:30 639232286095760789
215 ms 66.92.25.70
11 2026-08-25 04:13 639232276086186273
107 ms 66.92.25.70
10 2026-08-25 03:57 639232265900986425
224 ms 66.92.25.70
9 2026-08-25 03:40 639232255723518075
108 ms 66.92.25.70
8 2026-08-25 03:23 639232245484452890
2112 ms 66.92.25.70
7 2026-08-25 03:05 639232235157175331
237 ms 66.92.25.70
6 2026-08-25 02:12 639232203197189095
228 ms 66.92.25.70
5 2026-08-25 01:55 639232192844564298
35 ms 66.92.25.70
4 2026-08-25 01:38 639232182496008942
113 ms 66.92.25.70
3 2026-08-25 01:20 639232172197053132
224 ms 66.92.25.70
2 2026-08-25 00:27 639232140250307418
218 ms 66.92.25.70
1 2026-08-25 00:10 639232129927860324
228 ms 66.92.25.70