DNS response history for ns2.expressdir.com

ns2.expressdir.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 37 DNS check records, 36 successful responses, 1 failed responses, and 211 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.expressdir.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

211 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.134.180.210

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.expressdir.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
37 2026-08-26 12:21 639233434974187439
32 ms 91.134.180.210
36 2026-08-26 12:04 639233424567558554
2026 ms 91.134.180.210
35 2026-08-26 11:46 639233414056832719
2033 ms 91.134.180.210
34 2026-08-26 11:29 639233403515141099
47 ms 91.134.180.210
33 2026-08-26 10:34 639233370841350248
60 ms 91.134.180.210
32 2026-08-26 10:17 639233360361507238
45 ms 91.134.180.210
31 2026-08-26 10:00 639233350067824371
17 ms 91.134.180.210
30 2026-08-26 09:42 639233339545274518
35 ms 91.134.180.210
29 2026-08-26 09:25 639233329214918079
61 ms 91.134.180.210
28 2026-08-26 09:08 639233318749762337
20 ms 91.134.180.210
27 2026-08-26 08:50 639233308387917838
75 ms 91.134.180.210
26 2026-08-26 08:33 639233297961740122
38 ms 91.134.180.210
25 2026-08-26 08:16 639233287487159094
45 ms 91.134.180.210
24 2026-08-26 07:58 639233276995531707
13 ms 91.134.180.210
23 2026-08-26 07:41 639233266521568229
49 ms 91.134.180.210
22 2026-08-26 07:23 639233256081047431
59 ms 91.134.180.210
21 2026-08-26 06:29 639233223620132921
48 ms 91.134.180.210
20 2026-08-26 06:12 639233213287814244
37 ms 91.134.180.210
19 2026-08-26 05:55 639233202925983161
29 ms 91.134.180.210
18 2026-08-26 05:37 639233192644780696
24 ms 91.134.180.210
17 2026-08-26 05:20 639233182401183833
31 ms 91.134.180.210
16 2026-08-26 05:03 639233172074181051
166 ms 91.134.180.210
15 2026-08-26 04:46 639233161808421455
65 ms 91.134.180.210
14 2026-08-26 04:29 639233151357344052
34 ms 91.134.180.210
13 2026-08-26 04:11 639233141034116946
54 ms 91.134.180.210
12 2026-08-26 03:54 639233130828334142
44 ms 91.134.180.210
11 2026-08-26 03:37 639233120373450007
29 ms 91.134.180.210
10 2026-08-26 03:20 639233110066216193
2021 ms 91.134.180.210
9 2026-08-26 02:26 639233078065410564
35 ms 91.134.180.210
8 2026-08-26 02:09 639233067787457832
-
7 2026-08-26 01:52 639233057501801162
51 ms 91.134.180.210
6 2026-08-26 01:35 639233047089431703
54 ms 91.134.180.210
5 2026-08-26 01:18 639233036754790688
33 ms 91.134.180.210
4 2026-08-26 01:00 639233026412602472
60 ms 91.134.180.210
3 2026-08-26 00:43 639233016064066127
35 ms 91.134.180.210
2 2026-08-26 00:26 639233005922655772
31 ms 91.134.180.210
1 2026-08-26 00:09 639232995672256907
54 ms 91.134.180.210