DNS response history for ns1.hotelno5.com

ns1.hotelno5.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 36 DNS check records, 36 successful responses, 0 failed responses, and 293 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 ns1.hotelno5.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

293 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.236.231.47

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 ns1.hotelno5.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
36 2026-08-25 12:41 639232576780683689
401 ms 103.236.231.47
35 2026-08-25 12:23 639232566381512620
407 ms 103.236.231.47
34 2026-08-25 12:06 639232556111768563
253 ms 103.236.231.47
33 2026-08-25 11:49 639232545839529039
399 ms 103.236.231.47
32 2026-08-25 11:31 639232535349285207
196 ms 103.236.231.47
31 2026-08-25 11:14 639232524938080723
405 ms 103.236.231.47
30 2026-08-25 10:20 639232492740373468
197 ms 103.236.231.47
29 2026-08-25 10:03 639232482235303141
230 ms 103.236.231.47
28 2026-08-25 09:46 639232471861770303
4 ms 103.236.231.47
27 2026-08-25 09:28 639232461630217327
420 ms 103.236.231.47
26 2026-08-25 09:11 639232451282965990
402 ms 103.236.231.47
25 2026-08-25 08:54 639232440814614938
197 ms 103.236.231.47
24 2026-08-25 08:37 639232430410720425
397 ms 103.236.231.47
23 2026-08-25 08:19 639232420003096185
209 ms 103.236.231.47
22 2026-08-25 08:02 639232409467287444
393 ms 103.236.231.47
21 2026-08-25 07:44 639232399077195997
193 ms 103.236.231.47
20 2026-08-25 07:27 639232388731528337
192 ms 103.236.231.47
19 2026-08-25 07:10 639232378288598612
404 ms 103.236.231.47
18 2026-08-25 06:16 639232346196373643
407 ms 103.236.231.47
17 2026-08-25 05:59 639232336112370741
389 ms 103.236.231.47
16 2026-08-25 05:42 639232326146508970
391 ms 103.236.231.47
15 2026-08-25 05:26 639232316189381720
393 ms 103.236.231.47
14 2026-08-25 05:09 639232306217998913
348 ms 103.236.231.47
13 2026-08-25 04:53 639232296255744174
203 ms 103.236.231.47
12 2026-08-25 04:36 639232286095760789
197 ms 103.236.231.47
11 2026-08-25 04:19 639232276086186273
400 ms 103.236.231.47
10 2026-08-25 04:02 639232265900986425
200 ms 103.236.231.47
9 2026-08-25 03:45 639232255723518075
403 ms 103.236.231.47
8 2026-08-25 03:28 639232245484452890
393 ms 103.236.231.47
7 2026-08-25 03:11 639232235157175331
194 ms 103.236.231.47
6 2026-08-25 02:18 639232203197189095
386 ms 103.236.231.47
5 2026-08-25 02:01 639232192844564298
342 ms 103.236.231.47
4 2026-08-25 01:43 639232182496008942
388 ms 103.236.231.47
3 2026-08-25 01:26 639232172197053132
197 ms 103.236.231.47
2 2026-08-25 00:33 639232140250307418
9 ms 103.236.231.47
1 2026-08-25 00:16 639232129927860324
3 ms 103.236.231.47