DNS response history for ns2.swbell.net

ns2.swbell.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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 134 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.swbell.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

134 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

151.164.11.218

Most recently resolved hosting IP on selected date

Successful Responses

36

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

Showing DNS history for 2026-08-26 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
36 2026-08-26 12:01 639233424567558554
15 ms 151.164.11.218
35 2026-08-26 11:43 639233414056832719
52 ms 151.164.11.218
34 2026-08-26 11:26 639233403515141099
7 ms 151.164.11.218
33 2026-08-26 10:31 639233370841350248
11 ms 151.164.11.218
32 2026-08-26 10:14 639233360361507238
41 ms 151.164.11.218
31 2026-08-26 09:57 639233350067824371
5 ms 151.164.11.218
30 2026-08-26 09:39 639233339545274518
19 ms 151.164.11.218
29 2026-08-26 09:22 639233329214918079
5 ms 151.164.11.218
28 2026-08-26 09:05 639233318749762337
39 ms 151.164.11.218
27 2026-08-26 08:47 639233308387917838
4 ms 151.164.11.218
26 2026-08-26 08:30 639233297961740122
7 ms 151.164.11.218
25 2026-08-26 08:12 639233287487159094
8 ms 151.164.11.218
24 2026-08-26 07:55 639233276995531707
69 ms 151.164.11.218
23 2026-08-26 07:38 639233266521568229
23 ms 151.164.11.218
22 2026-08-26 07:20 639233256081047431
2036 ms 151.164.11.218
21 2026-08-26 06:26 639233223620132921
96 ms 151.164.11.218
20 2026-08-26 06:09 639233213287814244
15 ms 151.164.11.218
19 2026-08-26 05:52 639233202925983161
13 ms 151.164.11.218
18 2026-08-26 05:34 639233192644780696
4 ms 151.164.11.218
17 2026-08-26 05:17 639233182401183833
33 ms 151.164.11.218
16 2026-08-26 05:00 639233172074181051
9 ms 151.164.11.218
15 2026-08-26 04:43 639233161808421455
13 ms 151.164.11.218
14 2026-08-26 04:26 639233151357344052
6 ms 151.164.11.218
13 2026-08-26 04:08 639233141034116946
4 ms 151.164.11.218
12 2026-08-26 03:51 639233130828334142
31 ms 151.164.11.218
11 2026-08-26 03:34 639233120373450007
29 ms 151.164.11.218
10 2026-08-26 03:17 639233110066216193
16 ms 151.164.11.218
9 2026-08-26 02:23 639233078065410564
28 ms 151.164.11.218
8 2026-08-26 02:06 639233067787457832
11 ms 151.164.11.218
7 2026-08-26 01:49 639233057501801162
6 ms 151.164.11.218
6 2026-08-26 01:32 639233047089431703
47 ms 151.164.11.218
5 2026-08-26 01:15 639233036754790688
52 ms 151.164.11.218
4 2026-08-26 00:57 639233026412602472
23 ms 151.164.11.218
3 2026-08-26 00:40 639233016064066127
3 ms 151.164.11.218
2 2026-08-26 00:23 639233005922655772
2011 ms 151.164.11.218
1 2026-08-26 00:06 639232995672256907
19 ms 151.164.11.218