DNS response history for ns2.gilabytes.com

ns2.gilabytes.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-31. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 122 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.gilabytes.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

122 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 08:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.140.70.174

Most recently resolved hosting IP on selected date

Successful Responses

27

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

Showing DNS history for 2026-08-31 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
27 2026-08-31 08:34 639237617127808241
36 ms 165.140.70.174
26 2026-08-31 08:17 639237606990101394
60 ms 165.140.70.174
25 2026-08-31 08:00 639237596595480036
320 ms 165.140.70.174
24 2026-08-31 07:42 639237586261012001
32 ms 165.140.70.174
23 2026-08-31 07:25 639237576047657695
9 ms 165.140.70.174
22 2026-08-31 07:08 639237565832936443
43 ms 165.140.70.174
21 2026-08-31 06:51 639237555466329546
17 ms 165.140.70.174
20 2026-08-31 06:34 639237545032411072
22 ms 165.140.70.174
19 2026-08-31 06:16 639237534469438634
10 ms 165.140.70.174
18 2026-08-31 05:22 639237502279296801
30 ms 165.140.70.174
17 2026-08-31 05:06 639237492362730124
35 ms 165.140.70.174
16 2026-08-31 04:49 639237482311584319
228 ms 165.140.70.174
15 2026-08-31 04:32 639237472150685594
16 ms 165.140.70.174
14 2026-08-31 04:15 639237462055295430
19 ms 165.140.70.174
13 2026-08-31 03:59 639237452089913890
33 ms 165.140.70.174
12 2026-08-31 03:42 639237441972654103
2013 ms 165.140.70.174
11 2026-08-31 03:25 639237432052396478
32 ms 165.140.70.174
10 2026-08-31 03:09 639237422012990851
56 ms 165.140.70.174
9 2026-08-31 02:52 639237411889602012
24 ms 165.140.70.174
8 2026-08-31 02:35 639237401637354221
18 ms 165.140.70.174
7 2026-08-31 02:18 639237391412690360
46 ms 165.140.70.174
6 2026-08-31 01:25 639237359972957132
55 ms 165.140.70.174
5 2026-08-31 01:09 639237350032183979
33 ms 165.140.70.174
4 2026-08-31 00:52 639237340111452066
21 ms 165.140.70.174
3 2026-08-31 00:35 639237329967272514
16 ms 165.140.70.174
2 2026-08-31 00:18 639237319916508151
31 ms 165.140.70.174
1 2026-08-31 00:02 639237309944877243
34 ms 165.140.70.174