DNS response history for ns.trafficsystem.mx

ns.trafficsystem.mx 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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 520 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 ns.trafficsystem.mx.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

520 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.50.105.189

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 ns.trafficsystem.mx

Showing DNS history for 2026-08-24 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-24 14:03 639231765923559455
19 ms 74.50.105.189
33 2026-08-24 13:46 639231755868832964
16 ms 74.50.105.189
32 2026-08-24 13:29 639231745628278877
2008 ms 74.50.105.189
31 2026-08-24 13:12 639231735407682062
2323 ms 74.50.105.189
30 2026-08-24 12:19 639231703815441688
163 ms 74.50.105.189
29 2026-08-24 12:03 639231693747052549
31 ms 74.50.105.189
28 2026-08-24 11:46 639231683712487276
360 ms 74.50.105.189
27 2026-08-24 11:29 639231673513573868
335 ms 74.50.105.189
26 2026-08-24 10:36 639231641791249939
90 ms 74.50.105.189
25 2026-08-24 10:19 639231631866211033
175 ms 74.50.105.189
24 2026-08-24 10:02 639231621644955316
22 ms 74.50.105.189
23 2026-08-24 09:45 639231611478799259
64 ms 74.50.105.189
22 2026-08-24 08:53 639231579923718211
162 ms 74.50.105.189
21 2026-08-24 08:36 639231569810702936
9 ms 74.50.105.189
20 2026-08-24 08:19 639231559762411619
19 ms 74.50.105.189
19 2026-08-24 08:02 639231549663595407
2144 ms 74.50.105.189
18 2026-08-24 07:10 639231518076817246
3 ms 74.50.105.189
17 2026-08-24 06:53 639231508078650885
173 ms 74.50.105.189
16 2026-08-24 06:37 639231498210697093
15 ms 74.50.105.189
15 2026-08-24 06:20 639231488109699360
7 ms 74.50.105.189
14 2026-08-24 05:28 639231456772510692
2 ms 74.50.105.189
13 2026-08-24 05:12 639231447084631185
141 ms 74.50.105.189
12 2026-08-24 04:55 639231437208519473
33 ms 74.50.105.189
11 2026-08-24 04:38 639231427209627490
13 ms 74.50.105.189
10 2026-08-24 03:46 639231395791246644
20 ms 74.50.105.189
9 2026-08-24 03:30 639231386075551458
72 ms 74.50.105.189
8 2026-08-24 03:13 639231376208713791
2069 ms 74.50.105.189
7 2026-08-24 02:57 639231366170589276
19 ms 74.50.105.189
6 2026-08-24 02:04 639231334732159368
2023 ms 74.50.105.189
5 2026-08-24 01:48 639231325035670078
2236 ms 74.50.105.189
4 2026-08-24 01:31 639231315132253837
7 ms 74.50.105.189
3 2026-08-24 01:15 639231305014280808
2891 ms 74.50.105.189
2 2026-08-24 00:23 639231273779380675
6 ms 74.50.105.189
1 2026-08-24 00:07 639231264180839154
6 ms 74.50.105.189