DNS response history for ns2.swiftforgeserver.com

ns2.swiftforgeserver.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 353 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.swiftforgeserver.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

353 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

148.113.171.156

Most recently resolved hosting IP on selected date

Successful Responses

35

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

Showing DNS history for 2026-08-26 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-26 11:52 639233414056832719
229 ms 148.113.171.156
34 2026-08-26 11:35 639233403515141099
251 ms 148.113.171.156
33 2026-08-26 10:40 639233370841350248
221 ms 148.113.171.156
32 2026-08-26 10:23 639233360361507238
2224 ms 148.113.171.156
31 2026-08-26 10:06 639233350067824371
120 ms 148.113.171.156
30 2026-08-26 09:48 639233339545274518
225 ms 148.113.171.156
29 2026-08-26 09:31 639233329214918079
221 ms 148.113.171.156
28 2026-08-26 09:14 639233318749762337
228 ms 148.113.171.156
27 2026-08-26 08:56 639233308387917838
220 ms 148.113.171.156
26 2026-08-26 08:39 639233297961740122
7 ms 148.113.171.156
25 2026-08-26 08:22 639233287487159094
124 ms 148.113.171.156
24 2026-08-26 08:04 639233276995531707
230 ms 148.113.171.156
23 2026-08-26 07:46 639233266521568229
2113 ms 148.113.171.156
22 2026-08-26 07:29 639233256081047431
144 ms 148.113.171.156
21 2026-08-26 06:35 639233223620132921
9 ms 148.113.171.156
20 2026-08-26 06:18 639233213287814244
126 ms 148.113.171.156
19 2026-08-26 06:00 639233202925983161
216 ms 148.113.171.156
18 2026-08-26 05:43 639233192644780696
229 ms 148.113.171.156
17 2026-08-26 05:26 639233182401183833
127 ms 148.113.171.156
16 2026-08-26 05:09 639233172074181051
219 ms 148.113.171.156
15 2026-08-26 04:52 639233161808421455
220 ms 148.113.171.156
14 2026-08-26 04:35 639233151357344052
107 ms 148.113.171.156
13 2026-08-26 04:17 639233141034116946
231 ms 148.113.171.156
12 2026-08-26 04:00 639233130828334142
153 ms 148.113.171.156
11 2026-08-26 03:43 639233120373450007
2120 ms 148.113.171.156
10 2026-08-26 03:26 639233110066216193
217 ms 148.113.171.156
9 2026-08-26 02:32 639233078065410564
217 ms 148.113.171.156
8 2026-08-26 02:15 639233067787457832
155 ms 148.113.171.156
7 2026-08-26 01:58 639233057501801162
217 ms 148.113.171.156
6 2026-08-26 01:41 639233047089431703
223 ms 148.113.171.156
5 2026-08-26 01:24 639233036754790688
217 ms 148.113.171.156
4 2026-08-26 01:06 639233026412602472
231 ms 148.113.171.156
3 2026-08-26 00:49 639233016064066127
218 ms 148.113.171.156
2 2026-08-26 00:32 639233005922655772
223 ms 148.113.171.156
1 2026-08-26 00:15 639232995672256907
125 ms 148.113.171.156