DNS response history for ns2.osocial.media

ns2.osocial.media 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 30 DNS check records, 30 successful responses, 0 failed responses, and 313 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.osocial.media.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

313 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

54.39.233.170

Most recently resolved hosting IP on selected date

Successful Responses

30

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.osocial.media

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
30 2026-08-25 10:14 639232492740373468
105 ms 54.39.233.170
29 2026-08-25 09:57 639232482235303141
77 ms 54.39.233.170
28 2026-08-25 09:39 639232471861770303
98 ms 54.39.233.170
27 2026-08-25 09:22 639232461630217327
500 ms 54.39.233.170
26 2026-08-25 09:05 639232451282965990
2087 ms 54.39.233.170
25 2026-08-25 08:48 639232440814614938
341 ms 54.39.233.170
24 2026-08-25 08:30 639232430410720425
2019 ms 54.39.233.170
23 2026-08-25 08:13 639232420003096185
61 ms 54.39.233.170
22 2026-08-25 07:55 639232409467287444
119 ms 54.39.233.170
21 2026-08-25 07:38 639232399077195997
90 ms 54.39.233.170
20 2026-08-25 07:21 639232388731528337
51 ms 54.39.233.170
19 2026-08-25 07:03 639232378288598612
103 ms 54.39.233.170
18 2026-08-25 06:10 639232346196373643
106 ms 54.39.233.170
17 2026-08-25 05:53 639232336112370741
3 ms 54.39.233.170
16 2026-08-25 05:36 639232326146508970
168 ms 54.39.233.170
15 2026-08-25 05:20 639232316189381720
109 ms 54.39.233.170
14 2026-08-25 05:03 639232306217998913
119 ms 54.39.233.170
13 2026-08-25 04:47 639232296255744174
86 ms 54.39.233.170
12 2026-08-25 04:30 639232286095760789
2078 ms 54.39.233.170
11 2026-08-25 04:13 639232276086186273
90 ms 54.39.233.170
10 2026-08-25 03:56 639232265900986425
42 ms 54.39.233.170
9 2026-08-25 03:39 639232255723518075
192 ms 54.39.233.170
8 2026-08-25 03:22 639232245484452890
59 ms 54.39.233.170
7 2026-08-25 03:05 639232235157175331
96 ms 54.39.233.170
6 2026-08-25 02:11 639232203197189095
187 ms 54.39.233.170
5 2026-08-25 01:54 639232192844564298
58 ms 54.39.233.170
4 2026-08-25 01:37 639232182496008942
81 ms 54.39.233.170
3 2026-08-25 01:20 639232172197053132
82 ms 54.39.233.170
2 2026-08-25 00:26 639232140250307418
103 ms 54.39.233.170
1 2026-08-25 00:09 639232129927860324
88 ms 54.39.233.170