DNS response history for ns2.getsresponse.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

339 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.9.149.17

Most recently resolved hosting IP on selected date

Successful Responses

36

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.getsresponse.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
36 2026-08-26 12:11 639233424567558554
253 ms 72.9.149.17
35 2026-08-26 11:54 639233414056832719
248 ms 72.9.149.17
34 2026-08-26 11:36 639233403515141099
248 ms 72.9.149.17
33 2026-08-26 10:41 639233370841350248
252 ms 72.9.149.17
32 2026-08-26 10:24 639233360361507238
246 ms 72.9.149.17
31 2026-08-26 10:07 639233350067824371
248 ms 72.9.149.17
30 2026-08-26 09:50 639233339545274518
247 ms 72.9.149.17
29 2026-08-26 09:32 639233329214918079
247 ms 72.9.149.17
28 2026-08-26 09:15 639233318749762337
2176 ms 72.9.149.17
27 2026-08-26 08:57 639233308387917838
249 ms 72.9.149.17
26 2026-08-26 08:40 639233297961740122
261 ms 72.9.149.17
25 2026-08-26 08:23 639233287487159094
248 ms 72.9.149.17
24 2026-08-26 08:05 639233276995531707
245 ms 72.9.149.17
23 2026-08-26 07:48 639233266521568229
249 ms 72.9.149.17
22 2026-08-26 07:30 639233256081047431
132 ms 72.9.149.17
21 2026-08-26 06:36 639233223620132921
133 ms 72.9.149.17
20 2026-08-26 06:19 639233213287814244
249 ms 72.9.149.17
19 2026-08-26 06:02 639233202925983161
255 ms 72.9.149.17
18 2026-08-26 05:44 639233192644780696
250 ms 72.9.149.17
17 2026-08-26 05:27 639233182401183833
248 ms 72.9.149.17
16 2026-08-26 05:10 639233172074181051
130 ms 72.9.149.17
15 2026-08-26 04:53 639233161808421455
261 ms 72.9.149.17
14 2026-08-26 04:36 639233151357344052
152 ms 72.9.149.17
13 2026-08-26 04:18 639233141034116946
264 ms 72.9.149.17
12 2026-08-26 04:01 639233130828334142
247 ms 72.9.149.17
11 2026-08-26 03:44 639233120373450007
250 ms 72.9.149.17
10 2026-08-26 03:27 639233110066216193
2120 ms 72.9.149.17
9 2026-08-26 02:34 639233078065410564
247 ms 72.9.149.17
8 2026-08-26 02:16 639233067787457832
248 ms 72.9.149.17
7 2026-08-26 01:59 639233057501801162
270 ms 72.9.149.17
6 2026-08-26 01:42 639233047089431703
179 ms 72.9.149.17
5 2026-08-26 01:25 639233036754790688
255 ms 72.9.149.17
4 2026-08-26 01:08 639233026412602472
129 ms 72.9.149.17
3 2026-08-26 00:50 639233016064066127
254 ms 72.9.149.17
2 2026-08-26 00:33 639233005922655772
256 ms 72.9.149.17
1 2026-08-26 00:16 639232995672256907
255 ms 72.9.149.17