DNS response history for ns2.arbitron.net

ns2.arbitron.net 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 35 DNS check records, 35 successful responses, 0 failed responses, and 492 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.arbitron.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

492 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.40.3.107

Most recently resolved hosting IP on selected date

Successful Responses

35

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.arbitron.net

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
35 2026-08-25 12:11 639232566381512620
28 ms 198.40.3.107
34 2026-08-25 11:54 639232556111768563
2030 ms 198.40.3.107
33 2026-08-25 11:37 639232545839529039
25 ms 198.40.3.107
32 2026-08-25 11:19 639232535349285207
2030 ms 198.40.3.107
31 2026-08-25 11:02 639232524938080723
26 ms 198.40.3.107
30 2026-08-25 10:08 639232492740373468
39 ms 198.40.3.107
29 2026-08-25 09:51 639232482235303141
19 ms 198.40.3.107
28 2026-08-25 09:34 639232471861770303
21 ms 198.40.3.107
27 2026-08-25 09:17 639232461630217327
57 ms 198.40.3.107
26 2026-08-25 08:59 639232451282965990
16 ms 198.40.3.107
25 2026-08-25 08:42 639232440814614938
29 ms 198.40.3.107
24 2026-08-25 08:24 639232430410720425
2026 ms 198.40.3.107
23 2026-08-25 08:07 639232420003096185
36 ms 198.40.3.107
22 2026-08-25 07:50 639232409467287444
2078 ms 198.40.3.107
21 2026-08-25 07:32 639232399077195997
24 ms 198.40.3.107
20 2026-08-25 07:15 639232388731528337
4022 ms 198.40.3.107
19 2026-08-25 06:58 639232378288598612
2038 ms 198.40.3.107
18 2026-08-25 06:04 639232346196373643
21 ms 198.40.3.107
17 2026-08-25 05:47 639232336112370741
66 ms 198.40.3.107
16 2026-08-25 05:31 639232326146508970
36 ms 198.40.3.107
15 2026-08-25 05:14 639232316189381720
24 ms 198.40.3.107
14 2026-08-25 04:57 639232306217998913
24 ms 198.40.3.107
13 2026-08-25 04:41 639232296255744174
38 ms 198.40.3.107
12 2026-08-25 04:24 639232286095760789
38 ms 198.40.3.107
11 2026-08-25 04:07 639232276086186273
32 ms 198.40.3.107
10 2026-08-25 03:50 639232265900986425
21 ms 198.40.3.107
9 2026-08-25 03:33 639232255723518075
40 ms 198.40.3.107
8 2026-08-25 03:16 639232245484452890
25 ms 198.40.3.107
7 2026-08-25 02:59 639232235157175331
84 ms 198.40.3.107
6 2026-08-25 02:06 639232203197189095
18 ms 198.40.3.107
5 2026-08-25 01:48 639232192844564298
21 ms 198.40.3.107
4 2026-08-25 01:31 639232182496008942
23 ms 198.40.3.107
3 2026-08-25 01:14 639232172197053132
134 ms 198.40.3.107
2 2026-08-25 00:21 639232140250307418
2013 ms 198.40.3.107
1 2026-08-25 00:04 639232129927860324
17 ms 198.40.3.107