DNS response history for ns3.iforced.net

ns3.iforced.net 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 33 DNS check records, 32 successful responses, 1 failed responses, and 277 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 ns3.iforced.net.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

277 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.97.100

Most recently resolved hosting IP on selected date

Successful Responses

32

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns3.iforced.net

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
33 2026-08-25 11:42 639232545839529039
26 ms 185.136.97.100
32 2026-08-25 11:24 639232535349285207
34 ms 185.136.97.100
31 2026-08-25 11:07 639232524938080723
7 ms 185.136.97.100
30 2026-08-25 10:13 639232492740373468
17 ms 185.136.97.100
29 2026-08-25 09:56 639232482235303141
23 ms 185.136.97.100
28 2026-08-25 09:38 639232471861770303
12 ms 185.136.97.100
27 2026-08-25 09:21 639232461630217327
122 ms 185.136.97.100
26 2026-08-25 09:04 639232451282965990
31 ms 185.136.97.100
25 2026-08-25 08:47 639232440814614938
2051 ms 185.136.97.100
24 2026-08-25 08:29 639232430410720425
11 ms 185.136.97.100
23 2026-08-25 08:12 639232420003096185
19 ms 185.136.97.100
22 2026-08-25 07:55 639232409467287444
30 ms 185.136.97.100
21 2026-08-25 07:37 639232399077195997
10 ms 185.136.97.100
20 2026-08-25 07:20 639232388731528337
16 ms 185.136.97.100
19 2026-08-25 07:02 639232378288598612
50 ms 185.136.97.100
18 2026-08-25 06:09 639232346196373643
24 ms 185.136.97.100
17 2026-08-25 05:52 639232336112370741
36 ms 185.136.97.100
16 2026-08-25 05:36 639232326146508970
19 ms 185.136.97.100
15 2026-08-25 05:19 639232316189381720
11 ms 185.136.97.100
14 2026-08-25 05:02 639232306217998913
2009 ms 185.136.97.100
13 2026-08-25 04:46 639232296255744174
15 ms 185.136.97.100
12 2026-08-25 04:29 639232286095760789
28 ms 185.136.97.100
11 2026-08-25 04:12 639232276086186273
2046 ms 185.136.97.100
10 2026-08-25 03:55 639232265900986425
-
9 2026-08-25 03:38 639232255723518075
23 ms 185.136.97.100
8 2026-08-25 03:21 639232245484452890
25 ms 185.136.97.100
7 2026-08-25 03:04 639232235157175331
10 ms 185.136.97.100
6 2026-08-25 02:11 639232203197189095
2044 ms 185.136.97.100
5 2026-08-25 01:53 639232192844564298
19 ms 185.136.97.100
4 2026-08-25 01:36 639232182496008942
9 ms 185.136.97.100
3 2026-08-25 01:19 639232172197053132
9 ms 185.136.97.100
2 2026-08-25 00:26 639232140250307418
53 ms 185.136.97.100
1 2026-08-25 00:08 639232129927860324
13 ms 185.136.97.100