DNS response history for ns2.loudsaas.com

ns2.loudsaas.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 27 DNS check records, 27 successful responses, 0 failed responses, and 397 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.loudsaas.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

397 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.40.48

Most recently resolved hosting IP on selected date

Successful Responses

27

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.loudsaas.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
27 2026-08-26 08:42 639233297961740122
142 ms 129.121.40.48
26 2026-08-26 08:25 639233287487159094
142 ms 129.121.40.48
25 2026-08-26 08:08 639233276995531707
141 ms 129.121.40.48
24 2026-08-26 07:50 639233266521568229
431 ms 129.121.40.48
23 2026-08-26 07:32 639233256081047431
430 ms 129.121.40.48
22 2026-08-26 06:38 639233223620132921
419 ms 129.121.40.48
21 2026-08-26 06:21 639233213287814244
142 ms 129.121.40.48
20 2026-08-26 06:04 639233202925983161
430 ms 129.121.40.48
19 2026-08-26 05:47 639233192644780696
253 ms 129.121.40.48
18 2026-08-26 05:29 639233182401183833
423 ms 129.121.40.48
17 2026-08-26 05:13 639233172074181051
425 ms 129.121.40.48
16 2026-08-26 04:55 639233161808421455
524 ms 129.121.40.48
15 2026-08-26 04:38 639233151357344052
425 ms 129.121.40.48
14 2026-08-26 04:21 639233141034116946
141 ms 129.121.40.48
13 2026-08-26 04:04 639233130828334142
443 ms 129.121.40.48
12 2026-08-26 03:46 639233120373450007
424 ms 129.121.40.48
11 2026-08-26 03:29 639233110066216193
426 ms 129.121.40.48
10 2026-08-26 02:36 639233078065410564
426 ms 129.121.40.48
9 2026-08-26 02:19 639233067787457832
417 ms 129.121.40.48
8 2026-08-26 02:01 639233057501801162
420 ms 129.121.40.48
7 2026-08-26 01:44 639233047089431703
147 ms 129.121.40.48
6 2026-08-26 01:27 639233036754790688
138 ms 129.121.40.48
5 2026-08-26 01:10 639233026412602472
2293 ms 129.121.40.48
4 2026-08-26 00:52 639233016064066127
434 ms 129.121.40.48
3 2026-08-26 00:35 639233005922655772
141 ms 129.121.40.48
2 2026-08-26 00:18 639232995672256907
415 ms 129.121.40.48
1 2026-08-26 00:01 639232985300872416
139 ms 129.121.40.48