DNS response history for ns2.networkteam.com

ns2.networkteam.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-27. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 272 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.networkteam.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

272 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.51.17.255

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

Showing DNS history for 2026-08-27 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-27 11:59 639234286253196126
27 ms 212.51.17.255
35 2026-08-27 11:05 639234253963286387
70 ms 212.51.17.255
34 2026-08-27 10:48 639234243654907465
2011 ms 212.51.17.255
33 2026-08-27 10:31 639234233269654413
92 ms 212.51.17.255
32 2026-08-27 10:14 639234222943951923
69 ms 212.51.17.255
31 2026-08-27 09:56 639234212558002823
26 ms 212.51.17.255
30 2026-08-27 09:39 639234202117531850
76 ms 212.51.17.255
29 2026-08-27 09:22 639234191649612722
45 ms 212.51.17.255
28 2026-08-27 09:04 639234181105879568
9 ms 212.51.17.255
27 2026-08-27 08:47 639234170713214496
43 ms 212.51.17.255
26 2026-08-27 08:29 639234160341037652
56 ms 212.51.17.255
25 2026-08-27 08:12 639234149799404224
142 ms 212.51.17.255
24 2026-08-27 07:55 639234139553286469
46 ms 212.51.17.255
23 2026-08-27 07:01 639234107183588293
47 ms 212.51.17.255
22 2026-08-27 06:44 639234096905435724
64 ms 212.51.17.255
21 2026-08-27 06:27 639234086579410775
53 ms 212.51.17.255
20 2026-08-27 06:09 639234076291157956
74 ms 212.51.17.255
19 2026-08-27 05:52 639234065981939454
51 ms 212.51.17.255
18 2026-08-27 05:35 639234055548642997
42 ms 212.51.17.255
17 2026-08-27 05:18 639234045267979603
64 ms 212.51.17.255
16 2026-08-27 05:01 639234034999717463
50 ms 212.51.17.255
15 2026-08-27 04:43 639234024739225358
47 ms 212.51.17.255
14 2026-08-27 04:26 639234014311170162
105 ms 212.51.17.255
13 2026-08-27 04:09 639234003806017640
42 ms 212.51.17.255
12 2026-08-27 03:51 639233993356203030
60 ms 212.51.17.255
11 2026-08-27 02:58 639233961301716608
2041 ms 212.51.17.255
10 2026-08-27 02:40 639233950834200647
2068 ms 212.51.17.255
9 2026-08-27 02:23 639233940431849026
2032 ms 212.51.17.255
8 2026-08-27 02:06 639233930110596398
39 ms 212.51.17.255
7 2026-08-27 01:48 639233919705434540
28 ms 212.51.17.255
6 2026-08-27 01:31 639233909452807845
15 ms 212.51.17.255
5 2026-08-27 01:14 639233899096420820
7 ms 212.51.17.255
4 2026-08-27 00:57 639233888707824939
58 ms 212.51.17.255
3 2026-08-27 00:40 639233878461203802
23 ms 212.51.17.255
2 2026-08-27 00:22 639233868060868209
22 ms 212.51.17.255
1 2026-08-27 00:05 639233857450922991
49 ms 212.51.17.255