DNS response history for ns2.netedgetechnology.com

ns2.netedgetechnology.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 115 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.netedgetechnology.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

115 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.75.164.150

Most recently resolved hosting IP on selected date

Successful Responses

35

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

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:06 639234253963286387
58 ms 109.75.164.150
34 2026-08-27 10:49 639234243654907465
15 ms 109.75.164.150
33 2026-08-27 10:32 639234233269654413
79 ms 109.75.164.150
32 2026-08-27 10:15 639234222943951923
230 ms 109.75.164.150
31 2026-08-27 09:57 639234212558002823
19 ms 109.75.164.150
30 2026-08-27 09:40 639234202117531850
28 ms 109.75.164.150
29 2026-08-27 09:22 639234191649612722
60 ms 109.75.164.150
28 2026-08-27 09:05 639234181105879568
96 ms 109.75.164.150
27 2026-08-27 08:48 639234170713214496
2031 ms 109.75.164.150
26 2026-08-27 08:30 639234160341037652
55 ms 109.75.164.150
25 2026-08-27 08:13 639234149799404224
7 ms 109.75.164.150
24 2026-08-27 07:56 639234139553286469
64 ms 109.75.164.150
23 2026-08-27 07:02 639234107183588293
78 ms 109.75.164.150
22 2026-08-27 06:44 639234096905435724
57 ms 109.75.164.150
21 2026-08-27 06:27 639234086579410775
78 ms 109.75.164.150
20 2026-08-27 06:10 639234076291157956
82 ms 109.75.164.150
19 2026-08-27 05:53 639234065981939454
28 ms 109.75.164.150
18 2026-08-27 05:36 639234055548642997
78 ms 109.75.164.150
17 2026-08-27 05:19 639234045267979603
35 ms 109.75.164.150
16 2026-08-27 05:01 639234034999717463
46 ms 109.75.164.150
15 2026-08-27 04:44 639234024739225358
76 ms 109.75.164.150
14 2026-08-27 04:27 639234014311170162
57 ms 109.75.164.150
13 2026-08-27 04:09 639234003806017640
46 ms 109.75.164.150
12 2026-08-27 03:52 639233993356203030
81 ms 109.75.164.150
11 2026-08-27 02:59 639233961301716608
10 ms 109.75.164.150
10 2026-08-27 02:41 639233950834200647
56 ms 109.75.164.150
9 2026-08-27 02:24 639233940431849026
29 ms 109.75.164.150
8 2026-08-27 02:07 639233930110596398
31 ms 109.75.164.150
7 2026-08-27 01:49 639233919705434540
59 ms 109.75.164.150
6 2026-08-27 01:32 639233909452807845
42 ms 109.75.164.150
5 2026-08-27 01:15 639233899096420820
90 ms 109.75.164.150
4 2026-08-27 00:58 639233888707824939
82 ms 109.75.164.150
3 2026-08-27 00:40 639233878461203802
30 ms 109.75.164.150
2 2026-08-27 00:23 639233868060868209
87 ms 109.75.164.150
1 2026-08-27 00:05 639233857450922991
27 ms 109.75.164.150