DNS response history for ns2.transglobal.pt

ns2.transglobal.pt 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-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 142 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.transglobal.pt.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

142 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.126.172.49

Most recently resolved hosting IP on selected date

Successful Responses

29

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.transglobal.pt

Showing DNS history for 2026-08-25 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
29 2026-08-25 09:57 639232482235303141
100 ms 94.126.172.49
28 2026-08-25 09:39 639232471861770303
52 ms 94.126.172.49
27 2026-08-25 09:22 639232461630217327
70 ms 94.126.172.49
26 2026-08-25 09:05 639232451282965990
20 ms 94.126.172.49
25 2026-08-25 08:47 639232440814614938
51 ms 94.126.172.49
24 2026-08-25 08:30 639232430410720425
92 ms 94.126.172.49
23 2026-08-25 08:13 639232420003096185
126 ms 94.126.172.49
22 2026-08-25 07:55 639232409467287444
154 ms 94.126.172.49
21 2026-08-25 07:38 639232399077195997
71 ms 94.126.172.49
20 2026-08-25 07:21 639232388731528337
2074 ms 94.126.172.49
19 2026-08-25 07:03 639232378288598612
95 ms 94.126.172.49
18 2026-08-25 06:10 639232346196373643
51 ms 94.126.172.49
17 2026-08-25 05:53 639232336112370741
91 ms 94.126.172.49
16 2026-08-25 05:36 639232326146508970
93 ms 94.126.172.49
15 2026-08-25 05:20 639232316189381720
10 ms 94.126.172.49
14 2026-08-25 05:03 639232306217998913
49 ms 94.126.172.49
13 2026-08-25 04:46 639232296255744174
95 ms 94.126.172.49
12 2026-08-25 04:30 639232286095760789
59 ms 94.126.172.49
11 2026-08-25 04:13 639232276086186273
68 ms 94.126.172.49
10 2026-08-25 03:56 639232265900986425
34 ms 94.126.172.49
9 2026-08-25 03:39 639232255723518075
125 ms 94.126.172.49
8 2026-08-25 03:22 639232245484452890
51 ms 94.126.172.49
7 2026-08-25 03:05 639232235157175331
92 ms 94.126.172.49
6 2026-08-25 02:11 639232203197189095
49 ms 94.126.172.49
5 2026-08-25 01:54 639232192844564298
53 ms 94.126.172.49
4 2026-08-25 01:37 639232182496008942
51 ms 94.126.172.49
3 2026-08-25 01:20 639232172197053132
101 ms 94.126.172.49
2 2026-08-25 00:26 639232140250307418
104 ms 94.126.172.49
1 2026-08-25 00:09 639232129927860324
51 ms 94.126.172.49