DNS response history for ns2.digipehchan.com

ns2.digipehchan.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-30. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 226 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.digipehchan.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

226 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

101.53.147.122

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.digipehchan.com

Showing DNS history for 2026-08-30 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-30 11:51 639236867916029489
11 ms 101.53.147.122
35 2026-08-30 11:34 639236858088772005
266 ms 101.53.147.122
34 2026-08-30 11:18 639236848158742395
2161 ms 101.53.147.122
33 2026-08-30 11:01 639236838137395574
158 ms 101.53.147.122
32 2026-08-30 10:44 639236827967386881
302 ms 101.53.147.122
31 2026-08-30 10:27 639236817708615077
303 ms 101.53.147.122
30 2026-08-30 09:34 639236785770651804
5 ms 101.53.147.122
29 2026-08-30 09:17 639236775820686373
296 ms 101.53.147.122
28 2026-08-30 09:00 639236765768339082
5 ms 101.53.147.122
27 2026-08-30 08:44 639236755602384085
5 ms 101.53.147.122
26 2026-08-30 08:27 639236745600094925
301 ms 101.53.147.122
25 2026-08-30 08:10 639236735311262753
3 ms 101.53.147.122
24 2026-08-30 07:53 639236724996745235
3 ms 101.53.147.122
23 2026-08-30 07:36 639236714839899761
17 ms 101.53.147.122
22 2026-08-30 07:19 639236704748431488
203 ms 101.53.147.122
21 2026-08-30 07:02 639236694430128550
317 ms 101.53.147.122
20 2026-08-30 06:45 639236684143292417
310 ms 101.53.147.122
19 2026-08-30 06:27 639236673972499943
303 ms 101.53.147.122
18 2026-08-30 05:34 639236642126522802
2 ms 101.53.147.122
17 2026-08-30 05:18 639236632183518198
394 ms 101.53.147.122
16 2026-08-30 05:01 639236622289312589
4 ms 101.53.147.122
15 2026-08-30 04:45 639236612490676525
156 ms 101.53.147.122
14 2026-08-30 04:28 639236602582494852
2 ms 101.53.147.122
13 2026-08-30 04:12 639236592511706469
159 ms 101.53.147.122
12 2026-08-30 03:55 639236582441006869
298 ms 101.53.147.122
11 2026-08-30 03:38 639236572478785089
3 ms 101.53.147.122
10 2026-08-30 03:22 639236562556749999
7 ms 101.53.147.122
9 2026-08-30 03:05 639236552353482281
150 ms 101.53.147.122
8 2026-08-30 02:48 639236542188881607
301 ms 101.53.147.122
7 2026-08-30 02:31 639236531885440105
313 ms 101.53.147.122
6 2026-08-30 01:37 639236499922985383
297 ms 101.53.147.122
5 2026-08-30 01:20 639236489713594431
7 ms 101.53.147.122
4 2026-08-30 01:04 639236479750443901
149 ms 101.53.147.122
3 2026-08-30 00:47 639236469719936375
303 ms 101.53.147.122
2 2026-08-30 00:30 639236459579244885
301 ms 101.53.147.122
1 2026-08-30 00:13 639236449582837549
311 ms 101.53.147.122