DNS response history for ns2.getspost.com

ns2.getspost.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 327 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.getspost.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

327 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

117.53.155.244

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.getspost.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
320 ms 117.53.155.244
35 2026-08-26 11:54 639233414056832719
320 ms 117.53.155.244
34 2026-08-26 11:36 639233403515141099
328 ms 117.53.155.244
33 2026-08-26 10:42 639233370841350248
327 ms 117.53.155.244
32 2026-08-26 10:24 639233360361507238
328 ms 117.53.155.244
31 2026-08-26 10:07 639233350067824371
337 ms 117.53.155.244
30 2026-08-26 09:50 639233339545274518
335 ms 117.53.155.244
29 2026-08-26 09:32 639233329214918079
389 ms 117.53.155.244
28 2026-08-26 09:15 639233318749762337
341 ms 117.53.155.244
27 2026-08-26 08:58 639233308387917838
339 ms 117.53.155.244
26 2026-08-26 08:40 639233297961740122
320 ms 117.53.155.244
25 2026-08-26 08:23 639233287487159094
322 ms 117.53.155.244
24 2026-08-26 08:05 639233276995531707
328 ms 117.53.155.244
23 2026-08-26 07:48 639233266521568229
332 ms 117.53.155.244
22 2026-08-26 07:30 639233256081047431
322 ms 117.53.155.244
21 2026-08-26 06:36 639233223620132921
320 ms 117.53.155.244
20 2026-08-26 06:19 639233213287814244
352 ms 117.53.155.244
19 2026-08-26 06:02 639233202925983161
177 ms 117.53.155.244
18 2026-08-26 05:45 639233192644780696
335 ms 117.53.155.244
17 2026-08-26 05:27 639233182401183833
4 ms 117.53.155.244
16 2026-08-26 05:11 639233172074181051
332 ms 117.53.155.244
15 2026-08-26 04:53 639233161808421455
319 ms 117.53.155.244
14 2026-08-26 04:36 639233151357344052
333 ms 117.53.155.244
13 2026-08-26 04:19 639233141034116946
326 ms 117.53.155.244
12 2026-08-26 04:02 639233130828334142
645 ms 117.53.155.244
11 2026-08-26 03:44 639233120373450007
319 ms 117.53.155.244
10 2026-08-26 03:27 639233110066216193
351 ms 117.53.155.244
9 2026-08-26 02:34 639233078065410564
372 ms 117.53.155.244
8 2026-08-26 02:17 639233067787457832
328 ms 117.53.155.244
7 2026-08-26 01:59 639233057501801162
321 ms 117.53.155.244
6 2026-08-26 01:42 639233047089431703
339 ms 117.53.155.244
5 2026-08-26 01:25 639233036754790688
316 ms 117.53.155.244
4 2026-08-26 01:08 639233026412602472
319 ms 117.53.155.244
3 2026-08-26 00:50 639233016064066127
318 ms 117.53.155.244
2 2026-08-26 00:33 639233005922655772
332 ms 117.53.155.244
1 2026-08-26 00:16 639232995672256907
318 ms 117.53.155.244