DNS response history for ns2.ez2post.com

ns2.ez2post.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-25. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 207 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.ez2post.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

207 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.114.113.116

Most recently resolved hosting IP on selected date

Successful Responses

26

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

Showing DNS history for 2026-08-25 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
26 2026-08-25 09:09 639232451282965990
221 ms 167.114.113.116
25 2026-08-25 08:52 639232440814614938
220 ms 167.114.113.116
24 2026-08-25 08:34 639232430410720425
234 ms 167.114.113.116
23 2026-08-25 08:17 639232420003096185
240 ms 167.114.113.116
22 2026-08-25 08:00 639232409467287444
214 ms 167.114.113.116
21 2026-08-25 07:42 639232399077195997
220 ms 167.114.113.116
20 2026-08-25 07:25 639232388731528337
235 ms 167.114.113.116
19 2026-08-25 07:07 639232378288598612
238 ms 167.114.113.116
18 2026-08-25 06:14 639232346196373643
222 ms 167.114.113.116
17 2026-08-25 05:57 639232336112370741
217 ms 167.114.113.116
16 2026-08-25 05:40 639232326146508970
276 ms 167.114.113.116
15 2026-08-25 05:24 639232316189381720
275 ms 167.114.113.116
14 2026-08-25 05:07 639232306217998913
237 ms 167.114.113.116
13 2026-08-25 04:50 639232296255744174
240 ms 167.114.113.116
12 2026-08-25 04:34 639232286095760789
113 ms 167.114.113.116
11 2026-08-25 04:17 639232276086186273
225 ms 167.114.113.116
10 2026-08-25 04:00 639232265900986425
218 ms 167.114.113.116
9 2026-08-25 03:43 639232255723518075
231 ms 167.114.113.116
8 2026-08-25 03:26 639232245484452890
126 ms 167.114.113.116
7 2026-08-25 03:09 639232235157175331
111 ms 167.114.113.116
6 2026-08-25 02:15 639232203197189095
146 ms 167.114.113.116
5 2026-08-25 01:58 639232192844564298
237 ms 167.114.113.116
4 2026-08-25 01:41 639232182496008942
227 ms 167.114.113.116
3 2026-08-25 01:24 639232172197053132
108 ms 167.114.113.116
2 2026-08-25 00:30 639232140250307418
133 ms 167.114.113.116
1 2026-08-25 00:14 639232129927860324
226 ms 167.114.113.116