DNS response history for ns2.w3doms.com

ns2.w3doms.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 28 DNS check records, 28 successful responses, 0 failed responses, and 368 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.w3doms.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

368 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

101.53.150.116

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.w3doms.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
28 2026-08-28 11:39 639235132147470568
301 ms 101.53.150.116
27 2026-08-28 11:22 639235121907744088
306 ms 101.53.150.116
26 2026-08-28 11:05 639235111428014262
310 ms 101.53.150.116
25 2026-08-28 10:47 639235100921813626
302 ms 101.53.150.116
24 2026-08-28 09:53 639235068670703481
299 ms 101.53.150.116
23 2026-08-28 09:36 639235058337459445
301 ms 101.53.150.116
22 2026-08-28 09:19 639235047825109146
6 ms 101.53.150.116
21 2026-08-28 09:01 639235037383229033
306 ms 101.53.150.116
20 2026-08-28 08:08 639235005619242711
305 ms 101.53.150.116
19 2026-08-28 07:51 639234995310346584
295 ms 101.53.150.116
18 2026-08-28 07:34 639234984946548933
298 ms 101.53.150.116
17 2026-08-28 07:17 639234974608077290
3 ms 101.53.150.116
16 2026-08-28 06:23 639234942529845595
300 ms 101.53.150.116
15 2026-08-28 06:06 639234932259126627
309 ms 101.53.150.116
14 2026-08-28 05:49 639234921916735988
306 ms 101.53.150.116
13 2026-08-28 05:32 639234911470038027
313 ms 101.53.150.116
12 2026-08-28 04:38 639234879588411654
2163 ms 101.53.150.116
11 2026-08-28 04:21 639234869341589104
299 ms 101.53.150.116
10 2026-08-28 04:04 639234859012216675
297 ms 101.53.150.116
9 2026-08-28 03:47 639234848695364934
295 ms 101.53.150.116
8 2026-08-28 02:54 639234816952458162
308 ms 101.53.150.116
7 2026-08-28 02:37 639234806773081598
297 ms 101.53.150.116
6 2026-08-28 02:20 639234796382955255
301 ms 101.53.150.116
5 2026-08-28 02:02 639234786015782563
301 ms 101.53.150.116
4 2026-08-28 01:09 639234753811917646
301 ms 101.53.150.116
3 2026-08-28 00:52 639234743739767811
883 ms 101.53.150.116
2 2026-08-28 00:35 639234733372362811
298 ms 101.53.150.116
1 2026-08-28 00:17 639234723048550337
298 ms 101.53.150.116