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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 484 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

30

Historical checks stored for this nameserver on selected date

Average Latency

484 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

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

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.osresy.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
30 2026-08-25 10:21 639232492740373468
465 ms 74.206.228.76
29 2026-08-25 10:04 639232482235303141
487 ms 74.206.228.76
28 2026-08-25 09:47 639232471861770303
466 ms 74.206.228.76
27 2026-08-25 09:30 639232461630217327
467 ms 74.206.228.76
26 2026-08-25 09:12 639232451282965990
469 ms 74.206.228.76
25 2026-08-25 08:55 639232440814614938
333 ms 74.206.228.76
24 2026-08-25 08:38 639232430410720425
473 ms 74.206.228.76
23 2026-08-25 08:20 639232420003096185
478 ms 74.206.228.76
22 2026-08-25 08:03 639232409467287444
466 ms 74.206.228.76
21 2026-08-25 07:45 639232399077195997
231 ms 74.206.228.76
20 2026-08-25 07:28 639232388731528337
463 ms 74.206.228.76
19 2026-08-25 07:11 639232378288598612
496 ms 74.206.228.76
18 2026-08-25 06:17 639232346196373643
334 ms 74.206.228.76
17 2026-08-25 06:00 639232336112370741
242 ms 74.206.228.76
16 2026-08-25 05:43 639232326146508970
472 ms 74.206.228.76
15 2026-08-25 05:27 639232316189381720
461 ms 74.206.228.76
14 2026-08-25 05:10 639232306217998913
4115 ms 74.206.228.76
13 2026-08-25 04:54 639232296255744174
5 ms 74.206.228.76
12 2026-08-25 04:37 639232286095760789
460 ms 74.206.228.76
11 2026-08-25 04:20 639232276086186273
230 ms 74.206.228.76
10 2026-08-25 04:03 639232265900986425
457 ms 74.206.228.76
9 2026-08-25 03:46 639232255723518075
3 ms 74.206.228.76
8 2026-08-25 03:29 639232245484452890
469 ms 74.206.228.76
7 2026-08-25 03:12 639232235157175331
233 ms 74.206.228.76
6 2026-08-25 02:19 639232203197189095
337 ms 74.206.228.76
5 2026-08-25 02:02 639232192844564298
235 ms 74.206.228.76
4 2026-08-25 01:44 639232182496008942
234 ms 74.206.228.76
3 2026-08-25 01:27 639232172197053132
230 ms 74.206.228.76
2 2026-08-25 00:34 639232140250307418
231 ms 74.206.228.76
1 2026-08-25 00:17 639232129927860324
477 ms 74.206.228.76