DNS response history for ns2.fxxch.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

790 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.160.133

Most recently resolved hosting IP on selected date

Successful Responses

30

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.fxxch.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
30 2026-08-26 09:34 639233329214918079
174 ms 162.240.160.133
29 2026-08-26 09:17 639233318749762337
392 ms 162.240.160.133
28 2026-08-26 08:59 639233308387917838
403 ms 162.240.160.133
27 2026-08-26 08:42 639233297961740122
2188 ms 162.240.160.133
26 2026-08-26 08:24 639233287487159094
378 ms 162.240.160.133
25 2026-08-26 08:07 639233276995531707
10 ms 162.240.160.133
24 2026-08-26 07:49 639233266521568229
331 ms 162.240.160.133
23 2026-08-26 07:32 639233256081047431
4200 ms 162.240.160.133
22 2026-08-26 06:38 639233223620132921
351 ms 162.240.160.133
21 2026-08-26 06:21 639233213287814244
380 ms 162.240.160.133
20 2026-08-26 06:03 639233202925983161
9 ms 162.240.160.133
19 2026-08-26 05:46 639233192644780696
357 ms 162.240.160.133
18 2026-08-26 05:29 639233182401183833
175 ms 162.240.160.133
17 2026-08-26 05:12 639233172074181051
365 ms 162.240.160.133
16 2026-08-26 04:55 639233161808421455
175 ms 162.240.160.133
15 2026-08-26 04:38 639233151357344052
349 ms 162.240.160.133
14 2026-08-26 04:20 639233141034116946
2031 ms 162.240.160.133
13 2026-08-26 04:03 639233130828334142
176 ms 162.240.160.133
12 2026-08-26 03:46 639233120373450007
2352 ms 162.240.160.133
11 2026-08-26 03:29 639233110066216193
175 ms 162.240.160.133
10 2026-08-26 02:35 639233078065410564
346 ms 162.240.160.133
9 2026-08-26 02:18 639233067787457832
2200 ms 162.240.160.133
8 2026-08-26 02:01 639233057501801162
173 ms 162.240.160.133
7 2026-08-26 01:44 639233047089431703
351 ms 162.240.160.133
6 2026-08-26 01:26 639233036754790688
175 ms 162.240.160.133
5 2026-08-26 01:09 639233026412602472
349 ms 162.240.160.133
4 2026-08-26 00:52 639233016064066127
2231 ms 162.240.160.133
3 2026-08-26 00:35 639233005922655772
2222 ms 162.240.160.133
2 2026-08-26 00:18 639232995672256907
349 ms 162.240.160.133
1 2026-08-26 00:01 639232985300872416
348 ms 162.240.160.133