DNS response history for ns2.visitpas.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

420 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.171.180.121

Most recently resolved hosting IP on selected date

Successful Responses

33

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.visitpas.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
33 2026-08-27 10:38 639234233269654413
131 ms 103.171.180.121
32 2026-08-27 10:21 639234222943951923
301 ms 103.171.180.121
31 2026-08-27 10:03 639234212558002823
137 ms 103.171.180.121
30 2026-08-27 09:46 639234202117531850
272 ms 103.171.180.121
29 2026-08-27 09:28 639234191649612722
383 ms 103.171.180.121
28 2026-08-27 09:11 639234181105879568
164 ms 103.171.180.121
27 2026-08-27 08:53 639234170713214496
814 ms 103.171.180.121
26 2026-08-27 08:36 639234160341037652
339 ms 103.171.180.121
25 2026-08-27 08:19 639234149799404224
337 ms 103.171.180.121
24 2026-08-27 08:01 639234139553286469
514 ms 103.171.180.121
23 2026-08-27 07:08 639234107183588293
136 ms 103.171.180.121
22 2026-08-27 06:50 639234096905435724
270 ms 103.171.180.121
21 2026-08-27 06:33 639234086579410775
283 ms 103.171.180.121
20 2026-08-27 06:16 639234076291157956
4 ms 103.171.180.121
19 2026-08-27 05:59 639234065981939454
288 ms 103.171.180.121
18 2026-08-27 05:42 639234055548642997
277 ms 103.171.180.121
17 2026-08-27 05:24 639234045267979603
128 ms 103.171.180.121
16 2026-08-27 05:07 639234034999717463
277 ms 103.171.180.121
15 2026-08-27 04:50 639234024739225358
283 ms 103.171.180.121
14 2026-08-27 04:33 639234014311170162
143 ms 103.171.180.121
13 2026-08-27 04:16 639234003806017640
135 ms 103.171.180.121
12 2026-08-27 03:58 639233993356203030
133 ms 103.171.180.121
11 2026-08-27 03:05 639233961301716608
153 ms 103.171.180.121
10 2026-08-27 02:47 639233950834200647
137 ms 103.171.180.121
9 2026-08-27 02:30 639233940431849026
290 ms 103.171.180.121
8 2026-08-27 02:13 639233930110596398
2131 ms 103.171.180.121
7 2026-08-27 01:55 639233919705434540
295 ms 103.171.180.121
6 2026-08-27 01:38 639233909452807845
279 ms 103.171.180.121
5 2026-08-27 01:21 639233899096420820
2260 ms 103.171.180.121
4 2026-08-27 01:04 639233888707824939
143 ms 103.171.180.121
3 2026-08-27 00:46 639233878461203802
138 ms 103.171.180.121
2 2026-08-27 00:29 639233868060868209
2142 ms 103.171.180.121
1 2026-08-27 00:12 639233857450922991
134 ms 103.171.180.121