DNS response history for ns.raminglodge.com

ns.raminglodge.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 35 DNS check records, 35 successful responses, 0 failed responses, and 357 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 ns.raminglodge.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

357 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.150.19.107

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns.raminglodge.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
35 2026-08-25 12:24 639232566381512620
368 ms 203.150.19.107
34 2026-08-25 12:06 639232556111768563
386 ms 203.150.19.107
33 2026-08-25 11:49 639232545839529039
365 ms 203.150.19.107
32 2026-08-25 11:32 639232535349285207
364 ms 203.150.19.107
31 2026-08-25 11:14 639232524938080723
388 ms 203.150.19.107
30 2026-08-25 10:21 639232492740373468
210 ms 203.150.19.107
29 2026-08-25 10:04 639232482235303141
386 ms 203.150.19.107
28 2026-08-25 09:46 639232471861770303
368 ms 203.150.19.107
27 2026-08-25 09:29 639232461630217327
380 ms 203.150.19.107
26 2026-08-25 09:12 639232451282965990
366 ms 203.150.19.107
25 2026-08-25 08:54 639232440814614938
384 ms 203.150.19.107
24 2026-08-25 08:37 639232430410720425
375 ms 203.150.19.107
23 2026-08-25 08:20 639232420003096185
290 ms 203.150.19.107
22 2026-08-25 08:02 639232409467287444
369 ms 203.150.19.107
21 2026-08-25 07:45 639232399077195997
364 ms 203.150.19.107
20 2026-08-25 07:27 639232388731528337
368 ms 203.150.19.107
19 2026-08-25 07:10 639232378288598612
383 ms 203.150.19.107
18 2026-08-25 06:16 639232346196373643
535 ms 203.150.19.107
17 2026-08-25 05:59 639232336112370741
366 ms 203.150.19.107
16 2026-08-25 05:43 639232326146508970
365 ms 203.150.19.107
15 2026-08-25 05:26 639232316189381720
209 ms 203.150.19.107
14 2026-08-25 05:10 639232306217998913
249 ms 203.150.19.107
13 2026-08-25 04:53 639232296255744174
366 ms 203.150.19.107
12 2026-08-25 04:36 639232286095760789
368 ms 203.150.19.107
11 2026-08-25 04:19 639232276086186273
367 ms 203.150.19.107
10 2026-08-25 04:03 639232265900986425
379 ms 203.150.19.107
9 2026-08-25 03:46 639232255723518075
366 ms 203.150.19.107
8 2026-08-25 03:29 639232245484452890
367 ms 203.150.19.107
7 2026-08-25 03:11 639232235157175331
368 ms 203.150.19.107
6 2026-08-25 02:18 639232203197189095
261 ms 203.150.19.107
5 2026-08-25 02:01 639232192844564298
383 ms 203.150.19.107
4 2026-08-25 01:44 639232182496008942
372 ms 203.150.19.107
3 2026-08-25 01:26 639232172197053132
364 ms 203.150.19.107
2 2026-08-25 00:33 639232140250307418
321 ms 203.150.19.107
1 2026-08-25 00:16 639232129927860324
376 ms 203.150.19.107