DNS response history for ns2.osresy.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

292 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.206.228.76

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.osresy.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
36 2026-08-28 15:12 639235258803654519
3 ms 74.206.228.76
35 2026-08-28 14:54 639235248596087996
221 ms 74.206.228.76
34 2026-08-28 14:37 639235238225955920
211 ms 74.206.228.76
33 2026-08-28 14:20 639235227727862105
214 ms 74.206.228.76
32 2026-08-28 13:26 639235195230848570
100 ms 74.206.228.76
31 2026-08-28 13:08 639235184840503274
201 ms 74.206.228.76
30 2026-08-28 12:51 639235174453894956
102 ms 74.206.228.76
29 2026-08-28 12:33 639235163898672622
107 ms 74.206.228.76
28 2026-08-28 11:40 639235132147470568
221 ms 74.206.228.76
27 2026-08-28 11:23 639235121907744088
106 ms 74.206.228.76
26 2026-08-28 11:06 639235111428014262
101 ms 74.206.228.76
25 2026-08-28 10:49 639235100921813626
3698 ms 74.206.228.76
24 2026-08-28 09:55 639235068670703481
223 ms 74.206.228.76
23 2026-08-28 09:38 639235058337459445
206 ms 74.206.228.76
22 2026-08-28 09:20 639235047825109146
98 ms 74.206.228.76
21 2026-08-28 09:03 639235037383229033
113 ms 74.206.228.76
20 2026-08-28 08:09 639235005619242711
122 ms 74.206.228.76
19 2026-08-28 07:52 639234995310346584
687 ms 74.206.228.76
18 2026-08-28 07:35 639234984946548933
206 ms 74.206.228.76
17 2026-08-28 07:18 639234974608077290
98 ms 74.206.228.76
16 2026-08-28 06:24 639234942529845595
204 ms 74.206.228.76
15 2026-08-28 06:07 639234932259126627
115 ms 74.206.228.76
14 2026-08-28 05:50 639234921916735988
217 ms 74.206.228.76
13 2026-08-28 05:33 639234911470038027
212 ms 74.206.228.76
12 2026-08-28 04:40 639234879588411654
195 ms 74.206.228.76
11 2026-08-28 04:22 639234869341589104
209 ms 74.206.228.76
10 2026-08-28 04:05 639234859012216675
211 ms 74.206.228.76
9 2026-08-28 03:48 639234848695364934
216 ms 74.206.228.76
8 2026-08-28 02:55 639234816952458162
202 ms 74.206.228.76
7 2026-08-28 02:38 639234806773081598
198 ms 74.206.228.76
6 2026-08-28 02:21 639234796382955255
210 ms 74.206.228.76
5 2026-08-28 02:04 639234786015782563
104 ms 74.206.228.76
4 2026-08-28 01:10 639234753811917646
97 ms 74.206.228.76
3 2026-08-28 00:53 639234743739767811
105 ms 74.206.228.76
2 2026-08-28 00:36 639234733372362811
208 ms 74.206.228.76
1 2026-08-28 00:19 639234723048550337
783 ms 74.206.228.76