DNS response history for ns2.sfc-team.com

ns2.sfc-team.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 36 DNS check records, 36 successful responses, 0 failed responses, and 500 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.sfc-team.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

500 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

87.106.88.14

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.sfc-team.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
36 2026-08-25 12:32 639232576780683689
26 ms 87.106.88.14
35 2026-08-25 12:15 639232566381512620
2064 ms 87.106.88.14
34 2026-08-25 11:58 639232556111768563
16 ms 87.106.88.14
33 2026-08-25 11:40 639232545839529039
55 ms 87.106.88.14
32 2026-08-25 11:23 639232535349285207
2048 ms 87.106.88.14
31 2026-08-25 11:06 639232524938080723
2022 ms 87.106.88.14
30 2026-08-25 10:12 639232492740373468
139 ms 87.106.88.14
29 2026-08-25 09:55 639232482235303141
44 ms 87.106.88.14
28 2026-08-25 09:37 639232471861770303
63 ms 87.106.88.14
27 2026-08-25 09:20 639232461630217327
2031 ms 87.106.88.14
26 2026-08-25 09:03 639232451282965990
81 ms 87.106.88.14
25 2026-08-25 08:45 639232440814614938
23 ms 87.106.88.14
24 2026-08-25 08:28 639232430410720425
2056 ms 87.106.88.14
23 2026-08-25 08:11 639232420003096185
80 ms 87.106.88.14
22 2026-08-25 07:53 639232409467287444
2028 ms 87.106.88.14
21 2026-08-25 07:36 639232399077195997
70 ms 87.106.88.14
20 2026-08-25 07:19 639232388731528337
142 ms 87.106.88.14
19 2026-08-25 07:01 639232378288598612
49 ms 87.106.88.14
18 2026-08-25 06:08 639232346196373643
58 ms 87.106.88.14
17 2026-08-25 05:51 639232336112370741
58 ms 87.106.88.14
16 2026-08-25 05:34 639232326146508970
44 ms 87.106.88.14
15 2026-08-25 05:18 639232316189381720
41 ms 87.106.88.14
14 2026-08-25 05:01 639232306217998913
49 ms 87.106.88.14
13 2026-08-25 04:45 639232296255744174
139 ms 87.106.88.14
12 2026-08-25 04:28 639232286095760789
22 ms 87.106.88.14
11 2026-08-25 04:11 639232276086186273
2064 ms 87.106.88.14
10 2026-08-25 03:54 639232265900986425
84 ms 87.106.88.14
9 2026-08-25 03:37 639232255723518075
40 ms 87.106.88.14
8 2026-08-25 03:20 639232245484452890
48 ms 87.106.88.14
7 2026-08-25 03:03 639232235157175331
64 ms 87.106.88.14
6 2026-08-25 02:09 639232203197189095
54 ms 87.106.88.14
5 2026-08-25 01:52 639232192844564298
45 ms 87.106.88.14
4 2026-08-25 01:35 639232182496008942
57 ms 87.106.88.14
3 2026-08-25 01:18 639232172197053132
22 ms 87.106.88.14
2 2026-08-25 00:24 639232140250307418
40 ms 87.106.88.14
1 2026-08-25 00:07 639232129927860324
2038 ms 87.106.88.14