DNS response history for dns.gochagocha.org

dns.gochagocha.org 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-26. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 536 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 dns.gochagocha.org.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

536 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.136.72.122

Most recently resolved hosting IP on selected date

Successful Responses

28

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 dns.gochagocha.org

Showing DNS history for 2026-08-26 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
28 2026-08-26 09:01 639233308387917838
680 ms 210.136.72.122
27 2026-08-26 08:44 639233297961740122
557 ms 210.136.72.122
26 2026-08-26 08:26 639233287487159094
783 ms 210.136.72.122
25 2026-08-26 08:09 639233276995531707
679 ms 210.136.72.122
24 2026-08-26 07:51 639233266521568229
561 ms 210.136.72.122
23 2026-08-26 07:34 639233256081047431
561 ms 210.136.72.122
22 2026-08-26 06:40 639233223620132921
274 ms 210.136.72.122
21 2026-08-26 06:23 639233213287814244
289 ms 210.136.72.122
20 2026-08-26 06:05 639233202925983161
559 ms 210.136.72.122
19 2026-08-26 05:48 639233192644780696
560 ms 210.136.72.122
18 2026-08-26 05:31 639233182401183833
678 ms 210.136.72.122
17 2026-08-26 05:14 639233172074181051
786 ms 210.136.72.122
16 2026-08-26 04:57 639233161808421455
557 ms 210.136.72.122
15 2026-08-26 04:39 639233151357344052
562 ms 210.136.72.122
14 2026-08-26 04:22 639233141034116946
560 ms 210.136.72.122
13 2026-08-26 04:05 639233130828334142
273 ms 210.136.72.122
12 2026-08-26 03:48 639233120373450007
566 ms 210.136.72.122
11 2026-08-26 03:30 639233110066216193
556 ms 210.136.72.122
10 2026-08-26 02:37 639233078065410564
673 ms 210.136.72.122
9 2026-08-26 02:20 639233067787457832
559 ms 210.136.72.122
8 2026-08-26 02:03 639233057501801162
559 ms 210.136.72.122
7 2026-08-26 01:46 639233047089431703
557 ms 210.136.72.122
6 2026-08-26 01:28 639233036754790688
555 ms 210.136.72.122
5 2026-08-26 01:11 639233026412602472
674 ms 210.136.72.122
4 2026-08-26 00:54 639233016064066127
273 ms 210.136.72.122
3 2026-08-26 00:37 639233005922655772
278 ms 210.136.72.122
2 2026-08-26 00:20 639232995672256907
568 ms 210.136.72.122
1 2026-08-26 00:03 639232985300872416
273 ms 210.136.72.122