DNS response history for ns2.net-solve.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

522 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.13.40.121

Most recently resolved hosting IP on selected date

Successful Responses

29

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.net-solve.com

Showing DNS history for 2026-08-28 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
29 2026-08-28 12:28 639235163898672622
241 ms 69.13.40.121
28 2026-08-28 11:35 639235132147470568
5 ms 69.13.40.121
27 2026-08-28 11:18 639235121907744088
2007 ms 69.13.40.121
26 2026-08-28 11:01 639235111428014262
244 ms 69.13.40.121
25 2026-08-28 10:43 639235100921813626
2131 ms 69.13.40.121
24 2026-08-28 09:49 639235068670703481
242 ms 69.13.40.121
23 2026-08-28 09:32 639235058337459445
3 ms 69.13.40.121
22 2026-08-28 09:15 639235047825109146
244 ms 69.13.40.121
21 2026-08-28 08:57 639235037383229033
251 ms 69.13.40.121
20 2026-08-28 08:04 639235005619242711
7 ms 69.13.40.121
19 2026-08-28 07:47 639234995310346584
245 ms 69.13.40.121
18 2026-08-28 07:30 639234984946548933
244 ms 69.13.40.121
17 2026-08-28 07:13 639234974608077290
241 ms 69.13.40.121
16 2026-08-28 06:19 639234942529845595
240 ms 69.13.40.121
15 2026-08-28 06:02 639234932259126627
248 ms 69.13.40.121
14 2026-08-28 05:45 639234921916735988
253 ms 69.13.40.121
13 2026-08-28 05:28 639234911470038027
2031 ms 69.13.40.121
12 2026-08-28 04:34 639234879588411654
242 ms 69.13.40.121
11 2026-08-28 04:17 639234869341589104
242 ms 69.13.40.121
10 2026-08-28 04:00 639234859012216675
247 ms 69.13.40.121
9 2026-08-28 03:43 639234848695364934
2175 ms 69.13.40.121
8 2026-08-28 02:50 639234816952458162
239 ms 69.13.40.121
7 2026-08-28 02:33 639234806773081598
239 ms 69.13.40.121
6 2026-08-28 02:16 639234796382955255
249 ms 69.13.40.121
5 2026-08-28 01:58 639234786015782563
3 ms 69.13.40.121
4 2026-08-28 01:05 639234753811917646
2125 ms 69.13.40.121
3 2026-08-28 00:48 639234743739767811
246 ms 69.13.40.121
2 2026-08-28 00:31 639234733372362811
3 ms 69.13.40.121
1 2026-08-28 00:13 639234723048550337
239 ms 69.13.40.121