DNS response history for ns1.kidsclub.ltd

ns1.kidsclub.ltd 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-09-01. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 312 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.kidsclub.ltd.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

312 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.130.113.250

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.kidsclub.ltd

Showing DNS history for 2026-09-01 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-09-01 12:29 639238617906743100
177 ms 103.130.113.250
35 2026-09-01 12:12 639238607506044626
177 ms 103.130.113.250
34 2026-09-01 11:54 639238597040761406
175 ms 103.130.113.250
33 2026-09-01 11:37 639238586261546969
485 ms 103.130.113.250
32 2026-09-01 11:19 639238575587642333
4 ms 103.130.113.250
31 2026-09-01 10:24 639238543127398267
545 ms 103.130.113.250
30 2026-09-01 10:07 639238532668234016
363 ms 103.130.113.250
29 2026-09-01 09:50 639238522029321761
5 ms 103.130.113.250
28 2026-09-01 09:32 639238511519050351
4 ms 103.130.113.250
27 2026-09-01 09:14 639238500942239673
3 ms 103.130.113.250
26 2026-09-01 08:57 639238490412377398
176 ms 103.130.113.250
25 2026-09-01 08:39 639238479833203021
171 ms 103.130.113.250
24 2026-09-01 08:21 639238469140507479
181 ms 103.130.113.250
23 2026-09-01 08:04 639238458443560361
177 ms 103.130.113.250
22 2026-09-01 07:46 639238447694851502
367 ms 103.130.113.250
21 2026-09-01 07:28 639238436624109087
363 ms 103.130.113.250
20 2026-09-01 07:09 639238425565611335
358 ms 103.130.113.250
19 2026-09-01 06:14 639238392250222581
566 ms 103.130.113.250
18 2026-09-01 05:55 639238381322537831
369 ms 103.130.113.250
17 2026-09-01 05:37 639238370248186084
363 ms 103.130.113.250
16 2026-09-01 05:19 639238359264687845
361 ms 103.130.113.250
15 2026-09-01 05:01 639238348534621818
369 ms 103.130.113.250
14 2026-09-01 04:43 639238337725739433
358 ms 103.130.113.250
13 2026-09-01 04:24 639238326844749368
471 ms 103.130.113.250
12 2026-09-01 04:06 639238315792024737
403 ms 103.130.113.250
11 2026-09-01 03:48 639238304931064768
364 ms 103.130.113.250
10 2026-09-01 03:30 639238294131483803
364 ms 103.130.113.250
9 2026-09-01 03:12 639238283314985519
365 ms 103.130.113.250
8 2026-09-01 02:54 639238272374093187
364 ms 103.130.113.250
7 2026-09-01 02:00 639238240032549922
366 ms 103.130.113.250
6 2026-09-01 01:42 639238229204177368
364 ms 103.130.113.250
5 2026-09-01 01:24 639238218326150282
363 ms 103.130.113.250
4 2026-09-01 01:06 639238207574700853
620 ms 103.130.113.250
3 2026-09-01 00:48 639238196660283915
373 ms 103.130.113.250
2 2026-09-01 00:29 639238185782358546
366 ms 103.130.113.250
1 2026-09-01 00:11 639238175054391781
347 ms 103.130.113.250