History for ns2.expressparti.com

Domain: expressparti.com • Tracking since 2026-08-04 23:25 UTC

DNS response history for ns2.expressparti.com

ns2.expressparti.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-30. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 163 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.expressparti.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

163 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.111.111.48

Most recently resolved hosting IP on selected date

Successful Responses

37

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

Showing DNS history for 2026-08-30 UTC. Newest records appear first.

Today Previous Next

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-30 12:02 639236878057367680
168 ms 78.111.111.48
36 2026-08-30 11:45 639236867916029489
79 ms 78.111.111.48
35 2026-08-30 11:28 639236858088772005
83 ms 78.111.111.48
34 2026-08-30 11:11 639236848158742395
65 ms 78.111.111.48
33 2026-08-30 10:55 639236838137395574
8 ms 78.111.111.48
32 2026-08-30 10:38 639236827967386881
51 ms 78.111.111.48
31 2026-08-30 10:21 639236817708615077
85 ms 78.111.111.48
30 2026-08-30 09:28 639236785770651804
76 ms 78.111.111.48
29 2026-08-30 09:11 639236775820686373
89 ms 78.111.111.48
28 2026-08-30 08:54 639236765768339082
53 ms 78.111.111.48
27 2026-08-30 08:37 639236755602384085
8 ms 78.111.111.48
26 2026-08-30 08:21 639236745600094925
2 ms 78.111.111.48
25 2026-08-30 08:04 639236735311262753
77 ms 78.111.111.48
24 2026-08-30 07:46 639236724996745235
2011 ms 78.111.111.48
23 2026-08-30 07:29 639236714839899761
4 ms 78.111.111.48
22 2026-08-30 07:13 639236704748431488
89 ms 78.111.111.48
21 2026-08-30 06:55 639236694430128550
5 ms 78.111.111.48
20 2026-08-30 06:38 639236684143292417
95 ms 78.111.111.48
19 2026-08-30 06:21 639236673972499943
2011 ms 78.111.111.48
18 2026-08-30 05:28 639236642126522802
101 ms 78.111.111.48
17 2026-08-30 05:12 639236632183518198
81 ms 78.111.111.48
16 2026-08-30 04:55 639236622289312589
62 ms 78.111.111.48
15 2026-08-30 04:39 639236612490676525
62 ms 78.111.111.48
14 2026-08-30 04:22 639236602582494852
9 ms 78.111.111.48
13 2026-08-30 04:06 639236592511706469
73 ms 78.111.111.48
12 2026-08-30 03:49 639236582441006869
82 ms 78.111.111.48
11 2026-08-30 03:32 639236572478785089
20 ms 78.111.111.48
10 2026-08-30 03:16 639236562556749999
4 ms 78.111.111.48
9 2026-08-30 02:59 639236552353482281
37 ms 78.111.111.48
8 2026-08-30 02:42 639236542188881607
8 ms 78.111.111.48
7 2026-08-30 02:25 639236531885440105
84 ms 78.111.111.48
6 2026-08-30 01:31 639236499922985383
10 ms 78.111.111.48
5 2026-08-30 01:14 639236489713594431
2 ms 78.111.111.48
4 2026-08-30 00:58 639236479750443901
54 ms 78.111.111.48
3 2026-08-30 00:41 639236469719936375
127 ms 78.111.111.48
2 2026-08-30 00:24 639236459579244885
73 ms 78.111.111.48
1 2026-08-30 00:07 639236449582837549
81 ms 78.111.111.48