DNS response history for ns1.fireszone.com

ns1.fireszone.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-30. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 354 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.fireszone.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

354 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 12:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.246.18.9

Most recently resolved hosting IP on selected date

Successful Responses

37

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

Showing DNS history for 2026-08-30 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
37 2026-08-30 12:09 639236878057367680
350 ms 103.246.18.9
36 2026-08-30 11:52 639236867916029489
342 ms 103.246.18.9
35 2026-08-30 11:35 639236858088772005
344 ms 103.246.18.9
34 2026-08-30 11:19 639236848158742395
382 ms 103.246.18.9
33 2026-08-30 11:02 639236838137395574
350 ms 103.246.18.9
32 2026-08-30 10:45 639236827967386881
169 ms 103.246.18.9
31 2026-08-30 10:28 639236817708615077
348 ms 103.246.18.9
30 2026-08-30 09:35 639236785770651804
351 ms 103.246.18.9
29 2026-08-30 09:18 639236775820686373
342 ms 103.246.18.9
28 2026-08-30 09:02 639236765768339082
189 ms 103.246.18.9
27 2026-08-30 08:45 639236755602384085
351 ms 103.246.18.9
26 2026-08-30 08:28 639236745600094925
342 ms 103.246.18.9
25 2026-08-30 08:11 639236735311262753
344 ms 103.246.18.9
24 2026-08-30 07:54 639236724996745235
341 ms 103.246.18.9
23 2026-08-30 07:37 639236714839899761
349 ms 103.246.18.9
22 2026-08-30 07:20 639236704748431488
354 ms 103.246.18.9
21 2026-08-30 07:03 639236694430128550
351 ms 103.246.18.9
20 2026-08-30 06:46 639236684143292417
189 ms 103.246.18.9
19 2026-08-30 06:29 639236673972499943
343 ms 103.246.18.9
18 2026-08-30 05:36 639236642126522802
190 ms 103.246.18.9
17 2026-08-30 05:19 639236632183518198
345 ms 103.246.18.9
16 2026-08-30 05:03 639236622289312589
368 ms 103.246.18.9
15 2026-08-30 04:46 639236612490676525
349 ms 103.246.18.9
14 2026-08-30 04:30 639236602582494852
177 ms 103.246.18.9
13 2026-08-30 04:13 639236592511706469
345 ms 103.246.18.9
12 2026-08-30 03:56 639236582441006869
348 ms 103.246.18.9
11 2026-08-30 03:40 639236572478785089
184 ms 103.246.18.9
10 2026-08-30 03:23 639236562556749999
174 ms 103.246.18.9
9 2026-08-30 03:06 639236552353482281
325 ms 103.246.18.9
8 2026-08-30 02:49 639236542188881607
357 ms 103.246.18.9
7 2026-08-30 02:32 639236531885440105
2176 ms 103.246.18.9
6 2026-08-30 01:39 639236499922985383
355 ms 103.246.18.9
5 2026-08-30 01:22 639236489713594431
189 ms 103.246.18.9
4 2026-08-30 01:05 639236479750443901
184 ms 103.246.18.9
3 2026-08-30 00:48 639236469719936375
344 ms 103.246.18.9
2 2026-08-30 00:32 639236459579244885
188 ms 103.246.18.9
1 2026-08-30 00:15 639236449582837549
359 ms 103.246.18.9