DNS response history for ns2.exactllyweb.com

ns2.exactllyweb.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-30. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 299 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.exactllyweb.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

299 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 08:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.234.116.78

Most recently resolved hosting IP on selected date

Successful Responses

28

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

Showing DNS history for 2026-08-30 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
28 2026-08-30 08:59 639236765768339082
244 ms 103.234.116.78
27 2026-08-30 08:42 639236755602384085
4 ms 103.234.116.78
26 2026-08-30 08:25 639236745600094925
2404 ms 103.234.116.78
25 2026-08-30 08:09 639236735311262753
7 ms 103.234.116.78
24 2026-08-30 07:51 639236724996745235
120 ms 103.234.116.78
23 2026-08-30 07:34 639236714839899761
245 ms 103.234.116.78
22 2026-08-30 07:18 639236704748431488
129 ms 103.234.116.78
21 2026-08-30 07:01 639236694430128550
245 ms 103.234.116.78
20 2026-08-30 06:43 639236684143292417
284 ms 103.234.116.78
19 2026-08-30 06:26 639236673972499943
241 ms 103.234.116.78
18 2026-08-30 05:33 639236642126522802
240 ms 103.234.116.78
17 2026-08-30 05:17 639236632183518198
2141 ms 103.234.116.78
16 2026-08-30 05:00 639236622289312589
238 ms 103.234.116.78
15 2026-08-30 04:43 639236612490676525
122 ms 103.234.116.78
14 2026-08-30 04:27 639236602582494852
6 ms 103.234.116.78
13 2026-08-30 04:11 639236592511706469
249 ms 103.234.116.78
12 2026-08-30 03:54 639236582441006869
240 ms 103.234.116.78
11 2026-08-30 03:37 639236572478785089
3 ms 103.234.116.78
10 2026-08-30 03:20 639236562556749999
240 ms 103.234.116.78
9 2026-08-30 03:04 639236552353482281
120 ms 103.234.116.78
8 2026-08-30 02:47 639236542188881607
2 ms 103.234.116.78
7 2026-08-30 02:30 639236531885440105
244 ms 103.234.116.78
6 2026-08-30 01:36 639236499922985383
239 ms 103.234.116.78
5 2026-08-30 01:19 639236489713594431
3 ms 103.234.116.78
4 2026-08-30 01:03 639236479750443901
4 ms 103.234.116.78
3 2026-08-30 00:46 639236469719936375
3 ms 103.234.116.78
2 2026-08-30 00:29 639236459579244885
120 ms 103.234.116.78
1 2026-08-30 00:12 639236449582837549
244 ms 103.234.116.78