DNS response history for ns2.pusulaconsulting.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

141 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.230.111.111

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.pusulaconsulting.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
35 2026-08-26 11:52 639233414056832719
132 ms 37.230.111.111
34 2026-08-26 11:34 639233403515141099
202 ms 37.230.111.111
33 2026-08-26 10:40 639233370841350248
160 ms 37.230.111.111
32 2026-08-26 10:22 639233360361507238
140 ms 37.230.111.111
31 2026-08-26 10:05 639233350067824371
121 ms 37.230.111.111
30 2026-08-26 09:48 639233339545274518
118 ms 37.230.111.111
29 2026-08-26 09:30 639233329214918079
166 ms 37.230.111.111
28 2026-08-26 09:13 639233318749762337
151 ms 37.230.111.111
27 2026-08-26 08:56 639233308387917838
218 ms 37.230.111.111
26 2026-08-26 08:38 639233297961740122
142 ms 37.230.111.111
25 2026-08-26 08:21 639233287487159094
104 ms 37.230.111.111
24 2026-08-26 08:03 639233276995531707
118 ms 37.230.111.111
23 2026-08-26 07:46 639233266521568229
130 ms 37.230.111.111
22 2026-08-26 07:28 639233256081047431
117 ms 37.230.111.111
21 2026-08-26 06:35 639233223620132921
144 ms 37.230.111.111
20 2026-08-26 06:17 639233213287814244
140 ms 37.230.111.111
19 2026-08-26 06:00 639233202925983161
159 ms 37.230.111.111
18 2026-08-26 05:43 639233192644780696
142 ms 37.230.111.111
17 2026-08-26 05:26 639233182401183833
193 ms 37.230.111.111
16 2026-08-26 05:09 639233172074181051
145 ms 37.230.111.111
15 2026-08-26 04:51 639233161808421455
131 ms 37.230.111.111
14 2026-08-26 04:34 639233151357344052
125 ms 37.230.111.111
13 2026-08-26 04:17 639233141034116946
129 ms 37.230.111.111
12 2026-08-26 04:00 639233130828334142
146 ms 37.230.111.111
11 2026-08-26 03:42 639233120373450007
146 ms 37.230.111.111
10 2026-08-26 03:25 639233110066216193
124 ms 37.230.111.111
9 2026-08-26 02:32 639233078065410564
150 ms 37.230.111.111
8 2026-08-26 02:15 639233067787457832
127 ms 37.230.111.111
7 2026-08-26 01:57 639233057501801162
139 ms 37.230.111.111
6 2026-08-26 01:40 639233047089431703
116 ms 37.230.111.111
5 2026-08-26 01:23 639233036754790688
166 ms 37.230.111.111
4 2026-08-26 01:06 639233026412602472
114 ms 37.230.111.111
3 2026-08-26 00:48 639233016064066127
123 ms 37.230.111.111
2 2026-08-26 00:31 639233005922655772
120 ms 37.230.111.111
1 2026-08-26 00:14 639232995672256907
127 ms 37.230.111.111