DNS response history for ns2.s4c.kids

ns2.s4c.kids 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 427 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.s4c.kids.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

427 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.232.215.213

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 ns2.s4c.kids

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 08:59 639233308387917838
2261 ms 192.232.215.213
27 2026-08-26 08:42 639233297961740122
384 ms 192.232.215.213
26 2026-08-26 08:24 639233287487159094
528 ms 192.232.215.213
25 2026-08-26 08:07 639233276995531707
190 ms 192.232.215.213
24 2026-08-26 07:49 639233266521568229
482 ms 192.232.215.213
23 2026-08-26 07:32 639233256081047431
176 ms 192.232.215.213
22 2026-08-26 06:38 639233223620132921
2009 ms 192.232.215.213
21 2026-08-26 06:21 639233213287814244
188 ms 192.232.215.213
20 2026-08-26 06:03 639233202925983161
176 ms 192.232.215.213
19 2026-08-26 05:46 639233192644780696
377 ms 192.232.215.213
18 2026-08-26 05:29 639233182401183833
178 ms 192.232.215.213
17 2026-08-26 05:12 639233172074181051
349 ms 192.232.215.213
16 2026-08-26 04:55 639233161808421455
359 ms 192.232.215.213
15 2026-08-26 04:37 639233151357344052
471 ms 192.232.215.213
14 2026-08-26 04:20 639233141034116946
468 ms 192.232.215.213
13 2026-08-26 04:03 639233130828334142
7 ms 192.232.215.213
12 2026-08-26 03:46 639233120373450007
193 ms 192.232.215.213
11 2026-08-26 03:28 639233110066216193
474 ms 192.232.215.213
10 2026-08-26 02:35 639233078065410564
174 ms 192.232.215.213
9 2026-08-26 02:18 639233067787457832
173 ms 192.232.215.213
8 2026-08-26 02:01 639233057501801162
175 ms 192.232.215.213
7 2026-08-26 01:44 639233047089431703
376 ms 192.232.215.213
6 2026-08-26 01:26 639233036754790688
361 ms 192.232.215.213
5 2026-08-26 01:09 639233026412602472
174 ms 192.232.215.213
4 2026-08-26 00:52 639233016064066127
177 ms 192.232.215.213
3 2026-08-26 00:35 639233005922655772
422 ms 192.232.215.213
2 2026-08-26 00:18 639232995672256907
173 ms 192.232.215.213
1 2026-08-26 00:01 639232985300872416
471 ms 192.232.215.213