DNS response history for ns2.pavmann.com

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

27

Historical checks stored for this nameserver on selected date

Average Latency

178 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.170.129.4

Most recently resolved hosting IP on selected date

Successful Responses

27

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

Showing DNS history for 2026-08-27 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
27 2026-08-27 08:57 639234170713214496
115 ms 203.170.129.4
26 2026-08-27 08:39 639234160341037652
219 ms 203.170.129.4
25 2026-08-27 08:22 639234149799404224
119 ms 203.170.129.4
24 2026-08-27 08:04 639234139553286469
221 ms 203.170.129.4
23 2026-08-27 07:11 639234107183588293
121 ms 203.170.129.4
22 2026-08-27 06:54 639234096905435724
117 ms 203.170.129.4
21 2026-08-27 06:36 639234086579410775
302 ms 203.170.129.4
20 2026-08-27 06:19 639234076291157956
312 ms 203.170.129.4
19 2026-08-27 06:02 639234065981939454
301 ms 203.170.129.4
18 2026-08-27 05:45 639234055548642997
298 ms 203.170.129.4
17 2026-08-27 05:27 639234045267979603
220 ms 203.170.129.4
16 2026-08-27 05:10 639234034999717463
107 ms 203.170.129.4
15 2026-08-27 04:53 639234024739225358
112 ms 203.170.129.4
14 2026-08-27 04:36 639234014311170162
117 ms 203.170.129.4
13 2026-08-27 04:19 639234003806017640
220 ms 203.170.129.4
12 2026-08-27 04:01 639233993356203030
112 ms 203.170.129.4
11 2026-08-27 03:08 639233961301716608
2 ms 203.170.129.4
10 2026-08-27 02:50 639233950834200647
111 ms 203.170.129.4
9 2026-08-27 02:33 639233940431849026
299 ms 203.170.129.4
8 2026-08-27 02:16 639233930110596398
111 ms 203.170.129.4
7 2026-08-27 01:58 639233919705434540
133 ms 203.170.129.4
6 2026-08-27 01:41 639233909452807845
296 ms 203.170.129.4
5 2026-08-27 01:24 639233899096420820
113 ms 203.170.129.4
4 2026-08-27 01:07 639233888707824939
212 ms 203.170.129.4
3 2026-08-27 00:49 639233878461203802
114 ms 203.170.129.4
2 2026-08-27 00:32 639233868060868209
110 ms 203.170.129.4
1 2026-08-27 00:15 639233857450922991
289 ms 203.170.129.4