DNS response history for ns1.deeppol.com

ns1.deeppol.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, 36 successful responses, 1 failed responses, and 309 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 ns1.deeppol.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

309 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.210.43.180

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.deeppol.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:24 639233434974187439
96 ms 31.210.43.180
36 2026-08-26 12:07 639233424567558554
82 ms 31.210.43.180
35 2026-08-26 11:49 639233414056832719
76 ms 31.210.43.180
34 2026-08-26 11:32 639233403515141099
2084 ms 31.210.43.180
33 2026-08-26 10:37 639233370841350248
105 ms 31.210.43.180
32 2026-08-26 10:20 639233360361507238
95 ms 31.210.43.180
31 2026-08-26 10:03 639233350067824371
55 ms 31.210.43.180
30 2026-08-26 09:45 639233339545274518
85 ms 31.210.43.180
29 2026-08-26 09:28 639233329214918079
89 ms 31.210.43.180
28 2026-08-26 09:10 639233318749762337
67 ms 31.210.43.180
27 2026-08-26 08:53 639233308387917838
102 ms 31.210.43.180
26 2026-08-26 08:36 639233297961740122
138 ms 31.210.43.180
25 2026-08-26 08:18 639233287487159094
107 ms 31.210.43.180
24 2026-08-26 08:01 639233276995531707
143 ms 31.210.43.180
23 2026-08-26 07:43 639233266521568229
90 ms 31.210.43.180
22 2026-08-26 07:26 639233256081047431
98 ms 31.210.43.180
21 2026-08-26 06:32 639233223620132921
42 ms 31.210.43.180
20 2026-08-26 06:15 639233213287814244
153 ms 31.210.43.180
19 2026-08-26 05:58 639233202925983161
-
18 2026-08-26 05:40 639233192644780696
17 ms 31.210.43.180
17 2026-08-26 05:23 639233182401183833
106 ms 31.210.43.180
16 2026-08-26 05:06 639233172074181051
58 ms 31.210.43.180
15 2026-08-26 04:49 639233161808421455
102 ms 31.210.43.180
14 2026-08-26 04:31 639233151357344052
109 ms 31.210.43.180
13 2026-08-26 04:14 639233141034116946
2037 ms 31.210.43.180
12 2026-08-26 03:57 639233130828334142
130 ms 31.210.43.180
11 2026-08-26 03:40 639233120373450007
2009 ms 31.210.43.180
10 2026-08-26 03:23 639233110066216193
65 ms 31.210.43.180
9 2026-08-26 02:29 639233078065410564
2009 ms 31.210.43.180
8 2026-08-26 02:12 639233067787457832
116 ms 31.210.43.180
7 2026-08-26 01:55 639233057501801162
94 ms 31.210.43.180
6 2026-08-26 01:38 639233047089431703
116 ms 31.210.43.180
5 2026-08-26 01:21 639233036754790688
120 ms 31.210.43.180
4 2026-08-26 01:03 639233026412602472
96 ms 31.210.43.180
3 2026-08-26 00:46 639233016064066127
61 ms 31.210.43.180
2 2026-08-26 00:29 639233005922655772
56 ms 31.210.43.180
1 2026-08-26 00:12 639232995672256907
126 ms 31.210.43.180