DNS response history for ns2.expressservice.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

297 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.220.122.170

Most recently resolved hosting IP on selected date

Successful Responses

33

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.expressservice.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
33 2026-08-26 10:34 639233370841350248
2047 ms 158.220.122.170
32 2026-08-26 10:17 639233360361507238
66 ms 158.220.122.170
31 2026-08-26 10:00 639233350067824371
60 ms 158.220.122.170
30 2026-08-26 09:42 639233339545274518
65 ms 158.220.122.170
29 2026-08-26 09:25 639233329214918079
38 ms 158.220.122.170
28 2026-08-26 09:07 639233318749762337
31 ms 158.220.122.170
27 2026-08-26 08:50 639233308387917838
69 ms 158.220.122.170
26 2026-08-26 08:33 639233297961740122
87 ms 158.220.122.170
25 2026-08-26 08:15 639233287487159094
46 ms 158.220.122.170
24 2026-08-26 07:58 639233276995531707
38 ms 158.220.122.170
23 2026-08-26 07:40 639233266521568229
64 ms 158.220.122.170
22 2026-08-26 07:23 639233256081047431
47 ms 158.220.122.170
21 2026-08-26 06:29 639233223620132921
7 ms 158.220.122.170
20 2026-08-26 06:12 639233213287814244
85 ms 158.220.122.170
19 2026-08-26 05:54 639233202925983161
68 ms 158.220.122.170
18 2026-08-26 05:37 639233192644780696
81 ms 158.220.122.170
17 2026-08-26 05:20 639233182401183833
71 ms 158.220.122.170
16 2026-08-26 05:03 639233172074181051
63 ms 158.220.122.170
15 2026-08-26 04:46 639233161808421455
2031 ms 158.220.122.170
14 2026-08-26 04:28 639233151357344052
65 ms 158.220.122.170
13 2026-08-26 04:11 639233141034116946
52 ms 158.220.122.170
12 2026-08-26 03:54 639233130828334142
117 ms 158.220.122.170
11 2026-08-26 03:37 639233120373450007
55 ms 158.220.122.170
10 2026-08-26 03:20 639233110066216193
2028 ms 158.220.122.170
9 2026-08-26 02:26 639233078065410564
42 ms 158.220.122.170
8 2026-08-26 02:09 639233067787457832
131 ms 158.220.122.170
7 2026-08-26 01:52 639233057501801162
34 ms 158.220.122.170
6 2026-08-26 01:35 639233047089431703
2008 ms 158.220.122.170
5 2026-08-26 01:17 639233036754790688
30 ms 158.220.122.170
4 2026-08-26 01:00 639233026412602472
34 ms 158.220.122.170
3 2026-08-26 00:43 639233016064066127
53 ms 158.220.122.170
2 2026-08-26 00:26 639233005922655772
46 ms 158.220.122.170
1 2026-08-26 00:09 639232995672256907
39 ms 158.220.122.170