DNS response history for ns2.ptvems.com

ns2.ptvems.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 432 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.ptvems.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

432 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

154.61.72.250

Most recently resolved hosting IP on selected date

Successful Responses

34

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

Showing DNS history for 2026-08-26 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
34 2026-08-26 10:44 639233370841350248
2142 ms 154.61.72.250
33 2026-08-26 10:27 639233360361507238
366 ms 154.61.72.250
32 2026-08-26 10:09 639233350067824371
355 ms 154.61.72.250
31 2026-08-26 09:52 639233339545274518
349 ms 154.61.72.250
30 2026-08-26 09:34 639233329214918079
345 ms 154.61.72.250
29 2026-08-26 09:17 639233318749762337
351 ms 154.61.72.250
28 2026-08-26 09:00 639233308387917838
347 ms 154.61.72.250
27 2026-08-26 08:42 639233297961740122
344 ms 154.61.72.250
26 2026-08-26 08:25 639233287487159094
363 ms 154.61.72.250
25 2026-08-26 08:08 639233276995531707
182 ms 154.61.72.250
24 2026-08-26 07:50 639233266521568229
2252 ms 154.61.72.250
23 2026-08-26 07:33 639233256081047431
183 ms 154.61.72.250
22 2026-08-26 06:39 639233223620132921
196 ms 154.61.72.250
21 2026-08-26 06:21 639233213287814244
154 ms 154.61.72.250
20 2026-08-26 06:04 639233202925983161
180 ms 154.61.72.250
19 2026-08-26 05:47 639233192644780696
177 ms 154.61.72.250
18 2026-08-26 05:30 639233182401183833
4 ms 154.61.72.250
17 2026-08-26 05:13 639233172074181051
2 ms 154.61.72.250
16 2026-08-26 04:55 639233161808421455
349 ms 154.61.72.250
15 2026-08-26 04:38 639233151357344052
363 ms 154.61.72.250
14 2026-08-26 04:21 639233141034116946
177 ms 154.61.72.250
13 2026-08-26 04:04 639233130828334142
171 ms 154.61.72.250
12 2026-08-26 03:47 639233120373450007
345 ms 154.61.72.250
11 2026-08-26 03:29 639233110066216193
174 ms 154.61.72.250
10 2026-08-26 02:36 639233078065410564
357 ms 154.61.72.250
9 2026-08-26 02:19 639233067787457832
2187 ms 154.61.72.250
8 2026-08-26 02:02 639233057501801162
343 ms 154.61.72.250
7 2026-08-26 01:44 639233047089431703
173 ms 154.61.72.250
6 2026-08-26 01:27 639233036754790688
352 ms 154.61.72.250
5 2026-08-26 01:10 639233026412602472
344 ms 154.61.72.250
4 2026-08-26 00:53 639233016064066127
351 ms 154.61.72.250
3 2026-08-26 00:35 639233005922655772
175 ms 154.61.72.250
2 2026-08-26 00:18 639232995672256907
171 ms 154.61.72.250
1 2026-08-26 00:01 639232985300872416
349 ms 154.61.72.250