DNS response history for dns2.ramady.me

dns2.ramady.me 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 36 DNS check records, 36 successful responses, 0 failed responses, and 181 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.ramady.me.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

181 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.102.85.104

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 dns2.ramady.me

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
36 2026-08-25 12:36 639232576780683689
112 ms 38.102.85.104
35 2026-08-25 12:19 639232566381512620
20 ms 38.102.85.104
34 2026-08-25 12:02 639232556111768563
127 ms 38.102.85.104
33 2026-08-25 11:45 639232545839529039
31 ms 38.102.85.104
32 2026-08-25 11:27 639232535349285207
118 ms 38.102.85.104
31 2026-08-25 11:10 639232524938080723
539 ms 38.102.85.104
30 2026-08-25 10:16 639232492740373468
16 ms 38.102.85.104
29 2026-08-25 09:59 639232482235303141
303 ms 38.102.85.104
28 2026-08-25 09:41 639232471861770303
32 ms 38.102.85.104
27 2026-08-25 09:24 639232461630217327
2217 ms 38.102.85.104
26 2026-08-25 09:07 639232451282965990
31 ms 38.102.85.104
25 2026-08-25 08:50 639232440814614938
76 ms 38.102.85.104
24 2026-08-25 08:32 639232430410720425
35 ms 38.102.85.104
23 2026-08-25 08:15 639232420003096185
216 ms 38.102.85.104
22 2026-08-25 07:58 639232409467287444
239 ms 38.102.85.104
21 2026-08-25 07:40 639232399077195997
242 ms 38.102.85.104
20 2026-08-25 07:23 639232388731528337
115 ms 38.102.85.104
19 2026-08-25 07:05 639232378288598612
243 ms 38.102.85.104
18 2026-08-25 06:12 639232346196373643
59 ms 38.102.85.104
17 2026-08-25 05:55 639232336112370741
134 ms 38.102.85.104
16 2026-08-25 05:38 639232326146508970
20 ms 38.102.85.104
15 2026-08-25 05:22 639232316189381720
148 ms 38.102.85.104
14 2026-08-25 05:05 639232306217998913
157 ms 38.102.85.104
13 2026-08-25 04:49 639232296255744174
45 ms 38.102.85.104
12 2026-08-25 04:32 639232286095760789
201 ms 38.102.85.104
11 2026-08-25 04:15 639232276086186273
21 ms 38.102.85.104
10 2026-08-25 03:58 639232265900986425
137 ms 38.102.85.104
9 2026-08-25 03:41 639232255723518075
19 ms 38.102.85.104
8 2026-08-25 03:24 639232245484452890
121 ms 38.102.85.104
7 2026-08-25 03:07 639232235157175331
34 ms 38.102.85.104
6 2026-08-25 02:14 639232203197189095
29 ms 38.102.85.104
5 2026-08-25 01:56 639232192844564298
15 ms 38.102.85.104
4 2026-08-25 01:39 639232182496008942
596 ms 38.102.85.104
3 2026-08-25 01:22 639232172197053132
29 ms 38.102.85.104
2 2026-08-25 00:28 639232140250307418
13 ms 38.102.85.104
1 2026-08-25 00:11 639232129927860324
20 ms 38.102.85.104