DNS response history for dns2.medonline.com

dns2.medonline.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 34 DNS check records, 34 successful responses, 0 failed responses, and 450 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 dns2.medonline.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

450 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.31.118.131

Most recently resolved hosting IP on selected date

Successful Responses

34

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 dns2.medonline.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
34 2026-08-26 10:42 639233370841350248
125 ms 23.31.118.131
33 2026-08-26 10:25 639233360361507238
236 ms 23.31.118.131
32 2026-08-26 10:07 639233350067824371
260 ms 23.31.118.131
31 2026-08-26 09:50 639233339545274518
2153 ms 23.31.118.131
30 2026-08-26 09:33 639233329214918079
127 ms 23.31.118.131
29 2026-08-26 09:15 639233318749762337
159 ms 23.31.118.131
28 2026-08-26 08:58 639233308387917838
158 ms 23.31.118.131
27 2026-08-26 08:41 639233297961740122
238 ms 23.31.118.131
26 2026-08-26 08:23 639233287487159094
158 ms 23.31.118.131
25 2026-08-26 08:06 639233276995531707
245 ms 23.31.118.131
24 2026-08-26 07:48 639233266521568229
2209 ms 23.31.118.131
23 2026-08-26 07:31 639233256081047431
258 ms 23.31.118.131
22 2026-08-26 06:37 639233223620132921
237 ms 23.31.118.131
21 2026-08-26 06:20 639233213287814244
249 ms 23.31.118.131
20 2026-08-26 06:02 639233202925983161
146 ms 23.31.118.131
19 2026-08-26 05:45 639233192644780696
251 ms 23.31.118.131
18 2026-08-26 05:28 639233182401183833
164 ms 23.31.118.131
17 2026-08-26 05:11 639233172074181051
2171 ms 23.31.118.131
16 2026-08-26 04:54 639233161808421455
253 ms 23.31.118.131
15 2026-08-26 04:37 639233151357344052
361 ms 23.31.118.131
14 2026-08-26 04:19 639233141034116946
166 ms 23.31.118.131
13 2026-08-26 04:02 639233130828334142
259 ms 23.31.118.131
12 2026-08-26 03:45 639233120373450007
256 ms 23.31.118.131
11 2026-08-26 03:27 639233110066216193
2203 ms 23.31.118.131
10 2026-08-26 02:34 639233078065410564
142 ms 23.31.118.131
9 2026-08-26 02:17 639233067787457832
250 ms 23.31.118.131
8 2026-08-26 02:00 639233057501801162
263 ms 23.31.118.131
7 2026-08-26 01:43 639233047089431703
237 ms 23.31.118.131
6 2026-08-26 01:25 639233036754790688
243 ms 23.31.118.131
5 2026-08-26 01:08 639233026412602472
242 ms 23.31.118.131
4 2026-08-26 00:51 639233016064066127
254 ms 23.31.118.131
3 2026-08-26 00:34 639233005922655772
239 ms 23.31.118.131
2 2026-08-26 00:17 639232995672256907
118 ms 23.31.118.131
1 2026-08-26 00:00 639232985300872416
266 ms 23.31.118.131