DNS response history for ns-mx2.physio-control.com

ns-mx2.physio-control.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 37 DNS check records, 37 successful responses, 0 failed responses, and 349 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 ns-mx2.physio-control.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

349 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

204.128.31.150

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns-mx2.physio-control.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
37 2026-08-27 12:15 639234296664302575
24 ms 204.128.31.150
36 2026-08-27 11:58 639234286253196126
20 ms 204.128.31.150
35 2026-08-27 11:04 639234253963286387
4031 ms 204.128.31.150
34 2026-08-27 10:47 639234243654907465
16 ms 204.128.31.150
33 2026-08-27 10:29 639234233269654413
23 ms 204.128.31.150
32 2026-08-27 10:12 639234222943951923
2029 ms 204.128.31.150
31 2026-08-27 09:55 639234212558002823
25 ms 204.128.31.150
30 2026-08-27 09:38 639234202117531850
20 ms 204.128.31.150
29 2026-08-27 09:20 639234191649612722
2026 ms 204.128.31.150
28 2026-08-27 09:03 639234181105879568
4 ms 204.128.31.150
27 2026-08-27 08:45 639234170713214496
50 ms 204.128.31.150
26 2026-08-27 08:28 639234160341037652
21 ms 204.128.31.150
25 2026-08-27 08:10 639234149799404224
26 ms 204.128.31.150
24 2026-08-27 07:53 639234139553286469
30 ms 204.128.31.150
23 2026-08-27 06:59 639234107183588293
4037 ms 204.128.31.150
22 2026-08-27 06:42 639234096905435724
7 ms 204.128.31.150
21 2026-08-27 06:25 639234086579410775
20 ms 204.128.31.150
20 2026-08-27 06:08 639234076291157956
19 ms 204.128.31.150
19 2026-08-27 05:51 639234065981939454
3 ms 204.128.31.150
18 2026-08-27 05:33 639234055548642997
35 ms 204.128.31.150
17 2026-08-27 05:16 639234045267979603
21 ms 204.128.31.150
16 2026-08-27 04:59 639234034999717463
40 ms 204.128.31.150
15 2026-08-27 04:42 639234024739225358
9 ms 204.128.31.150
14 2026-08-27 04:25 639234014311170162
20 ms 204.128.31.150
13 2026-08-27 04:07 639234003806017640
21 ms 204.128.31.150
12 2026-08-27 03:50 639233993356203030
24 ms 204.128.31.150
11 2026-08-27 02:56 639233961301716608
24 ms 204.128.31.150
10 2026-08-27 02:39 639233950834200647
18 ms 204.128.31.150
9 2026-08-27 02:21 639233940431849026
19 ms 204.128.31.150
8 2026-08-27 02:04 639233930110596398
23 ms 204.128.31.150
7 2026-08-27 01:47 639233919705434540
55 ms 204.128.31.150
6 2026-08-27 01:30 639233909452807845
20 ms 204.128.31.150
5 2026-08-27 01:12 639233899096420820
74 ms 204.128.31.150
4 2026-08-27 00:55 639233888707824939
11 ms 204.128.31.150
3 2026-08-27 00:38 639233878461203802
24 ms 204.128.31.150
2 2026-08-27 00:21 639233868060868209
10 ms 204.128.31.150
1 2026-08-27 00:03 639233857450922991
41 ms 204.128.31.150