DNS response history for ns2.ejewerly.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

349 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.76.124.29

Most recently resolved hosting IP on selected date

Successful Responses

36

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.ejewerly.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
36 2026-08-25 12:41 639232576780683689
270 ms 31.76.124.29
35 2026-08-25 12:23 639232566381512620
266 ms 31.76.124.29
34 2026-08-25 12:06 639232556111768563
2207 ms 127.0.0.1
33 2026-08-25 11:49 639232545839529039
280 ms 31.76.124.29
32 2026-08-25 11:32 639232535349285207
280 ms 31.76.124.29
31 2026-08-25 11:14 639232524938080723
181 ms 31.76.124.29
30 2026-08-25 10:20 639232492740373468
269 ms 31.76.124.29
29 2026-08-25 10:03 639232482235303141
287 ms 31.76.124.29
28 2026-08-25 09:46 639232471861770303
274 ms 31.76.124.29
27 2026-08-25 09:28 639232461630217327
291 ms 31.76.124.29
26 2026-08-25 09:11 639232451282965990
273 ms 31.76.124.29
25 2026-08-25 08:54 639232440814614938
194 ms 31.76.124.29
24 2026-08-25 08:37 639232430410720425
274 ms 31.76.124.29
23 2026-08-25 08:19 639232420003096185
272 ms 31.76.124.29
22 2026-08-25 08:02 639232409467287444
278 ms 31.76.124.29
21 2026-08-25 07:44 639232399077195997
175 ms 31.76.124.29
20 2026-08-25 07:27 639232388731528337
287 ms 31.76.124.29
19 2026-08-25 07:10 639232378288598612
280 ms 31.76.124.29
18 2026-08-25 06:16 639232346196373643
4 ms 31.76.124.29
17 2026-08-25 05:59 639232336112370741
279 ms 31.76.124.29
16 2026-08-25 05:42 639232326146508970
182 ms 31.76.124.29
15 2026-08-25 05:26 639232316189381720
266 ms 31.76.124.29
14 2026-08-25 05:09 639232306217998913
2200 ms 31.76.124.29
13 2026-08-25 04:53 639232296255744174
268 ms 31.76.124.29
12 2026-08-25 04:36 639232286095760789
4 ms 31.76.124.29
11 2026-08-25 04:19 639232276086186273
263 ms 31.76.124.29
10 2026-08-25 04:02 639232265900986425
269 ms 31.76.124.29
9 2026-08-25 03:45 639232255723518075
176 ms 31.76.124.29
8 2026-08-25 03:28 639232245484452890
271 ms 31.76.124.29
7 2026-08-25 03:11 639232235157175331
264 ms 31.76.124.29
6 2026-08-25 02:18 639232203197189095
269 ms 31.76.124.29
5 2026-08-25 02:01 639232192844564298
285 ms 31.76.124.29
4 2026-08-25 01:43 639232182496008942
269 ms 31.76.124.29
3 2026-08-25 01:26 639232172197053132
263 ms 31.76.124.29
2 2026-08-25 00:33 639232140250307418
209 ms 31.76.124.29
1 2026-08-25 00:16 639232129927860324
174 ms 31.76.124.29