DNS response history for ns1.fxevents.live

ns1.fxevents.live 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 242 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.fxevents.live.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

242 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

213.165.230.180

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 ns1.fxevents.live

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:44 639233339545274518
79 ms 213.165.230.180
29 2026-08-26 09:27 639233329214918079
86 ms 213.165.230.180
28 2026-08-26 09:09 639233318749762337
68 ms 213.165.230.180
27 2026-08-26 08:52 639233308387917838
57 ms 213.165.230.180
26 2026-08-26 08:35 639233297961740122
64 ms 213.165.230.180
25 2026-08-26 08:17 639233287487159094
30 ms 213.165.230.180
24 2026-08-26 08:00 639233276995531707
63 ms 213.165.230.180
23 2026-08-26 07:42 639233266521568229
2019 ms 213.165.230.180
22 2026-08-26 07:25 639233256081047431
53 ms 213.165.230.180
21 2026-08-26 06:31 639233223620132921
20 ms 213.165.230.180
20 2026-08-26 06:13 639233213287814244
37 ms 213.165.230.180
19 2026-08-26 05:56 639233202925983161
325 ms 213.165.230.180
18 2026-08-26 05:39 639233192644780696
384 ms 213.165.230.180
17 2026-08-26 05:22 639233182401183833
28 ms 213.165.230.180
16 2026-08-26 05:05 639233172074181051
426 ms 213.165.230.180
15 2026-08-26 04:48 639233161808421455
53 ms 213.165.230.180
14 2026-08-26 04:30 639233151357344052
29 ms 213.165.230.180
13 2026-08-26 04:13 639233141034116946
182 ms 213.165.230.180
12 2026-08-26 03:56 639233130828334142
13 ms 213.165.230.180
11 2026-08-26 03:39 639233120373450007
49 ms 213.165.230.180
10 2026-08-26 03:21 639233110066216193
2011 ms 213.165.230.180
9 2026-08-26 02:28 639233078065410564
279 ms 213.165.230.180
8 2026-08-26 02:11 639233067787457832
43 ms 213.165.230.180
7 2026-08-26 01:54 639233057501801162
48 ms 213.165.230.180
6 2026-08-26 01:36 639233047089431703
15 ms 213.165.230.180
5 2026-08-26 01:19 639233036754790688
158 ms 213.165.230.180
4 2026-08-26 01:02 639233026412602472
179 ms 213.165.230.180
3 2026-08-26 00:45 639233016064066127
174 ms 213.165.230.180
2 2026-08-26 00:28 639233005922655772
274 ms 213.165.230.180
1 2026-08-26 00:11 639232995672256907
29 ms 213.165.230.180