DNS response history for ns2.ejad.com.eg

ns2.ejad.com.eg 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 294 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.ejad.com.eg.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

294 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

148.251.141.99

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.ejad.com.eg

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:34 639232576780683689
14 ms 148.251.141.99
35 2026-08-25 12:17 639232566381512620
180 ms 148.251.141.99
34 2026-08-25 12:00 639232556111768563
359 ms 148.251.141.99
33 2026-08-25 11:43 639232545839529039
67 ms 148.251.141.99
32 2026-08-25 11:25 639232535349285207
188 ms 148.251.141.99
31 2026-08-25 11:08 639232524938080723
69 ms 148.251.141.99
30 2026-08-25 10:14 639232492740373468
194 ms 148.251.141.99
29 2026-08-25 09:57 639232482235303141
1176 ms 148.251.141.99
28 2026-08-25 09:39 639232471861770303
75 ms 148.251.141.99
27 2026-08-25 09:22 639232461630217327
49 ms 148.251.141.99
26 2026-08-25 09:05 639232451282965990
6 ms 148.251.141.99
25 2026-08-25 08:48 639232440814614938
146 ms 148.251.141.99
24 2026-08-25 08:30 639232430410720425
362 ms 148.251.141.99
23 2026-08-25 08:13 639232420003096185
5 ms 148.251.141.99
22 2026-08-25 07:56 639232409467287444
31 ms 148.251.141.99
21 2026-08-25 07:38 639232399077195997
3 ms 148.251.141.99
20 2026-08-25 07:21 639232388731528337
80 ms 148.251.141.99
19 2026-08-25 07:03 639232378288598612
321 ms 148.251.141.99
18 2026-08-25 06:10 639232346196373643
182 ms 148.251.141.99
17 2026-08-25 05:53 639232336112370741
348 ms 148.251.141.99
16 2026-08-25 05:37 639232326146508970
2724 ms 148.251.141.99
15 2026-08-25 05:20 639232316189381720
66 ms 148.251.141.99
14 2026-08-25 05:03 639232306217998913
17 ms 148.251.141.99
13 2026-08-25 04:47 639232296255744174
174 ms 148.251.141.99
12 2026-08-25 04:30 639232286095760789
21 ms 148.251.141.99
11 2026-08-25 04:13 639232276086186273
130 ms 148.251.141.99
10 2026-08-25 03:56 639232265900986425
446 ms 148.251.141.99
9 2026-08-25 03:39 639232255723518075
234 ms 148.251.141.99
8 2026-08-25 03:22 639232245484452890
232 ms 148.251.141.99
7 2026-08-25 03:05 639232235157175331
66 ms 148.251.141.99
6 2026-08-25 02:12 639232203197189095
188 ms 148.251.141.99
5 2026-08-25 01:54 639232192844564298
64 ms 148.251.141.99
4 2026-08-25 01:37 639232182496008942
7 ms 148.251.141.99
3 2026-08-25 01:20 639232172197053132
82 ms 148.251.141.99
2 2026-08-25 00:27 639232140250307418
211 ms 148.251.141.99
1 2026-08-25 00:10 639232129927860324
2076 ms 148.251.141.99