DNS response history for ns2.physiovd.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

320 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.57.27.147

Most recently resolved hosting IP on selected date

Successful Responses

36

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.physiovd.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
36 2026-08-27 12:08 639234286253196126
220 ms 198.57.27.147
35 2026-08-27 11:14 639234253963286387
221 ms 198.57.27.147
34 2026-08-27 10:57 639234243654907465
219 ms 198.57.27.147
33 2026-08-27 10:40 639234233269654413
221 ms 198.57.27.147
32 2026-08-27 10:22 639234222943951923
224 ms 198.57.27.147
31 2026-08-27 10:05 639234212558002823
230 ms 198.57.27.147
30 2026-08-27 09:48 639234202117531850
218 ms 198.57.27.147
29 2026-08-27 09:30 639234191649612722
215 ms 198.57.27.147
28 2026-08-27 09:13 639234181105879568
217 ms 198.57.27.147
27 2026-08-27 08:55 639234170713214496
223 ms 198.57.27.147
26 2026-08-27 08:38 639234160341037652
2113 ms 198.57.27.147
25 2026-08-27 08:21 639234149799404224
218 ms 198.57.27.147
24 2026-08-27 08:03 639234139553286469
218 ms 198.57.27.147
23 2026-08-27 07:09 639234107183588293
219 ms 198.57.27.147
22 2026-08-27 06:52 639234096905435724
216 ms 198.57.27.147
21 2026-08-27 06:35 639234086579410775
214 ms 198.57.27.147
20 2026-08-27 06:18 639234076291157956
215 ms 198.57.27.147
19 2026-08-27 06:01 639234065981939454
229 ms 198.57.27.147
18 2026-08-27 05:44 639234055548642997
223 ms 198.57.27.147
17 2026-08-27 05:26 639234045267979603
222 ms 198.57.27.147
16 2026-08-27 05:09 639234034999717463
221 ms 198.57.27.147
15 2026-08-27 04:52 639234024739225358
215 ms 198.57.27.147
14 2026-08-27 04:35 639234014311170162
213 ms 198.57.27.147
13 2026-08-27 04:17 639234003806017640
219 ms 198.57.27.147
12 2026-08-27 04:00 639233993356203030
220 ms 198.57.27.147
11 2026-08-27 03:06 639233961301716608
216 ms 198.57.27.147
10 2026-08-27 02:49 639233950834200647
211 ms 198.57.27.147
9 2026-08-27 02:32 639233940431849026
106 ms 198.57.27.147
8 2026-08-27 02:14 639233930110596398
218 ms 198.57.27.147
7 2026-08-27 01:57 639233919705434540
213 ms 198.57.27.147
6 2026-08-27 01:40 639233909452807845
219 ms 198.57.27.147
5 2026-08-27 01:23 639233899096420820
2108 ms 198.57.27.147
4 2026-08-27 01:06 639233888707824939
209 ms 198.57.27.147
3 2026-08-27 00:48 639233878461203802
215 ms 198.57.27.147
2 2026-08-27 00:31 639233868060868209
215 ms 198.57.27.147
1 2026-08-27 00:13 639233857450922991
216 ms 198.57.27.147