DNS response history for ns2.perfecttrainerapp.com

ns2.perfecttrainerapp.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 272 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.perfecttrainerapp.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

272 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.161.41.169

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.perfecttrainerapp.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:00 639232587225721862
311 ms 203.161.41.169
37 2026-08-25 12:42 639232576780683689
317 ms 203.161.41.169
36 2026-08-25 12:25 639232566381512620
145 ms 203.161.41.169
35 2026-08-25 12:08 639232556111768563
327 ms 203.161.41.169
34 2026-08-25 11:51 639232545839529039
170 ms 203.161.41.169
33 2026-08-25 11:33 639232535349285207
295 ms 203.161.41.169
32 2026-08-25 11:16 639232524938080723
308 ms 203.161.41.169
31 2026-08-25 10:22 639232492740373468
310 ms 203.161.41.169
30 2026-08-25 10:05 639232482235303141
303 ms 203.161.41.169
29 2026-08-25 09:47 639232471861770303
162 ms 203.161.41.169
28 2026-08-25 09:30 639232461630217327
311 ms 203.161.41.169
27 2026-08-25 09:13 639232451282965990
151 ms 203.161.41.169
26 2026-08-25 08:56 639232440814614938
335 ms 203.161.41.169
25 2026-08-25 08:38 639232430410720425
301 ms 203.161.41.169
24 2026-08-25 08:21 639232420003096185
309 ms 203.161.41.169
23 2026-08-25 08:04 639232409467287444
309 ms 203.161.41.169
22 2026-08-25 07:46 639232399077195997
156 ms 203.161.41.169
21 2026-08-25 07:29 639232388731528337
325 ms 203.161.41.169
20 2026-08-25 07:12 639232378288598612
321 ms 203.161.41.169
19 2026-08-25 06:18 639232346196373643
299 ms 203.161.41.169
18 2026-08-25 06:01 639232336112370741
305 ms 203.161.41.169
17 2026-08-25 05:44 639232326146508970
288 ms 203.161.41.169
16 2026-08-25 05:28 639232316189381720
385 ms 203.161.41.169
15 2026-08-25 05:11 639232306217998913
322 ms 203.161.41.169
14 2026-08-25 04:54 639232296255744174
301 ms 203.161.41.169
13 2026-08-25 04:38 639232286095760789
332 ms 203.161.41.169
12 2026-08-25 04:21 639232276086186273
156 ms 203.161.41.169
11 2026-08-25 04:04 639232265900986425
314 ms 203.161.41.169
10 2026-08-25 03:47 639232255723518075
299 ms 203.161.41.169
9 2026-08-25 03:30 639232245484452890
315 ms 203.161.41.169
8 2026-08-25 03:13 639232235157175331
322 ms 203.161.41.169
7 2026-08-25 02:20 639232203197189095
304 ms 203.161.41.169
6 2026-08-25 02:03 639232192844564298
3 ms 203.161.41.169
5 2026-08-25 01:45 639232182496008942
306 ms 203.161.41.169
4 2026-08-25 01:28 639232172197053132
152 ms 203.161.41.169
3 2026-08-25 00:34 639232140250307418
300 ms 203.161.41.169
2 2026-08-25 00:18 639232129927860324
299 ms 203.161.41.169
1 2026-08-25 00:00 639232119551972438
173 ms 203.161.41.169