DNS response history for ns2.ecentry.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

561 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

177.87.136.3

Most recently resolved hosting IP on selected date

Successful Responses

29

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.ecentry.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
29 2026-08-26 09:17 639233318749762337
247 ms 177.87.136.3
28 2026-08-26 09:00 639233308387917838
370 ms 177.87.136.3
27 2026-08-26 08:42 639233297961740122
370 ms 177.87.136.3
26 2026-08-26 08:25 639233287487159094
373 ms 177.87.136.3
25 2026-08-26 08:08 639233276995531707
376 ms 177.87.136.3
24 2026-08-26 07:50 639233266521568229
205 ms 177.87.136.3
23 2026-08-26 07:32 639233256081047431
368 ms 177.87.136.3
22 2026-08-26 06:39 639233223620132921
373 ms 177.87.136.3
21 2026-08-26 06:21 639233213287814244
371 ms 177.87.136.3
20 2026-08-26 06:04 639233202925983161
376 ms 177.87.136.3
19 2026-08-26 05:47 639233192644780696
383 ms 177.87.136.3
18 2026-08-26 05:29 639233182401183833
2247 ms 177.87.136.3
17 2026-08-26 05:13 639233172074181051
372 ms 177.87.136.3
16 2026-08-26 04:55 639233161808421455
374 ms 177.87.136.3
15 2026-08-26 04:38 639233151357344052
365 ms 177.87.136.3
14 2026-08-26 04:21 639233141034116946
372 ms 177.87.136.3
13 2026-08-26 04:04 639233130828334142
373 ms 177.87.136.3
12 2026-08-26 03:46 639233120373450007
371 ms 177.87.136.3
11 2026-08-26 03:29 639233110066216193
625 ms 177.87.136.3
10 2026-08-26 02:36 639233078065410564
2283 ms 177.87.136.3
9 2026-08-26 02:19 639233067787457832
182 ms 177.87.136.3
8 2026-08-26 02:01 639233057501801162
364 ms 177.87.136.3
7 2026-08-26 01:44 639233047089431703
372 ms 177.87.136.3
6 2026-08-26 01:27 639233036754790688
367 ms 177.87.136.3
5 2026-08-26 01:10 639233026412602472
384 ms 177.87.136.3
4 2026-08-26 00:52 639233016064066127
371 ms 177.87.136.3
3 2026-08-26 00:35 639233005922655772
379 ms 177.87.136.3
2 2026-08-26 00:18 639232995672256907
365 ms 177.87.136.3
1 2026-08-26 00:01 639232985300872416
2280 ms 177.87.136.3