DNS response history for ns2.getconnectedbeselected.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

328 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 14:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.179.207.233

Most recently resolved hosting IP on selected date

Successful Responses

34

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.getconnectedbeselected.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
34 2026-08-28 14:30 639235238225955920
6 ms 108.179.207.233
33 2026-08-28 14:12 639235227727862105
298 ms 108.179.207.233
32 2026-08-28 13:18 639235195230848570
7 ms 108.179.207.233
31 2026-08-28 13:01 639235184840503274
8 ms 108.179.207.233
30 2026-08-28 12:44 639235174453894956
274 ms 108.179.207.233
29 2026-08-28 12:26 639235163898672622
279 ms 108.179.207.233
28 2026-08-28 11:33 639235132147470568
289 ms 108.179.207.233
27 2026-08-28 11:16 639235121907744088
4159 ms 108.179.207.233
26 2026-08-28 10:59 639235111428014262
301 ms 108.179.207.233
25 2026-08-28 10:41 639235100921813626
8 ms 108.179.207.233
24 2026-08-28 09:47 639235068670703481
269 ms 108.179.207.233
23 2026-08-28 09:30 639235058337459445
276 ms 108.179.207.233
22 2026-08-28 09:13 639235047825109146
272 ms 108.179.207.233
21 2026-08-28 08:55 639235037383229033
278 ms 108.179.207.233
20 2026-08-28 08:02 639235005619242711
281 ms 108.179.207.233
19 2026-08-28 07:45 639234995310346584
133 ms 108.179.207.233
18 2026-08-28 07:28 639234984946548933
44 ms 108.179.207.233
17 2026-08-28 07:11 639234974608077290
138 ms 108.179.207.233
16 2026-08-28 06:17 639234942529845595
168 ms 108.179.207.233
15 2026-08-28 06:00 639234932259126627
164 ms 108.179.207.233
14 2026-08-28 05:43 639234921916735988
273 ms 108.179.207.233
13 2026-08-28 05:26 639234911470038027
272 ms 108.179.207.233
12 2026-08-28 04:32 639234879588411654
292 ms 108.179.207.233
11 2026-08-28 04:15 639234869341589104
268 ms 108.179.207.233
10 2026-08-28 03:58 639234859012216675
271 ms 108.179.207.233
9 2026-08-28 03:41 639234848695364934
283 ms 108.179.207.233
8 2026-08-28 02:48 639234816952458162
233 ms 108.179.207.233
7 2026-08-28 02:31 639234806773081598
239 ms 108.179.207.233
6 2026-08-28 02:14 639234796382955255
280 ms 108.179.207.233
5 2026-08-28 01:56 639234786015782563
235 ms 108.179.207.233
4 2026-08-28 01:03 639234753811917646
236 ms 108.179.207.233
3 2026-08-28 00:46 639234743739767811
242 ms 108.179.207.233
2 2026-08-28 00:29 639234733372362811
148 ms 108.179.207.233
1 2026-08-28 00:11 639234723048550337
240 ms 108.179.207.233