DNS response history for ns2.webpulse.com

ns2.webpulse.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 488 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.webpulse.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

488 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.210.36.137

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.webpulse.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:17 639234253963286387
508 ms 66.210.36.137
34 2026-08-27 11:00 639234243654907465
521 ms 66.210.36.137
33 2026-08-27 10:43 639234233269654413
509 ms 66.210.36.137
32 2026-08-27 10:25 639234222943951923
500 ms 66.210.36.137
31 2026-08-27 10:08 639234212558002823
511 ms 66.210.36.137
30 2026-08-27 09:51 639234202117531850
499 ms 66.210.36.137
29 2026-08-27 09:33 639234191649612722
508 ms 66.210.36.137
28 2026-08-27 09:16 639234181105879568
497 ms 66.210.36.137
27 2026-08-27 08:58 639234170713214496
506 ms 66.210.36.137
26 2026-08-27 08:41 639234160341037652
514 ms 66.210.36.137
25 2026-08-27 08:24 639234149799404224
523 ms 66.210.36.137
24 2026-08-27 08:06 639234139553286469
510 ms 66.210.36.137
23 2026-08-27 07:13 639234107183588293
507 ms 66.210.36.137
22 2026-08-27 06:55 639234096905435724
471 ms 66.210.36.137
21 2026-08-27 06:38 639234086579410775
478 ms 66.210.36.137
20 2026-08-27 06:21 639234076291157956
477 ms 66.210.36.137
19 2026-08-27 06:04 639234065981939454
471 ms 66.210.36.137
18 2026-08-27 05:47 639234055548642997
487 ms 66.210.36.137
17 2026-08-27 05:29 639234045267979603
463 ms 66.210.36.137
16 2026-08-27 05:12 639234034999717463
482 ms 66.210.36.137
15 2026-08-27 04:55 639234024739225358
164 ms 66.210.36.137
14 2026-08-27 04:38 639234014311170162
518 ms 66.210.36.137
13 2026-08-27 04:20 639234003806017640
520 ms 66.210.36.137
12 2026-08-27 04:03 639233993356203030
482 ms 66.210.36.137
11 2026-08-27 03:09 639233961301716608
516 ms 66.210.36.137
10 2026-08-27 02:52 639233950834200647
498 ms 66.210.36.137
9 2026-08-27 02:35 639233940431849026
500 ms 66.210.36.137
8 2026-08-27 02:17 639233930110596398
489 ms 66.210.36.137
7 2026-08-27 02:00 639233919705434540
509 ms 66.210.36.137
6 2026-08-27 01:43 639233909452807845
494 ms 66.210.36.137
5 2026-08-27 01:26 639233899096420820
469 ms 66.210.36.137
4 2026-08-27 01:09 639233888707824939
491 ms 66.210.36.137
3 2026-08-27 00:51 639233878461203802
487 ms 66.210.36.137
2 2026-08-27 00:34 639233868060868209
492 ms 66.210.36.137
1 2026-08-27 00:17 639233857450922991
496 ms 66.210.36.137