DNS response history for ns2.mirzabimeh.com

ns2.mirzabimeh.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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 277 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.mirzabimeh.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

277 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.116.161.126

Most recently resolved hosting IP on selected date

Successful Responses

32

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

Showing DNS history for 2026-08-24 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
32 2026-08-24 13:31 639231745628278877
122 ms 185.116.161.126
31 2026-08-24 13:14 639231735407682062
5 ms 185.116.161.126
30 2026-08-24 12:21 639231703815441688
14 ms 185.116.161.126
29 2026-08-24 12:04 639231693747052549
181 ms 185.116.161.126
28 2026-08-24 11:48 639231683712487276
25 ms 185.116.161.126
27 2026-08-24 11:31 639231673513573868
168 ms 185.116.161.126
26 2026-08-24 10:38 639231641791249939
92 ms 185.116.161.126
25 2026-08-24 10:21 639231631866211033
180 ms 185.116.161.126
24 2026-08-24 10:04 639231621644955316
190 ms 185.116.161.126
23 2026-08-24 09:47 639231611478799259
93 ms 185.116.161.126
22 2026-08-24 08:55 639231579923718211
188 ms 185.116.161.126
21 2026-08-24 08:38 639231569810702936
7 ms 185.116.161.126
20 2026-08-24 08:21 639231559762411619
167 ms 185.116.161.126
19 2026-08-24 08:04 639231549663595407
139 ms 185.116.161.126
18 2026-08-24 07:12 639231518076817246
4 ms 185.116.161.126
17 2026-08-24 06:55 639231508078650885
3 ms 185.116.161.126
16 2026-08-24 06:38 639231498210697093
3 ms 185.116.161.126
15 2026-08-24 06:22 639231488109699360
2087 ms 185.116.161.126
14 2026-08-24 05:30 639231456772510692
6 ms 185.116.161.126
13 2026-08-24 05:13 639231447084631185
187 ms 185.116.161.126
12 2026-08-24 04:57 639231437208519473
171 ms 185.116.161.126
11 2026-08-24 04:40 639231427209627490
2007 ms 185.116.161.126
10 2026-08-24 03:48 639231395791246644
14 ms 185.116.161.126
9 2026-08-24 03:32 639231386075551458
92 ms 185.116.161.126
8 2026-08-24 03:15 639231376208713791
172 ms 185.116.161.126
7 2026-08-24 02:59 639231366170589276
100 ms 185.116.161.126
6 2026-08-24 02:06 639231334732159368
7 ms 185.116.161.126
5 2026-08-24 01:50 639231325035670078
8 ms 185.116.161.126
4 2026-08-24 01:33 639231315132253837
198 ms 185.116.161.126
3 2026-08-24 01:17 639231305014280808
173 ms 185.116.161.126
2 2026-08-24 00:24 639231273779380675
52 ms 185.116.161.126
1 2026-08-24 00:09 639231264180839154
2003 ms 185.116.161.126