DNS response history for ns.face2fire.com

ns.face2fire.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-27. For this date, NameServerHistory found 35 DNS check records, 34 successful responses, 1 failed responses, and 110 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 ns.face2fire.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

110 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

146.255.98.166

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns.face2fire.com

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:08 639234253963286387
62 ms 146.255.98.166
34 2026-08-27 10:50 639234243654907465
58 ms 146.255.98.166
33 2026-08-27 10:33 639234233269654413
55 ms 146.255.98.166
32 2026-08-27 10:16 639234222943951923
21 ms 146.255.98.166
31 2026-08-27 09:59 639234212558002823
57 ms 146.255.98.166
30 2026-08-27 09:41 639234202117531850
55 ms 146.255.98.166
29 2026-08-27 09:24 639234191649612722
58 ms 146.255.98.166
28 2026-08-27 09:06 639234181105879568
41 ms 146.255.98.166
27 2026-08-27 08:49 639234170713214496
-
26 2026-08-27 08:32 639234160341037652
64 ms 146.255.98.166
25 2026-08-27 08:14 639234149799404224
55 ms 146.255.98.166
24 2026-08-27 07:57 639234139553286469
40 ms 146.255.98.166
23 2026-08-27 07:03 639234107183588293
43 ms 146.255.98.166
22 2026-08-27 06:46 639234096905435724
139 ms 146.255.98.166
21 2026-08-27 06:29 639234086579410775
9 ms 146.255.98.166
20 2026-08-27 06:12 639234076291157956
67 ms 146.255.98.166
19 2026-08-27 05:55 639234065981939454
61 ms 146.255.98.166
18 2026-08-27 05:37 639234055548642997
54 ms 146.255.98.166
17 2026-08-27 05:20 639234045267979603
50 ms 146.255.98.166
16 2026-08-27 05:03 639234034999717463
57 ms 146.255.98.166
15 2026-08-27 04:46 639234024739225358
21 ms 146.255.98.166
14 2026-08-27 04:28 639234014311170162
46 ms 146.255.98.166
13 2026-08-27 04:11 639234003806017640
38 ms 146.255.98.166
12 2026-08-27 03:53 639233993356203030
38 ms 146.255.98.166
11 2026-08-27 03:00 639233961301716608
42 ms 146.255.98.166
10 2026-08-27 02:43 639233950834200647
59 ms 146.255.98.166
9 2026-08-27 02:25 639233940431849026
49 ms 146.255.98.166
8 2026-08-27 02:08 639233930110596398
54 ms 146.255.98.166
7 2026-08-27 01:51 639233919705434540
58 ms 146.255.98.166
6 2026-08-27 01:34 639233909452807845
2085 ms 146.255.98.166
5 2026-08-27 01:16 639233899096420820
58 ms 146.255.98.166
4 2026-08-27 00:59 639233888707824939
29 ms 146.255.98.166
3 2026-08-27 00:42 639233878461203802
75 ms 146.255.98.166
2 2026-08-27 00:25 639233868060868209
38 ms 146.255.98.166
1 2026-08-27 00:07 639233857450922991
13 ms 146.255.98.166