DNS response history for ns2.gyoby.com

ns2.gyoby.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-30. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 351 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.gyoby.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

351 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

89.116.157.212

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.gyoby.com

Showing DNS history for 2026-08-30 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-30 11:50 639236867916029489
4 ms 89.116.157.212
35 2026-08-30 11:33 639236858088772005
310 ms 89.116.157.212
34 2026-08-30 11:17 639236848158742395
2007 ms 89.116.157.212
33 2026-08-30 11:00 639236838137395574
311 ms 89.116.157.212
32 2026-08-30 10:43 639236827967386881
337 ms 89.116.157.212
31 2026-08-30 10:26 639236817708615077
3 ms 89.116.157.212
30 2026-08-30 09:33 639236785770651804
3 ms 89.116.157.212
29 2026-08-30 09:17 639236775820686373
313 ms 89.116.157.212
28 2026-08-30 09:00 639236765768339082
308 ms 89.116.157.212
27 2026-08-30 08:43 639236755602384085
309 ms 89.116.157.212
26 2026-08-30 08:26 639236745600094925
309 ms 89.116.157.212
25 2026-08-30 08:09 639236735311262753
3 ms 89.116.157.212
24 2026-08-30 07:52 639236724996745235
308 ms 89.116.157.212
23 2026-08-30 07:35 639236714839899761
307 ms 89.116.157.212
22 2026-08-30 07:18 639236704748431488
2170 ms 89.116.157.212
21 2026-08-30 07:01 639236694430128550
3 ms 89.116.157.212
20 2026-08-30 06:44 639236684143292417
323 ms 89.116.157.212
19 2026-08-30 06:27 639236673972499943
4 ms 89.116.157.212
18 2026-08-30 05:34 639236642126522802
4 ms 89.116.157.212
17 2026-08-30 05:17 639236632183518198
4 ms 89.116.157.212
16 2026-08-30 05:01 639236622289312589
306 ms 89.116.157.212
15 2026-08-30 04:44 639236612490676525
306 ms 89.116.157.212
14 2026-08-30 04:28 639236602582494852
2 ms 89.116.157.212
13 2026-08-30 04:11 639236592511706469
306 ms 89.116.157.212
12 2026-08-30 03:54 639236582441006869
308 ms 89.116.157.212
11 2026-08-30 03:38 639236572478785089
313 ms 89.116.157.212
10 2026-08-30 03:21 639236562556749999
312 ms 89.116.157.212
9 2026-08-30 03:04 639236552353482281
306 ms 89.116.157.212
8 2026-08-30 02:47 639236542188881607
308 ms 89.116.157.212
7 2026-08-30 02:30 639236531885440105
309 ms 89.116.157.212
6 2026-08-30 01:37 639236499922985383
311 ms 89.116.157.212
5 2026-08-30 01:20 639236489713594431
3 ms 89.116.157.212
4 2026-08-30 01:03 639236479750443901
2 ms 89.116.157.212
3 2026-08-30 00:46 639236469719936375
2 ms 89.116.157.212
2 2026-08-30 00:30 639236459579244885
2 ms 89.116.157.212
1 2026-08-30 00:13 639236449582837549
2199 ms 89.116.157.212