DNS response history for ns1.centralresidencejelutong.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

380 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.6.198.135

Most recently resolved hosting IP on selected date

Successful Responses

28

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.centralresidencejelutong.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
28 2026-08-26 09:00 639233308387917838
493 ms 103.6.198.135
27 2026-08-26 08:43 639233297961740122
487 ms 103.6.198.135
26 2026-08-26 08:25 639233287487159094
468 ms 103.6.198.135
25 2026-08-26 08:08 639233276995531707
339 ms 103.6.198.135
24 2026-08-26 07:50 639233266521568229
652 ms 103.6.198.135
23 2026-08-26 07:33 639233256081047431
329 ms 103.6.198.135
22 2026-08-26 06:39 639233223620132921
504 ms 103.6.198.135
21 2026-08-26 06:21 639233213287814244
320 ms 103.6.198.135
20 2026-08-26 06:04 639233202925983161
330 ms 103.6.198.135
19 2026-08-26 05:47 639233192644780696
275 ms 103.6.198.135
18 2026-08-26 05:30 639233182401183833
292 ms 103.6.198.135
17 2026-08-26 05:13 639233172074181051
666 ms 103.6.198.135
16 2026-08-26 04:56 639233161808421455
291 ms 103.6.198.135
15 2026-08-26 04:38 639233151357344052
304 ms 103.6.198.135
14 2026-08-26 04:21 639233141034116946
174 ms 103.6.198.135
13 2026-08-26 04:04 639233130828334142
332 ms 103.6.198.135
12 2026-08-26 03:47 639233120373450007
328 ms 103.6.198.135
11 2026-08-26 03:29 639233110066216193
482 ms 103.6.198.135
10 2026-08-26 02:36 639233078065410564
214 ms 103.6.198.135
9 2026-08-26 02:19 639233067787457832
459 ms 103.6.198.135
8 2026-08-26 02:02 639233057501801162
501 ms 103.6.198.135
7 2026-08-26 01:45 639233047089431703
485 ms 103.6.198.135
6 2026-08-26 01:27 639233036754790688
9 ms 103.6.198.135
5 2026-08-26 01:10 639233026412602472
579 ms 103.6.198.135
4 2026-08-26 00:53 639233016064066127
481 ms 103.6.198.135
3 2026-08-26 00:36 639233005922655772
511 ms 103.6.198.135
2 2026-08-26 00:19 639232995672256907
2 ms 103.6.198.135
1 2026-08-26 00:02 639232985300872416
337 ms 103.6.198.135