DNS response history for ns1.forextradinglivenews.com

ns1.forextradinglivenews.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 252 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.forextradinglivenews.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

252 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.192.25.205

Most recently resolved hosting IP on selected date

Successful Responses

36

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.forextradinglivenews.com

Showing DNS history for 2026-08-25 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
36 2026-08-25 12:25 639232566381512620
156 ms 199.192.25.205
35 2026-08-25 12:08 639232556111768563
304 ms 199.192.25.205
34 2026-08-25 11:51 639232545839529039
300 ms 199.192.25.205
33 2026-08-25 11:34 639232535349285207
149 ms 199.192.25.205
32 2026-08-25 11:16 639232524938080723
312 ms 199.192.25.205
31 2026-08-25 10:22 639232492740373468
159 ms 199.192.25.205
30 2026-08-25 10:05 639232482235303141
158 ms 199.192.25.205
29 2026-08-25 09:48 639232471861770303
144 ms 199.192.25.205
28 2026-08-25 09:30 639232461630217327
144 ms 199.192.25.205
27 2026-08-25 09:13 639232451282965990
326 ms 199.192.25.205
26 2026-08-25 08:56 639232440814614938
329 ms 199.192.25.205
25 2026-08-25 08:39 639232430410720425
313 ms 199.192.25.205
24 2026-08-25 08:21 639232420003096185
299 ms 199.192.25.205
23 2026-08-25 08:04 639232409467287444
154 ms 199.192.25.205
22 2026-08-25 07:46 639232399077195997
292 ms 199.192.25.205
21 2026-08-25 07:29 639232388731528337
308 ms 199.192.25.205
20 2026-08-25 07:12 639232378288598612
308 ms 199.192.25.205
19 2026-08-25 06:18 639232346196373643
318 ms 199.192.25.205
18 2026-08-25 06:01 639232336112370741
304 ms 199.192.25.205
17 2026-08-25 05:44 639232326146508970
155 ms 199.192.25.205
16 2026-08-25 05:28 639232316189381720
317 ms 199.192.25.205
15 2026-08-25 05:11 639232306217998913
4 ms 199.192.25.205
14 2026-08-25 04:54 639232296255744174
300 ms 199.192.25.205
13 2026-08-25 04:38 639232286095760789
305 ms 199.192.25.205
12 2026-08-25 04:21 639232276086186273
150 ms 199.192.25.205
11 2026-08-25 04:04 639232265900986425
310 ms 199.192.25.205
10 2026-08-25 03:47 639232255723518075
154 ms 199.192.25.205
9 2026-08-25 03:30 639232245484452890
295 ms 199.192.25.205
8 2026-08-25 03:13 639232235157175331
309 ms 199.192.25.205
7 2026-08-25 02:20 639232203197189095
156 ms 199.192.25.205
6 2026-08-25 02:03 639232192844564298
320 ms 199.192.25.205
5 2026-08-25 01:45 639232182496008942
322 ms 199.192.25.205
4 2026-08-25 01:28 639232172197053132
294 ms 199.192.25.205
3 2026-08-25 00:34 639232140250307418
304 ms 199.192.25.205
2 2026-08-25 00:18 639232129927860324
297 ms 199.192.25.205
1 2026-08-25 00:00 639232119551972438
316 ms 199.192.25.205