DNS response history for ns2.pulsant.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

256 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

82.113.166.103

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.pulsant.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
36 2026-08-26 12:02 639233424567558554
128 ms 82.113.166.103
35 2026-08-26 11:44 639233414056832719
55 ms 82.113.166.103
34 2026-08-26 11:26 639233403515141099
2029 ms 82.113.166.103
33 2026-08-26 10:32 639233370841350248
39 ms 82.113.166.103
32 2026-08-26 10:15 639233360361507238
27 ms 82.113.166.103
31 2026-08-26 09:57 639233350067824371
20 ms 82.113.166.103
30 2026-08-26 09:40 639233339545274518
8 ms 82.113.166.103
29 2026-08-26 09:23 639233329214918079
24 ms 82.113.166.103
28 2026-08-26 09:05 639233318749762337
15 ms 82.113.166.103
27 2026-08-26 08:48 639233308387917838
43 ms 82.113.166.103
26 2026-08-26 08:30 639233297961740122
13 ms 82.113.166.103
25 2026-08-26 08:13 639233287487159094
46 ms 82.113.166.103
24 2026-08-26 07:56 639233276995531707
40 ms 82.113.166.103
23 2026-08-26 07:38 639233266521568229
23 ms 82.113.166.103
22 2026-08-26 07:21 639233256081047431
2022 ms 82.113.166.103
21 2026-08-26 06:27 639233223620132921
25 ms 82.113.166.103
20 2026-08-26 06:09 639233213287814244
30 ms 82.113.166.103
19 2026-08-26 05:52 639233202925983161
31 ms 82.113.166.103
18 2026-08-26 05:35 639233192644780696
30 ms 82.113.166.103
17 2026-08-26 05:18 639233182401183833
2028 ms 82.113.166.103
16 2026-08-26 05:01 639233172074181051
23 ms 82.113.166.103
15 2026-08-26 04:44 639233161808421455
56 ms 82.113.166.103
14 2026-08-26 04:26 639233151357344052
25 ms 82.113.166.103
13 2026-08-26 04:09 639233141034116946
24 ms 82.113.166.103
12 2026-08-26 03:52 639233130828334142
68 ms 82.113.166.103
11 2026-08-26 03:35 639233120373450007
26 ms 82.113.166.103
10 2026-08-26 03:17 639233110066216193
6 ms 82.113.166.103
9 2026-08-26 02:24 639233078065410564
112 ms 82.113.166.103
8 2026-08-26 02:07 639233067787457832
21 ms 82.113.166.103
7 2026-08-26 01:50 639233057501801162
42 ms 82.113.166.103
6 2026-08-26 01:32 639233047089431703
17 ms 82.113.166.103
5 2026-08-26 01:15 639233036754790688
4 ms 82.113.166.103
4 2026-08-26 00:58 639233026412602472
9 ms 82.113.166.103
3 2026-08-26 00:41 639233016064066127
33 ms 82.113.166.103
2 2026-08-26 00:24 639233005922655772
2040 ms 82.113.166.103
1 2026-08-26 00:07 639232995672256907
49 ms 82.113.166.103