DNS response history for ns2.firmstep.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

257 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.28.210.163

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.firmstep.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
30 2026-08-27 09:39 639234202117531850
33 ms 52.28.210.163
29 2026-08-27 09:22 639234191649612722
186 ms 52.28.210.163
28 2026-08-27 09:04 639234181105879568
2053 ms 52.28.210.163
27 2026-08-27 08:47 639234170713214496
58 ms 52.28.210.163
26 2026-08-27 08:29 639234160341037652
61 ms 52.28.210.163
25 2026-08-27 08:12 639234149799404224
43 ms 52.28.210.163
24 2026-08-27 07:55 639234139553286469
35 ms 52.28.210.163
23 2026-08-27 07:01 639234107183588293
60 ms 52.28.210.163
22 2026-08-27 06:44 639234096905435724
10 ms 52.28.210.163
21 2026-08-27 06:27 639234086579410775
73 ms 52.28.210.163
20 2026-08-27 06:09 639234076291157956
107 ms 52.28.210.163
19 2026-08-27 05:52 639234065981939454
70 ms 52.28.210.163
18 2026-08-27 05:35 639234055548642997
9 ms 52.28.210.163
17 2026-08-27 05:18 639234045267979603
42 ms 52.28.210.163
16 2026-08-27 05:01 639234034999717463
71 ms 52.28.210.163
15 2026-08-27 04:44 639234024739225358
12 ms 52.28.210.163
14 2026-08-27 04:26 639234014311170162
30 ms 52.28.210.163
13 2026-08-27 04:09 639234003806017640
67 ms 52.28.210.163
12 2026-08-27 03:51 639233993356203030
44 ms 52.28.210.163
11 2026-08-27 02:58 639233961301716608
96 ms 52.28.210.163
10 2026-08-27 02:41 639233950834200647
57 ms 52.28.210.163
9 2026-08-27 02:23 639233940431849026
69 ms 52.28.210.163
8 2026-08-27 02:06 639233930110596398
86 ms 52.28.210.163
7 2026-08-27 01:48 639233919705434540
50 ms 52.28.210.163
6 2026-08-27 01:31 639233909452807845
2148 ms 52.28.210.163
5 2026-08-27 01:14 639233899096420820
15 ms 52.28.210.163
4 2026-08-27 00:57 639233888707824939
62 ms 52.28.210.163
3 2026-08-27 00:40 639233878461203802
20 ms 52.28.210.163
2 2026-08-27 00:22 639233868060868209
30 ms 52.28.210.163
1 2026-08-27 00:05 639233857450922991
2016 ms 52.28.210.163