DNS response history for ns2.thrivemeup.com

ns2.thrivemeup.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-24. For this date, NameServerHistory found 37 DNS check records, 35 successful responses, 2 failed responses, and 44 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.thrivemeup.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

44 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.180.121.200

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.thrivemeup.com

Showing DNS history for 2026-08-24 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
37 2026-08-24 15:25 639231818080917481
8 ms 38.180.121.200
36 2026-08-24 15:08 639231807961539652
32 ms 38.180.121.200
35 2026-08-24 14:51 639231797631669865
4 ms 38.180.121.200
34 2026-08-24 13:58 639231765923559455
5 ms 38.180.121.200
33 2026-08-24 13:42 639231755868832964
56 ms 38.180.121.200
32 2026-08-24 13:25 639231745628278877
54 ms 38.180.121.200
31 2026-08-24 13:08 639231735407682062
80 ms 38.180.121.200
30 2026-08-24 12:15 639231703815441688
104 ms 38.180.121.200
29 2026-08-24 11:58 639231693747052549
64 ms 38.180.121.200
28 2026-08-24 11:41 639231683712487276
52 ms 38.180.121.200
27 2026-08-24 11:24 639231673513573868
70 ms 38.180.121.200
26 2026-08-24 10:31 639231641791249939
5 ms 38.180.121.200
25 2026-08-24 10:15 639231631866211033
110 ms 38.180.121.200
24 2026-08-24 09:58 639231621644955316
58 ms 38.180.121.200
23 2026-08-24 09:41 639231611478799259
83 ms 38.180.121.200
22 2026-08-24 08:48 639231579923718211
32 ms 38.180.121.200
21 2026-08-24 08:32 639231569810702936
-
20 2026-08-24 08:15 639231559762411619
5 ms 38.180.121.200
19 2026-08-24 07:58 639231549663595407
26 ms 38.180.121.200
18 2026-08-24 07:05 639231518076817246
48 ms 38.180.121.200
17 2026-08-24 06:49 639231508078650885
43 ms 38.180.121.200
16 2026-08-24 06:32 639231498210697093
12 ms 38.180.121.200
15 2026-08-24 06:15 639231488109699360
38 ms 38.180.121.200
14 2026-08-24 05:23 639231456772510692
43 ms 38.180.121.200
13 2026-08-24 05:07 639231447084631185
77 ms 38.180.121.200
12 2026-08-24 04:51 639231437208519473
34 ms 38.180.121.200
11 2026-08-24 04:34 639231427209627490
48 ms 38.180.121.200
10 2026-08-24 03:42 639231395791246644
51 ms 38.180.121.200
9 2026-08-24 03:25 639231386075551458
46 ms 38.180.121.200
8 2026-08-24 03:09 639231376208713791
78 ms 38.180.121.200
7 2026-08-24 02:52 639231366170589276
23 ms 38.180.121.200
6 2026-08-24 02:00 639231334732159368
34 ms 38.180.121.200
5 2026-08-24 01:44 639231325035670078
-
4 2026-08-24 01:27 639231315132253837
10 ms 38.180.121.200
3 2026-08-24 01:10 639231305014280808
29 ms 38.180.121.200
2 2026-08-24 00:18 639231273779380675
13 ms 38.180.121.200
1 2026-08-24 00:02 639231264180839154
73 ms 38.180.121.200