DNS response history for ns2.web242.com

ns2.web242.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 342 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.web242.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

342 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.225.128.173

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.web242.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:31 639235163898672622
246 ms 67.225.128.173
28 2026-08-28 11:38 639235132147470568
120 ms 67.225.128.173
27 2026-08-28 11:21 639235121907744088
234 ms 67.225.128.173
26 2026-08-28 11:03 639235111428014262
243 ms 67.225.128.173
25 2026-08-28 10:46 639235100921813626
4 ms 67.225.128.173
24 2026-08-28 09:52 639235068670703481
222 ms 67.225.128.173
23 2026-08-28 09:35 639235058337459445
228 ms 67.225.128.173
22 2026-08-28 09:17 639235047825109146
241 ms 67.225.128.173
21 2026-08-28 09:00 639235037383229033
2121 ms 67.225.128.173
20 2026-08-28 08:07 639235005619242711
225 ms 67.225.128.173
19 2026-08-28 07:50 639234995310346584
236 ms 67.225.128.173
18 2026-08-28 07:32 639234984946548933
221 ms 67.225.128.173
17 2026-08-28 07:15 639234974608077290
229 ms 67.225.128.173
16 2026-08-28 06:22 639234942529845595
2122 ms 67.225.128.173
15 2026-08-28 06:05 639234932259126627
244 ms 67.225.128.173
14 2026-08-28 05:47 639234921916735988
253 ms 67.225.128.173
13 2026-08-28 05:30 639234911470038027
228 ms 67.225.128.173
12 2026-08-28 04:37 639234879588411654
221 ms 67.225.128.173
11 2026-08-28 04:20 639234869341589104
221 ms 67.225.128.173
10 2026-08-28 04:03 639234859012216675
237 ms 67.225.128.173
9 2026-08-28 03:45 639234848695364934
229 ms 67.225.128.173
8 2026-08-28 02:52 639234816952458162
230 ms 67.225.128.173
7 2026-08-28 02:36 639234806773081598
219 ms 67.225.128.173
6 2026-08-28 02:18 639234796382955255
221 ms 67.225.128.173
5 2026-08-28 02:01 639234786015782563
238 ms 67.225.128.173
4 2026-08-28 01:07 639234753811917646
236 ms 67.225.128.173
3 2026-08-28 00:50 639234743739767811
226 ms 67.225.128.173
2 2026-08-28 00:33 639234733372362811
2 ms 67.225.128.173
1 2026-08-28 00:16 639234723048550337
231 ms 67.225.128.173