DNS response history for ns2.webmdpro.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

279 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

132.148.77.72

Most recently resolved hosting IP on selected date

Successful Responses

35

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.webmdpro.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
35 2026-08-27 11:15 639234253963286387
338 ms 132.148.77.72
34 2026-08-27 10:58 639234243654907465
171 ms 132.148.77.72
33 2026-08-27 10:40 639234233269654413
353 ms 132.148.77.72
32 2026-08-27 10:23 639234222943951923
173 ms 132.148.77.72
31 2026-08-27 10:06 639234212558002823
353 ms 132.148.77.72
30 2026-08-27 09:48 639234202117531850
362 ms 132.148.77.72
29 2026-08-27 09:31 639234191649612722
173 ms 132.148.77.72
28 2026-08-27 09:14 639234181105879568
368 ms 132.148.77.72
27 2026-08-27 08:56 639234170713214496
335 ms 132.148.77.72
26 2026-08-27 08:39 639234160341037652
352 ms 132.148.77.72
25 2026-08-27 08:21 639234149799404224
337 ms 132.148.77.72
24 2026-08-27 08:04 639234139553286469
369 ms 132.148.77.72
23 2026-08-27 07:10 639234107183588293
175 ms 132.148.77.72
22 2026-08-27 06:53 639234096905435724
336 ms 132.148.77.72
21 2026-08-27 06:36 639234086579410775
358 ms 132.148.77.72
20 2026-08-27 06:19 639234076291157956
339 ms 132.148.77.72
19 2026-08-27 06:02 639234065981939454
355 ms 132.148.77.72
18 2026-08-27 05:44 639234055548642997
335 ms 132.148.77.72
17 2026-08-27 05:27 639234045267979603
173 ms 132.148.77.72
16 2026-08-27 05:10 639234034999717463
391 ms 132.148.77.72
15 2026-08-27 04:53 639234024739225358
166 ms 132.148.77.72
14 2026-08-27 04:36 639234014311170162
332 ms 132.148.77.72
13 2026-08-27 04:18 639234003806017640
169 ms 132.148.77.72
12 2026-08-27 04:00 639233993356203030
9 ms 132.148.77.72
11 2026-08-27 03:07 639233961301716608
172 ms 132.148.77.72
10 2026-08-27 02:50 639233950834200647
350 ms 132.148.77.72
9 2026-08-27 02:32 639233940431849026
332 ms 132.148.77.72
8 2026-08-27 02:15 639233930110596398
365 ms 132.148.77.72
7 2026-08-27 01:58 639233919705434540
9 ms 132.148.77.72
6 2026-08-27 01:41 639233909452807845
344 ms 132.148.77.72
5 2026-08-27 01:23 639233899096420820
171 ms 132.148.77.72
4 2026-08-27 01:06 639233888707824939
339 ms 132.148.77.72
3 2026-08-27 00:49 639233878461203802
189 ms 132.148.77.72
2 2026-08-27 00:32 639233868060868209
331 ms 132.148.77.72
1 2026-08-27 00:14 639233857450922991
341 ms 132.148.77.72