DNS response history for ns2.y2s.net

ns2.y2s.net 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 35 DNS check records, 35 successful responses, 0 failed responses, and 520 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.y2s.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

520 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.229.33.245

Most recently resolved hosting IP on selected date

Successful Responses

35

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.y2s.net

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
35 2026-08-25 12:07 639232556111768563
527 ms 202.229.33.245
34 2026-08-25 11:50 639232545839529039
525 ms 202.229.33.245
33 2026-08-25 11:33 639232535349285207
526 ms 202.229.33.245
32 2026-08-25 11:15 639232524938080723
537 ms 202.229.33.245
31 2026-08-25 10:22 639232492740373468
527 ms 202.229.33.245
30 2026-08-25 10:05 639232482235303141
531 ms 202.229.33.245
29 2026-08-25 09:47 639232471861770303
526 ms 202.229.33.245
28 2026-08-25 09:30 639232461630217327
524 ms 202.229.33.245
27 2026-08-25 09:13 639232451282965990
523 ms 202.229.33.245
26 2026-08-25 08:55 639232440814614938
533 ms 202.229.33.245
25 2026-08-25 08:38 639232430410720425
525 ms 202.229.33.245
24 2026-08-25 08:21 639232420003096185
533 ms 202.229.33.245
23 2026-08-25 08:03 639232409467287444
524 ms 202.229.33.245
22 2026-08-25 07:46 639232399077195997
528 ms 202.229.33.245
21 2026-08-25 07:28 639232388731528337
522 ms 202.229.33.245
20 2026-08-25 07:11 639232378288598612
526 ms 202.229.33.245
19 2026-08-25 06:17 639232346196373643
526 ms 202.229.33.245
18 2026-08-25 06:00 639232336112370741
525 ms 202.229.33.245
17 2026-08-25 05:44 639232326146508970
522 ms 202.229.33.245
16 2026-08-25 05:27 639232316189381720
521 ms 202.229.33.245
15 2026-08-25 05:11 639232306217998913
519 ms 202.229.33.245
14 2026-08-25 04:54 639232296255744174
523 ms 202.229.33.245
13 2026-08-25 04:37 639232286095760789
525 ms 202.229.33.245
12 2026-08-25 04:20 639232276086186273
520 ms 202.229.33.245
11 2026-08-25 04:04 639232265900986425
524 ms 202.229.33.245
10 2026-08-25 03:47 639232255723518075
522 ms 202.229.33.245
9 2026-08-25 03:30 639232245484452890
527 ms 202.229.33.245
8 2026-08-25 03:12 639232235157175331
292 ms 202.229.33.245
7 2026-08-25 02:19 639232203197189095
523 ms 202.229.33.245
6 2026-08-25 02:02 639232192844564298
524 ms 202.229.33.245
5 2026-08-25 01:45 639232182496008942
533 ms 202.229.33.245
4 2026-08-25 01:27 639232172197053132
525 ms 202.229.33.245
3 2026-08-25 00:34 639232140250307418
529 ms 202.229.33.245
2 2026-08-25 00:17 639232129927860324
537 ms 202.229.33.245
1 2026-08-25 00:00 639232119551972438
540 ms 202.229.33.245