DNS response history for ns2.trainwashingtondc.com

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

25

Historical checks stored for this nameserver on selected date

Average Latency

253 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.227.236.124

Most recently resolved hosting IP on selected date

Successful Responses

25

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.trainwashingtondc.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
25 2026-08-26 08:21 639233287487159094
121 ms 212.227.236.124
24 2026-08-26 08:04 639233276995531707
274 ms 212.227.236.124
23 2026-08-26 07:46 639233266521568229
289 ms 212.227.236.124
22 2026-08-26 07:29 639233256081047431
2007 ms 212.227.236.124
21 2026-08-26 06:35 639233223620132921
7 ms 212.227.236.124
20 2026-08-26 06:17 639233213287814244
96 ms 212.227.236.124
19 2026-08-26 06:00 639233202925983161
130 ms 212.227.236.124
18 2026-08-26 05:43 639233192644780696
288 ms 212.227.236.124
17 2026-08-26 05:26 639233182401183833
253 ms 212.227.236.124
16 2026-08-26 05:09 639233172074181051
6 ms 212.227.236.124
15 2026-08-26 04:51 639233161808421455
289 ms 212.227.236.124
14 2026-08-26 04:34 639233151357344052
311 ms 212.227.236.124
13 2026-08-26 04:17 639233141034116946
2 ms 212.227.236.124
12 2026-08-26 04:00 639233130828334142
282 ms 212.227.236.124
11 2026-08-26 03:43 639233120373450007
260 ms 212.227.236.124
10 2026-08-26 03:25 639233110066216193
251 ms 212.227.236.124
9 2026-08-26 02:32 639233078065410564
280 ms 212.227.236.124
8 2026-08-26 02:15 639233067787457832
268 ms 212.227.236.124
7 2026-08-26 01:58 639233057501801162
248 ms 212.227.236.124
6 2026-08-26 01:40 639233047089431703
149 ms 212.227.236.124
5 2026-08-26 01:23 639233036754790688
97 ms 212.227.236.124
4 2026-08-26 01:06 639233026412602472
48 ms 212.227.236.124
3 2026-08-26 00:48 639233016064066127
154 ms 212.227.236.124
2 2026-08-26 00:31 639233005922655772
128 ms 212.227.236.124
1 2026-08-26 00:14 639232995672256907
97 ms 212.227.236.124