DNS response history for ns2.sfiregroup.com

ns2.sfiregroup.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 34 DNS check records, 34 successful responses, 0 failed responses, and 431 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.sfiregroup.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

431 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.101.91

Most recently resolved hosting IP on selected date

Successful Responses

34

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.sfiregroup.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
34 2026-08-25 12:05 639232556111768563
190 ms 162.240.101.91
33 2026-08-25 11:48 639232545839529039
362 ms 162.240.101.91
32 2026-08-25 11:31 639232535349285207
351 ms 162.240.101.91
31 2026-08-25 11:13 639232524938080723
350 ms 162.240.101.91
30 2026-08-25 10:19 639232492740373468
353 ms 162.240.101.91
29 2026-08-25 10:02 639232482235303141
193 ms 162.240.101.91
28 2026-08-25 09:45 639232471861770303
348 ms 162.240.101.91
27 2026-08-25 09:27 639232461630217327
347 ms 162.240.101.91
26 2026-08-25 09:10 639232451282965990
4 ms 162.240.101.91
25 2026-08-25 08:53 639232440814614938
350 ms 162.240.101.91
24 2026-08-25 08:36 639232430410720425
355 ms 162.240.101.91
23 2026-08-25 08:18 639232420003096185
365 ms 162.240.101.91
22 2026-08-25 08:01 639232409467287444
2174 ms 162.240.101.91
21 2026-08-25 07:43 639232399077195997
354 ms 162.240.101.91
20 2026-08-25 07:26 639232388731528337
206 ms 162.240.101.91
19 2026-08-25 07:09 639232378288598612
356 ms 162.240.101.91
18 2026-08-25 06:15 639232346196373643
3 ms 162.240.101.91
17 2026-08-25 05:58 639232336112370741
344 ms 162.240.101.91
16 2026-08-25 05:42 639232326146508970
2 ms 162.240.101.91
15 2026-08-25 05:25 639232316189381720
347 ms 162.240.101.91
14 2026-08-25 05:08 639232306217998913
2 ms 162.240.101.91
13 2026-08-25 04:52 639232296255744174
343 ms 162.240.101.91
12 2026-08-25 04:35 639232286095760789
2 ms 162.240.101.91
11 2026-08-25 04:18 639232276086186273
206 ms 162.240.101.91
10 2026-08-25 04:01 639232265900986425
4 ms 162.240.101.91
9 2026-08-25 03:44 639232255723518075
2172 ms 162.240.101.91
8 2026-08-25 03:27 639232245484452890
346 ms 162.240.101.91
7 2026-08-25 03:10 639232235157175331
339 ms 162.240.101.91
6 2026-08-25 02:17 639232203197189095
354 ms 162.240.101.91
5 2026-08-25 02:00 639232192844564298
339 ms 162.240.101.91
4 2026-08-25 01:42 639232182496008942
338 ms 162.240.101.91
3 2026-08-25 01:25 639232172197053132
339 ms 162.240.101.91
2 2026-08-25 00:32 639232140250307418
2170 ms 162.240.101.91
1 2026-08-25 00:15 639232129927860324
347 ms 162.240.101.91