DNS response history for ns2.telegobe.net

ns2.telegobe.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 319 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.telegobe.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

319 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

170.130.16.201

Most recently resolved hosting IP on selected date

Successful Responses

34

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

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
34 2026-08-26 10:45 639233370841350248
141 ms 170.130.16.201
33 2026-08-26 10:28 639233360361507238
68 ms 170.130.16.201
32 2026-08-26 10:10 639233350067824371
68 ms 170.130.16.201
31 2026-08-26 09:53 639233339545274518
71 ms 170.130.16.201
30 2026-08-26 09:36 639233329214918079
118 ms 170.130.16.201
29 2026-08-26 09:18 639233318749762337
494 ms 170.130.16.201
28 2026-08-26 09:01 639233308387917838
497 ms 170.130.16.201
27 2026-08-26 08:44 639233297961740122
497 ms 170.130.16.201
26 2026-08-26 08:26 639233287487159094
73 ms 170.130.16.201
25 2026-08-26 08:09 639233276995531707
71 ms 170.130.16.201
24 2026-08-26 07:51 639233266521568229
189 ms 170.130.16.201
23 2026-08-26 07:34 639233256081047431
43 ms 170.130.16.201
22 2026-08-26 06:40 639233223620132921
491 ms 170.130.16.201
21 2026-08-26 06:22 639233213287814244
491 ms 170.130.16.201
20 2026-08-26 06:05 639233202925983161
490 ms 170.130.16.201
19 2026-08-26 05:48 639233192644780696
2172 ms 170.130.16.201
18 2026-08-26 05:31 639233182401183833
328 ms 170.130.16.201
17 2026-08-26 05:14 639233172074181051
487 ms 170.130.16.201
16 2026-08-26 04:56 639233161808421455
354 ms 170.130.16.201
15 2026-08-26 04:39 639233151357344052
65 ms 170.130.16.201
14 2026-08-26 04:22 639233141034116946
65 ms 170.130.16.201
13 2026-08-26 04:05 639233130828334142
492 ms 170.130.16.201
12 2026-08-26 03:48 639233120373450007
42 ms 170.130.16.201
11 2026-08-26 03:30 639233110066216193
490 ms 170.130.16.201
10 2026-08-26 02:37 639233078065410564
208 ms 170.130.16.201
9 2026-08-26 02:20 639233067787457832
338 ms 170.130.16.201
8 2026-08-26 02:03 639233057501801162
335 ms 170.130.16.201
7 2026-08-26 01:46 639233047089431703
325 ms 170.130.16.201
6 2026-08-26 01:28 639233036754790688
62 ms 170.130.16.201
5 2026-08-26 01:11 639233026412602472
64 ms 170.130.16.201
4 2026-08-26 00:54 639233016064066127
497 ms 170.130.16.201
3 2026-08-26 00:37 639233005922655772
65 ms 170.130.16.201
2 2026-08-26 00:20 639232995672256907
331 ms 170.130.16.201
1 2026-08-26 00:02 639232985300872416
333 ms 170.130.16.201