DNS response history for ns2.s4dom.org

ns2.s4dom.org 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 29 DNS check records, 29 successful responses, 0 failed responses, and 481 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.s4dom.org.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

481 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

131.153.159.67

Most recently resolved hosting IP on selected date

Successful Responses

29

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.s4dom.org

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
29 2026-08-26 09:16 639233318749762337
324 ms 131.153.159.67
28 2026-08-26 08:59 639233308387917838
648 ms 131.153.159.67
27 2026-08-26 08:41 639233297961740122
450 ms 131.153.159.67
26 2026-08-26 08:24 639233287487159094
188 ms 131.153.159.67
25 2026-08-26 08:07 639233276995531707
446 ms 131.153.159.67
24 2026-08-26 07:49 639233266521568229
20 ms 131.153.159.67
23 2026-08-26 07:31 639233256081047431
663 ms 131.153.159.67
22 2026-08-26 06:38 639233223620132921
252 ms 131.153.159.67
21 2026-08-26 06:20 639233213287814244
417 ms 131.153.159.67
20 2026-08-26 06:03 639233202925983161
356 ms 131.153.159.67
19 2026-08-26 05:46 639233192644780696
402 ms 131.153.159.67
18 2026-08-26 05:29 639233182401183833
335 ms 131.153.159.67
17 2026-08-26 05:12 639233172074181051
356 ms 131.153.159.67
16 2026-08-26 04:54 639233161808421455
329 ms 131.153.159.67
15 2026-08-26 04:37 639233151357344052
559 ms 131.153.159.67
14 2026-08-26 04:20 639233141034116946
12 ms 131.153.159.67
13 2026-08-26 04:03 639233130828334142
7 ms 131.153.159.67
12 2026-08-26 03:46 639233120373450007
260 ms 131.153.159.67
11 2026-08-26 03:28 639233110066216193
345 ms 131.153.159.67
10 2026-08-26 02:35 639233078065410564
562 ms 131.153.159.67
9 2026-08-26 02:18 639233067787457832
321 ms 131.153.159.67
8 2026-08-26 02:01 639233057501801162
2009 ms 131.153.159.67
7 2026-08-26 01:43 639233047089431703
439 ms 131.153.159.67
6 2026-08-26 01:26 639233036754790688
474 ms 131.153.159.67
5 2026-08-26 01:09 639233026412602472
309 ms 131.153.159.67
4 2026-08-26 00:52 639233016064066127
2324 ms 131.153.159.67
3 2026-08-26 00:34 639233005922655772
328 ms 131.153.159.67
2 2026-08-26 00:17 639232995672256907
256 ms 131.153.159.67
1 2026-08-26 00:00 639232985300872416
568 ms 131.153.159.67