DNS response history for ns2.connectrservice.com

ns2.connectrservice.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-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 88 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.connectrservice.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

88 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.46.122.50

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

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:17 639232566381512620
84 ms 37.46.122.50
34 2026-08-25 12:00 639232556111768563
95 ms 37.46.122.50
33 2026-08-25 11:43 639232545839529039
69 ms 37.46.122.50
32 2026-08-25 11:26 639232535349285207
57 ms 37.46.122.50
31 2026-08-25 11:08 639232524938080723
84 ms 37.46.122.50
30 2026-08-25 10:14 639232492740373468
139 ms 37.46.122.50
29 2026-08-25 09:57 639232482235303141
140 ms 37.46.122.50
28 2026-08-25 09:40 639232471861770303
64 ms 37.46.122.50
27 2026-08-25 09:23 639232461630217327
72 ms 37.46.122.50
26 2026-08-25 09:06 639232451282965990
66 ms 37.46.122.50
25 2026-08-25 08:48 639232440814614938
52 ms 37.46.122.50
24 2026-08-25 08:31 639232430410720425
107 ms 37.46.122.50
23 2026-08-25 08:13 639232420003096185
103 ms 37.46.122.50
22 2026-08-25 07:56 639232409467287444
106 ms 37.46.122.50
21 2026-08-25 07:39 639232399077195997
117 ms 37.46.122.50
20 2026-08-25 07:21 639232388731528337
65 ms 37.46.122.50
19 2026-08-25 07:04 639232378288598612
57 ms 37.46.122.50
18 2026-08-25 06:10 639232346196373643
52 ms 37.46.122.50
17 2026-08-25 05:54 639232336112370741
125 ms 37.46.122.50
16 2026-08-25 05:37 639232326146508970
130 ms 37.46.122.50
15 2026-08-25 05:20 639232316189381720
124 ms 37.46.122.50
14 2026-08-25 05:04 639232306217998913
165 ms 37.46.122.50
13 2026-08-25 04:47 639232296255744174
83 ms 37.46.122.50
12 2026-08-25 04:30 639232286095760789
113 ms 37.46.122.50
11 2026-08-25 04:13 639232276086186273
104 ms 37.46.122.50
10 2026-08-25 03:57 639232265900986425
81 ms 37.46.122.50
9 2026-08-25 03:40 639232255723518075
156 ms 37.46.122.50
8 2026-08-25 03:23 639232245484452890
73 ms 37.46.122.50
7 2026-08-25 03:05 639232235157175331
61 ms 37.46.122.50
6 2026-08-25 02:12 639232203197189095
45 ms 37.46.122.50
5 2026-08-25 01:55 639232192844564298
78 ms 37.46.122.50
4 2026-08-25 01:38 639232182496008942
61 ms 37.46.122.50
3 2026-08-25 01:20 639232172197053132
67 ms 37.46.122.50
2 2026-08-25 00:27 639232140250307418
10 ms 37.46.122.50
1 2026-08-25 00:10 639232129927860324
62 ms 37.46.122.50