DNS response history for ns1.twitter-trending.com

ns1.twitter-trending.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-25. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 497 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.twitter-trending.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

497 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 05:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.67.208.29

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 ns1.twitter-trending.com

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
34 2026-08-25 05:47 639232336112370741
47 ms 172.67.208.29
33 2026-08-25 05:47 639232336112370741
47 ms 104.21.37.125
32 2026-08-25 05:30 639232326146508970
13 ms 172.67.208.29
31 2026-08-25 05:30 639232326146508970
13 ms 104.21.37.125
30 2026-08-25 05:14 639232316189381720
8 ms 104.21.37.125
29 2026-08-25 05:14 639232316189381720
8 ms 172.67.208.29
28 2026-08-25 04:57 639232306217998913
38 ms 104.21.37.125
27 2026-08-25 04:57 639232306217998913
38 ms 172.67.208.29
26 2026-08-25 04:40 639232296255744174
4053 ms 104.21.37.125
25 2026-08-25 04:40 639232296255744174
4053 ms 172.67.208.29
24 2026-08-25 04:23 639232286095760789
9 ms 104.21.37.125
23 2026-08-25 04:23 639232286095760789
9 ms 172.67.208.29
22 2026-08-25 04:07 639232276086186273
51 ms 104.21.37.125
21 2026-08-25 04:07 639232276086186273
51 ms 172.67.208.29
20 2026-08-25 03:50 639232265900986425
2049 ms 104.21.37.125
19 2026-08-25 03:50 639232265900986425
2049 ms 172.67.208.29
18 2026-08-25 03:33 639232255723518075
10 ms 104.21.37.125
17 2026-08-25 03:33 639232255723518075
10 ms 172.67.208.29
16 2026-08-25 03:16 639232245484452890
18 ms 172.67.208.29
15 2026-08-25 03:16 639232245484452890
18 ms 104.21.37.125
14 2026-08-25 02:59 639232235157175331
14 ms 104.21.37.125
13 2026-08-25 02:59 639232235157175331
14 ms 172.67.208.29
12 2026-08-25 02:05 639232203197189095
20 ms 104.21.37.125
11 2026-08-25 02:05 639232203197189095
20 ms 172.67.208.29
10 2026-08-25 01:48 639232192844564298
26 ms 104.21.37.125
9 2026-08-25 01:48 639232192844564298
26 ms 172.67.208.29
8 2026-08-25 01:31 639232182496008942
7 ms 104.21.37.125
7 2026-08-25 01:31 639232182496008942
7 ms 172.67.208.29
6 2026-08-25 01:14 639232172197053132
8 ms 104.21.37.125
5 2026-08-25 01:14 639232172197053132
8 ms 172.67.208.29
4 2026-08-25 00:20 639232140250307418
25 ms 172.67.208.29
3 2026-08-25 00:20 639232140250307418
25 ms 104.21.37.125
2 2026-08-25 00:03 639232129927860324
2048 ms 104.21.37.125
1 2026-08-25 00:03 639232129927860324
2048 ms 172.67.208.29