DNS response history for ns2.medyamir.com

ns2.medyamir.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-27. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 237 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.medyamir.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

237 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.68.60.50

Most recently resolved hosting IP on selected date

Successful Responses

31

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

Showing DNS history for 2026-08-27 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
31 2026-08-27 10:00 639234212558002823
62 ms 212.68.60.50
30 2026-08-27 09:43 639234202117531850
126 ms 212.68.60.50
29 2026-08-27 09:25 639234191649612722
56 ms 212.68.60.50
28 2026-08-27 09:08 639234181105879568
145 ms 212.68.60.50
27 2026-08-27 08:51 639234170713214496
110 ms 212.68.60.50
26 2026-08-27 08:33 639234160341037652
156 ms 212.68.60.50
25 2026-08-27 08:16 639234149799404224
130 ms 212.68.60.50
24 2026-08-27 07:59 639234139553286469
139 ms 212.68.60.50
23 2026-08-27 07:05 639234107183588293
127 ms 212.68.60.50
22 2026-08-27 06:48 639234096905435724
117 ms 212.68.60.50
21 2026-08-27 06:31 639234086579410775
3 ms 212.68.60.50
20 2026-08-27 06:13 639234076291157956
147 ms 212.68.60.50
19 2026-08-27 05:56 639234065981939454
4 ms 212.68.60.50
18 2026-08-27 05:39 639234055548642997
119 ms 212.68.60.50
17 2026-08-27 05:22 639234045267979603
146 ms 212.68.60.50
16 2026-08-27 05:05 639234034999717463
129 ms 212.68.60.50
15 2026-08-27 04:47 639234024739225358
2080 ms 212.68.60.50
14 2026-08-27 04:30 639234014311170162
126 ms 212.68.60.50
13 2026-08-27 04:13 639234003806017640
123 ms 212.68.60.50
12 2026-08-27 03:55 639233993356203030
78 ms 212.68.60.50
11 2026-08-27 03:02 639233961301716608
109 ms 212.68.60.50
10 2026-08-27 02:45 639233950834200647
2059 ms 212.68.60.50
9 2026-08-27 02:27 639233940431849026
56 ms 212.68.60.50
8 2026-08-27 02:10 639233930110596398
82 ms 212.68.60.50
7 2026-08-27 01:52 639233919705434540
145 ms 212.68.60.50
6 2026-08-27 01:35 639233909452807845
145 ms 212.68.60.50
5 2026-08-27 01:18 639233899096420820
133 ms 212.68.60.50
4 2026-08-27 01:01 639233888707824939
122 ms 212.68.60.50
3 2026-08-27 00:44 639233878461203802
114 ms 212.68.60.50
2 2026-08-27 00:26 639233868060868209
138 ms 212.68.60.50
1 2026-08-27 00:09 639233857450922991
108 ms 212.68.60.50