DNS response history for ns1.g3tm.com

ns1.g3tm.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-26. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 132 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 ns1.g3tm.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

132 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

148.113.170.126

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns1.g3tm.com

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
33 2026-08-26 10:36 639233370841350248
8 ms 148.113.170.126
32 2026-08-26 10:19 639233360361507238
49 ms 148.113.170.126
31 2026-08-26 10:02 639233350067824371
153 ms 148.113.170.126
30 2026-08-26 09:44 639233339545274518
20 ms 148.113.170.126
29 2026-08-26 09:27 639233329214918079
7 ms 148.113.170.126
28 2026-08-26 09:10 639233318749762337
2258 ms 148.113.170.126
27 2026-08-26 08:52 639233308387917838
7 ms 148.113.170.126
26 2026-08-26 08:35 639233297961740122
6 ms 148.113.170.126
25 2026-08-26 08:18 639233287487159094
188 ms 148.113.170.126
24 2026-08-26 08:00 639233276995531707
16 ms 148.113.170.126
23 2026-08-26 07:43 639233266521568229
9 ms 148.113.170.126
22 2026-08-26 07:25 639233256081047431
23 ms 148.113.170.126
21 2026-08-26 06:31 639233223620132921
7 ms 148.113.170.126
20 2026-08-26 06:14 639233213287814244
6 ms 148.113.170.126
19 2026-08-26 05:57 639233202925983161
313 ms 148.113.170.126
18 2026-08-26 05:39 639233192644780696
5 ms 148.113.170.126
17 2026-08-26 05:22 639233182401183833
20 ms 148.113.170.126
16 2026-08-26 05:05 639233172074181051
181 ms 148.113.170.126
15 2026-08-26 04:48 639233161808421455
6 ms 148.113.170.126
14 2026-08-26 04:31 639233151357344052
248 ms 148.113.170.126
13 2026-08-26 04:13 639233141034116946
4 ms 148.113.170.126
12 2026-08-26 03:56 639233130828334142
47 ms 148.113.170.126
11 2026-08-26 03:39 639233120373450007
156 ms 148.113.170.126
10 2026-08-26 03:22 639233110066216193
161 ms 148.113.170.126
9 2026-08-26 02:28 639233078065410564
38 ms 148.113.170.126
8 2026-08-26 02:11 639233067787457832
149 ms 148.113.170.126
7 2026-08-26 01:54 639233057501801162
150 ms 148.113.170.126
6 2026-08-26 01:37 639233047089431703
8 ms 148.113.170.126
5 2026-08-26 01:20 639233036754790688
4 ms 148.113.170.126
4 2026-08-26 01:02 639233026412602472
5 ms 148.113.170.126
3 2026-08-26 00:45 639233016064066127
38 ms 148.113.170.126
2 2026-08-26 00:28 639233005922655772
7 ms 148.113.170.126
1 2026-08-26 00:11 639232995672256907
46 ms 148.113.170.126