DNS response history for ns2.webedge.org

ns2.webedge.org 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 38 DNS check records, 38 successful responses, 0 failed responses, and 466 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.webedge.org.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

466 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.20.171.225

Most recently resolved hosting IP on selected date

Successful Responses

38

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.webedge.org

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
38 2026-08-25 13:10 639232597643611557
103 ms 198.20.171.225
37 2026-08-25 12:52 639232587225721862
116 ms 198.20.171.225
36 2026-08-25 12:35 639232576780683689
263 ms 198.20.171.225
35 2026-08-25 12:17 639232566381512620
184 ms 198.20.171.225
34 2026-08-25 12:00 639232556111768563
483 ms 198.20.171.225
33 2026-08-25 11:43 639232545839529039
120 ms 198.20.171.225
32 2026-08-25 11:26 639232535349285207
120 ms 198.20.171.225
31 2026-08-25 11:08 639232524938080723
250 ms 198.20.171.225
30 2026-08-25 10:15 639232492740373468
2039 ms 198.20.171.225
29 2026-08-25 09:57 639232482235303141
386 ms 198.20.171.225
28 2026-08-25 09:40 639232471861770303
3606 ms 198.20.171.225
27 2026-08-25 09:23 639232461630217327
131 ms 198.20.171.225
26 2026-08-25 09:06 639232451282965990
282 ms 198.20.171.225
25 2026-08-25 08:48 639232440814614938
122 ms 198.20.171.225
24 2026-08-25 08:31 639232430410720425
119 ms 198.20.171.225
23 2026-08-25 08:14 639232420003096185
259 ms 198.20.171.225
22 2026-08-25 07:56 639232409467287444
124 ms 198.20.171.225
21 2026-08-25 07:39 639232399077195997
464 ms 198.20.171.225
20 2026-08-25 07:21 639232388731528337
221 ms 198.20.171.225
19 2026-08-25 07:04 639232378288598612
23 ms 198.20.171.225
18 2026-08-25 06:11 639232346196373643
235 ms 198.20.171.225
17 2026-08-25 05:54 639232336112370741
32 ms 198.20.171.225
16 2026-08-25 05:37 639232326146508970
256 ms 198.20.171.225
15 2026-08-25 05:20 639232316189381720
149 ms 198.20.171.225
14 2026-08-25 05:04 639232306217998913
216 ms 198.20.171.225
13 2026-08-25 04:47 639232296255744174
219 ms 198.20.171.225
12 2026-08-25 04:30 639232286095760789
3413 ms 198.20.171.225
11 2026-08-25 04:14 639232276086186273
235 ms 198.20.171.225
10 2026-08-25 03:57 639232265900986425
251 ms 198.20.171.225
9 2026-08-25 03:40 639232255723518075
138 ms 198.20.171.225
8 2026-08-25 03:23 639232245484452890
12 ms 198.20.171.225
7 2026-08-25 03:06 639232235157175331
2122 ms 198.20.171.225
6 2026-08-25 02:12 639232203197189095
106 ms 198.20.171.225
5 2026-08-25 01:55 639232192844564298
105 ms 198.20.171.225
4 2026-08-25 01:38 639232182496008942
121 ms 198.20.171.225
3 2026-08-25 01:20 639232172197053132
217 ms 198.20.171.225
2 2026-08-25 00:27 639232140250307418
221 ms 198.20.171.225
1 2026-08-25 00:10 639232129927860324
240 ms 198.20.171.225