DNS response history for ns2.valcourtpediatrics.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

436 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.161.117.175

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 ns2.valcourtpediatrics.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
37 2026-08-26 12:14 639233424567558554
427 ms 51.161.117.175
36 2026-08-26 11:56 639233414056832719
436 ms 51.161.117.175
35 2026-08-26 11:39 639233403515141099
435 ms 51.161.117.175
34 2026-08-26 10:44 639233370841350248
436 ms 51.161.117.175
33 2026-08-26 10:27 639233360361507238
427 ms 51.161.117.175
32 2026-08-26 10:09 639233350067824371
2218 ms 51.161.117.175
31 2026-08-26 09:52 639233339545274518
428 ms 51.161.117.175
30 2026-08-26 09:35 639233329214918079
435 ms 51.161.117.175
29 2026-08-26 09:17 639233318749762337
429 ms 51.161.117.175
28 2026-08-26 09:00 639233308387917838
443 ms 51.161.117.175
27 2026-08-26 08:43 639233297961740122
431 ms 51.161.117.175
26 2026-08-26 08:25 639233287487159094
430 ms 51.161.117.175
25 2026-08-26 08:08 639233276995531707
432 ms 51.161.117.175
24 2026-08-26 07:50 639233266521568229
433 ms 51.161.117.175
23 2026-08-26 07:33 639233256081047431
437 ms 51.161.117.175
22 2026-08-26 06:39 639233223620132921
430 ms 51.161.117.175
21 2026-08-26 06:22 639233213287814244
428 ms 51.161.117.175
20 2026-08-26 06:04 639233202925983161
121 ms 51.161.117.175
19 2026-08-26 05:47 639233192644780696
447 ms 51.161.117.175
18 2026-08-26 05:30 639233182401183833
438 ms 51.161.117.175
17 2026-08-26 05:13 639233172074181051
427 ms 51.161.117.175
16 2026-08-26 04:56 639233161808421455
386 ms 51.161.117.175
15 2026-08-26 04:38 639233151357344052
430 ms 51.161.117.175
14 2026-08-26 04:21 639233141034116946
428 ms 51.161.117.175
13 2026-08-26 04:04 639233130828334142
430 ms 51.161.117.175
12 2026-08-26 03:47 639233120373450007
428 ms 51.161.117.175
11 2026-08-26 03:29 639233110066216193
433 ms 51.161.117.175
10 2026-08-26 02:36 639233078065410564
431 ms 51.161.117.175
9 2026-08-26 02:19 639233067787457832
9 ms 51.161.117.175
8 2026-08-26 02:02 639233057501801162
2 ms 51.161.117.175
7 2026-08-26 01:45 639233047089431703
428 ms 51.161.117.175
6 2026-08-26 01:27 639233036754790688
429 ms 51.161.117.175
5 2026-08-26 01:10 639233026412602472
10 ms 51.161.117.175
4 2026-08-26 00:53 639233016064066127
429 ms 51.161.117.175
3 2026-08-26 00:36 639233005922655772
440 ms 51.161.117.175
2 2026-08-26 00:19 639232995672256907
429 ms 51.161.117.175
1 2026-08-26 00:02 639232985300872416
427 ms 51.161.117.175