DNS response history for ns2.good-fire-training.org

ns2.good-fire-training.org 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 30 DNS check records, 30 successful responses, 0 failed responses, and 752 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.good-fire-training.org.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

752 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.75.235

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.good-fire-training.org

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
30 2026-08-25 10:17 639232492740373468
213 ms 129.121.75.235
29 2026-08-25 10:00 639232482235303141
105 ms 129.121.75.235
28 2026-08-25 09:42 639232471861770303
322 ms 129.121.75.235
27 2026-08-25 09:25 639232461630217327
101 ms 129.121.75.235
26 2026-08-25 09:08 639232451282965990
243 ms 129.121.75.235
25 2026-08-25 08:50 639232440814614938
253 ms 129.121.75.235
24 2026-08-25 08:33 639232430410720425
101 ms 129.121.75.235
23 2026-08-25 08:16 639232420003096185
464 ms 129.121.75.235
22 2026-08-25 07:58 639232409467287444
2244 ms 129.121.75.235
21 2026-08-25 07:41 639232399077195997
212 ms 129.121.75.235
20 2026-08-25 07:24 639232388731528337
9 ms 129.121.75.235
19 2026-08-25 07:06 639232378288598612
102 ms 129.121.75.235
18 2026-08-25 06:13 639232346196373643
383 ms 129.121.75.235
17 2026-08-25 05:56 639232336112370741
107 ms 129.121.75.235
16 2026-08-25 05:39 639232326146508970
102 ms 129.121.75.235
15 2026-08-25 05:23 639232316189381720
2100 ms 129.121.75.235
14 2026-08-25 05:06 639232306217998913
477 ms 129.121.75.235
13 2026-08-25 04:49 639232296255744174
211 ms 129.121.75.235
12 2026-08-25 04:32 639232286095760789
2099 ms 129.121.75.235
11 2026-08-25 04:16 639232276086186273
210 ms 129.121.75.235
10 2026-08-25 03:59 639232265900986425
4610 ms 129.121.75.235
9 2026-08-25 03:42 639232255723518075
101 ms 129.121.75.235
8 2026-08-25 03:25 639232245484452890
2203 ms 129.121.75.235
7 2026-08-25 03:08 639232235157175331
2241 ms 129.121.75.235
6 2026-08-25 02:14 639232203197189095
109 ms 129.121.75.235
5 2026-08-25 01:57 639232192844564298
206 ms 129.121.75.235
4 2026-08-25 01:40 639232182496008942
210 ms 129.121.75.235
3 2026-08-25 01:23 639232172197053132
2176 ms 129.121.75.235
2 2026-08-25 00:29 639232140250307418
432 ms 129.121.75.235
1 2026-08-25 00:12 639232129927860324
200 ms 129.121.75.235