DNS response history for ns2.ptsrm.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

327 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

190.102.104.130

Most recently resolved hosting IP on selected date

Successful Responses

30

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.ptsrm.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
30 2026-08-26 09:34 639233329214918079
317 ms 190.102.104.130
29 2026-08-26 09:17 639233318749762337
314 ms 190.102.104.130
28 2026-08-26 08:59 639233308387917838
296 ms 190.102.104.130
27 2026-08-26 08:42 639233297961740122
292 ms 190.102.104.130
26 2026-08-26 08:25 639233287487159094
191 ms 190.102.104.130
25 2026-08-26 08:07 639233276995531707
299 ms 190.102.104.130
24 2026-08-26 07:50 639233266521568229
304 ms 190.102.104.130
23 2026-08-26 07:32 639233256081047431
2173 ms 190.102.104.130
22 2026-08-26 06:38 639233223620132921
154 ms 190.102.104.130
21 2026-08-26 06:21 639233213287814244
329 ms 190.102.104.130
20 2026-08-26 06:04 639233202925983161
308 ms 190.102.104.130
19 2026-08-26 05:46 639233192644780696
302 ms 190.102.104.130
18 2026-08-26 05:29 639233182401183833
301 ms 190.102.104.130
17 2026-08-26 05:12 639233172074181051
150 ms 190.102.104.130
16 2026-08-26 04:55 639233161808421455
310 ms 190.102.104.130
15 2026-08-26 04:38 639233151357344052
296 ms 190.102.104.130
14 2026-08-26 04:20 639233141034116946
297 ms 190.102.104.130
13 2026-08-26 04:03 639233130828334142
309 ms 190.102.104.130
12 2026-08-26 03:46 639233120373450007
150 ms 190.102.104.130
11 2026-08-26 03:29 639233110066216193
306 ms 190.102.104.130
10 2026-08-26 02:35 639233078065410564
309 ms 190.102.104.130
9 2026-08-26 02:18 639233067787457832
293 ms 190.102.104.130
8 2026-08-26 02:01 639233057501801162
299 ms 190.102.104.130
7 2026-08-26 01:44 639233047089431703
292 ms 190.102.104.130
6 2026-08-26 01:27 639233036754790688
290 ms 190.102.104.130
5 2026-08-26 01:09 639233026412602472
158 ms 190.102.104.130
4 2026-08-26 00:52 639233016064066127
150 ms 190.102.104.130
3 2026-08-26 00:35 639233005922655772
305 ms 190.102.104.130
2 2026-08-26 00:18 639232995672256907
179 ms 190.102.104.130
1 2026-08-26 00:01 639232985300872416
151 ms 190.102.104.130