DNS response history for ns5.mediatrope.com

ns5.mediatrope.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-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 262 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 ns5.mediatrope.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

262 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.6.241.12

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns5.mediatrope.com

Showing DNS history for 2026-08-25 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
29 2026-08-25 10:03 639232482235303141
182 ms 38.6.241.12
28 2026-08-25 09:45 639232471861770303
335 ms 38.6.241.12
27 2026-08-25 09:28 639232461630217327
330 ms 38.6.241.12
26 2026-08-25 09:11 639232451282965990
322 ms 38.6.241.12
25 2026-08-25 08:53 639232440814614938
187 ms 38.6.241.12
24 2026-08-25 08:36 639232430410720425
193 ms 38.6.241.12
23 2026-08-25 08:19 639232420003096185
211 ms 38.6.241.12
22 2026-08-25 08:01 639232409467287444
207 ms 38.6.241.12
21 2026-08-25 07:44 639232399077195997
202 ms 38.6.241.12
20 2026-08-25 07:26 639232388731528337
184 ms 38.6.241.12
19 2026-08-25 07:09 639232378288598612
326 ms 38.6.241.12
18 2026-08-25 06:15 639232346196373643
317 ms 38.6.241.12
17 2026-08-25 05:59 639232336112370741
175 ms 38.6.241.12
16 2026-08-25 05:42 639232326146508970
174 ms 38.6.241.12
15 2026-08-25 05:25 639232316189381720
325 ms 38.6.241.12
14 2026-08-25 05:09 639232306217998913
326 ms 38.6.241.12
13 2026-08-25 04:52 639232296255744174
325 ms 38.6.241.12
12 2026-08-25 04:35 639232286095760789
327 ms 38.6.241.12
11 2026-08-25 04:18 639232276086186273
317 ms 38.6.241.12
10 2026-08-25 04:02 639232265900986425
322 ms 38.6.241.12
9 2026-08-25 03:45 639232255723518075
310 ms 38.6.241.12
8 2026-08-25 03:28 639232245484452890
163 ms 38.6.241.12
7 2026-08-25 03:11 639232235157175331
318 ms 38.6.241.12
6 2026-08-25 02:17 639232203197189095
172 ms 38.6.241.12
5 2026-08-25 02:00 639232192844564298
333 ms 38.6.241.12
4 2026-08-25 01:43 639232182496008942
166 ms 38.6.241.12
3 2026-08-25 01:26 639232172197053132
324 ms 38.6.241.12
2 2026-08-25 00:32 639232140250307418
318 ms 38.6.241.12
1 2026-08-25 00:15 639232129927860324
195 ms 38.6.241.12