DNS response history for ns2.ronesansesyadepolama.com

ns2.ronesansesyadepolama.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 30 DNS check records, 30 successful responses, 0 failed responses, and 382 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.ronesansesyadepolama.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

382 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.203.117.175

Most recently resolved hosting IP on selected date

Successful Responses

30

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.ronesansesyadepolama.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
30 2026-08-26 09:47 639233339545274518
66 ms 109.203.117.175
29 2026-08-26 09:29 639233329214918079
49 ms 109.203.117.175
28 2026-08-26 09:12 639233318749762337
15 ms 109.203.117.175
27 2026-08-26 08:55 639233308387917838
2045 ms 109.203.117.175
26 2026-08-26 08:38 639233297961740122
46 ms 109.203.117.175
25 2026-08-26 08:20 639233287487159094
33 ms 109.203.117.175
24 2026-08-26 08:03 639233276995531707
51 ms 109.203.117.175
23 2026-08-26 07:45 639233266521568229
46 ms 109.203.117.175
22 2026-08-26 07:28 639233256081047431
57 ms 109.203.117.175
21 2026-08-26 06:34 639233223620132921
46 ms 109.203.117.175
20 2026-08-26 06:16 639233213287814244
48 ms 109.203.117.175
19 2026-08-26 05:59 639233202925983161
131 ms 109.203.117.175
18 2026-08-26 05:42 639233192644780696
26 ms 109.203.117.175
17 2026-08-26 05:25 639233182401183833
51 ms 109.203.117.175
16 2026-08-26 05:08 639233172074181051
51 ms 109.203.117.175
15 2026-08-26 04:51 639233161808421455
43 ms 109.203.117.175
14 2026-08-26 04:33 639233151357344052
2035 ms 109.203.117.175
13 2026-08-26 04:16 639233141034116946
4052 ms 109.203.117.175
12 2026-08-26 03:59 639233130828334142
44 ms 109.203.117.175
11 2026-08-26 03:42 639233120373450007
57 ms 109.203.117.175
10 2026-08-26 03:24 639233110066216193
46 ms 109.203.117.175
9 2026-08-26 02:31 639233078065410564
43 ms 109.203.117.175
8 2026-08-26 02:14 639233067787457832
2044 ms 109.203.117.175
7 2026-08-26 01:57 639233057501801162
44 ms 109.203.117.175
6 2026-08-26 01:39 639233047089431703
42 ms 109.203.117.175
5 2026-08-26 01:22 639233036754790688
47 ms 109.203.117.175
4 2026-08-26 01:05 639233026412602472
79 ms 109.203.117.175
3 2026-08-26 00:48 639233016064066127
55 ms 109.203.117.175
2 2026-08-26 00:31 639233005922655772
44 ms 109.203.117.175
1 2026-08-26 00:14 639232995672256907
9 ms 109.203.117.175