DNS response history for ns2.ipforge.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

245 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

98.123.145.134

Most recently resolved hosting IP on selected date

Successful Responses

31

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.ipforge.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
31 2026-08-27 10:01 639234212558002823
251 ms 98.123.145.134
30 2026-08-27 09:44 639234202117531850
35 ms 98.123.145.134
29 2026-08-27 09:26 639234191649612722
248 ms 98.123.145.134
28 2026-08-27 09:09 639234181105879568
118 ms 98.123.145.134
27 2026-08-27 08:52 639234170713214496
127 ms 98.123.145.134
26 2026-08-27 08:34 639234160341037652
155 ms 98.123.145.134
25 2026-08-27 08:17 639234149799404224
121 ms 98.123.145.134
24 2026-08-27 08:00 639234139553286469
255 ms 98.123.145.134
23 2026-08-27 07:06 639234107183588293
176 ms 98.123.145.134
22 2026-08-27 06:49 639234096905435724
245 ms 98.123.145.134
21 2026-08-27 06:31 639234086579410775
247 ms 98.123.145.134
20 2026-08-27 06:14 639234076291157956
127 ms 98.123.145.134
19 2026-08-27 05:57 639234065981939454
220 ms 98.123.145.134
18 2026-08-27 05:40 639234055548642997
235 ms 98.123.145.134
17 2026-08-27 05:22 639234045267979603
174 ms 98.123.145.134
16 2026-08-27 05:06 639234034999717463
9 ms 98.123.145.134
15 2026-08-27 04:48 639234024739225358
2124 ms 98.123.145.134
14 2026-08-27 04:31 639234014311170162
148 ms 98.123.145.134
13 2026-08-27 04:14 639234003806017640
138 ms 98.123.145.134
12 2026-08-27 03:56 639233993356203030
241 ms 98.123.145.134
11 2026-08-27 03:03 639233961301716608
242 ms 98.123.145.134
10 2026-08-27 02:45 639233950834200647
226 ms 98.123.145.134
9 2026-08-27 02:28 639233940431849026
144 ms 98.123.145.134
8 2026-08-27 02:11 639233930110596398
219 ms 98.123.145.134
7 2026-08-27 01:53 639233919705434540
216 ms 98.123.145.134
6 2026-08-27 01:36 639233909452807845
109 ms 98.123.145.134
5 2026-08-27 01:19 639233899096420820
225 ms 98.123.145.134
4 2026-08-27 01:02 639233888707824939
228 ms 98.123.145.134
3 2026-08-27 00:45 639233878461203802
140 ms 98.123.145.134
2 2026-08-27 00:27 639233868060868209
235 ms 98.123.145.134
1 2026-08-27 00:10 639233857450922991
221 ms 98.123.145.134