DNS response history for ns2.transportnewsportals.com

ns2.transportnewsportals.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 35 DNS check records, 35 successful responses, 0 failed responses, and 437 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.transportnewsportals.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

437 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.182.215.88

Most recently resolved hosting IP on selected date

Successful Responses

35

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.transportnewsportals.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
35 2026-08-25 12:20 639232566381512620
245 ms 64.182.215.88
34 2026-08-25 12:03 639232556111768563
249 ms 64.182.215.88
33 2026-08-25 11:46 639232545839529039
242 ms 64.182.215.88
32 2026-08-25 11:29 639232535349285207
248 ms 64.182.215.88
31 2026-08-25 11:11 639232524938080723
246 ms 64.182.215.88
30 2026-08-25 10:17 639232492740373468
251 ms 64.182.215.88
29 2026-08-25 10:00 639232482235303141
243 ms 64.182.215.88
28 2026-08-25 09:43 639232471861770303
7 ms 64.182.215.88
27 2026-08-25 09:25 639232461630217327
258 ms 64.182.215.88
26 2026-08-25 09:08 639232451282965990
2259 ms 64.182.215.88
25 2026-08-25 08:51 639232440814614938
246 ms 64.182.215.88
24 2026-08-25 08:33 639232430410720425
124 ms 64.182.215.88
23 2026-08-25 08:16 639232420003096185
146 ms 64.182.215.88
22 2026-08-25 07:59 639232409467287444
10 ms 64.182.215.88
21 2026-08-25 07:41 639232399077195997
248 ms 64.182.215.88
20 2026-08-25 07:24 639232388731528337
252 ms 64.182.215.88
19 2026-08-25 07:07 639232378288598612
259 ms 64.182.215.88
18 2026-08-25 06:13 639232346196373643
251 ms 64.182.215.88
17 2026-08-25 05:56 639232336112370741
246 ms 64.182.215.88
16 2026-08-25 05:40 639232326146508970
248 ms 64.182.215.88
15 2026-08-25 05:23 639232316189381720
2138 ms 64.182.215.88
14 2026-08-25 05:06 639232306217998913
245 ms 64.182.215.88
13 2026-08-25 04:50 639232296255744174
124 ms 64.182.215.88
12 2026-08-25 04:33 639232286095760789
126 ms 64.182.215.88
11 2026-08-25 04:16 639232276086186273
248 ms 64.182.215.88
10 2026-08-25 03:59 639232265900986425
247 ms 64.182.215.88
9 2026-08-25 03:42 639232255723518075
130 ms 64.182.215.88
8 2026-08-25 03:25 639232245484452890
247 ms 64.182.215.88
7 2026-08-25 03:08 639232235157175331
250 ms 64.182.215.88
6 2026-08-25 02:15 639232203197189095
248 ms 64.182.215.88
5 2026-08-25 01:58 639232192844564298
249 ms 64.182.215.88
4 2026-08-25 01:40 639232182496008942
124 ms 64.182.215.88
3 2026-08-25 01:23 639232172197053132
2177 ms 64.182.215.88
2 2026-08-25 00:30 639232140250307418
247 ms 64.182.215.88
1 2026-08-25 00:13 639232129927860324
2200 ms 64.182.215.88