DNS response history for ns2.chromango.com

ns2.chromango.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-28. For this date, NameServerHistory found 28 DNS check records, 27 successful responses, 1 failed responses, and 120 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.chromango.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

120 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 11:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.119.253.34

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.chromango.com

Showing DNS history for 2026-08-28 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
28 2026-08-28 11:35 639235132147470568
19 ms 160.119.253.34
27 2026-08-28 11:18 639235121907744088
24 ms 160.119.253.34
26 2026-08-28 11:01 639235111428014262
29 ms 160.119.253.34
25 2026-08-28 10:43 639235100921813626
44 ms 160.119.253.34
24 2026-08-28 09:49 639235068670703481
46 ms 160.119.253.34
23 2026-08-28 09:32 639235058337459445
23 ms 160.119.253.34
22 2026-08-28 09:14 639235047825109146
27 ms 160.119.253.34
21 2026-08-28 08:57 639235037383229033
39 ms 160.119.253.34
20 2026-08-28 08:04 639235005619242711
49 ms 160.119.253.34
19 2026-08-28 07:47 639234995310346584
54 ms 160.119.253.34
18 2026-08-28 07:30 639234984946548933
26 ms 160.119.253.34
17 2026-08-28 07:12 639234974608077290
37 ms 160.119.253.34
16 2026-08-28 06:19 639234942529845595
49 ms 160.119.253.34
15 2026-08-28 06:02 639234932259126627
28 ms 160.119.253.34
14 2026-08-28 05:44 639234921916735988
35 ms 160.119.253.34
13 2026-08-28 05:27 639234911470038027
34 ms 160.119.253.34
12 2026-08-28 04:34 639234879588411654
209 ms 160.119.253.34
11 2026-08-28 04:17 639234869341589104
23 ms 160.119.253.34
10 2026-08-28 04:00 639234859012216675
34 ms 160.119.253.34
9 2026-08-28 03:42 639234848695364934
35 ms 160.119.253.34
8 2026-08-28 02:50 639234816952458162
27 ms 160.119.253.34
7 2026-08-28 02:33 639234806773081598
35 ms 160.119.253.34
6 2026-08-28 02:15 639234796382955255
206 ms 160.119.253.34
5 2026-08-28 01:58 639234786015782563
25 ms 160.119.253.34
4 2026-08-28 01:04 639234753811917646
31 ms 160.119.253.34
3 2026-08-28 00:47 639234743739767811
2035 ms 160.119.253.34
2 2026-08-28 00:30 639234733372362811
-
1 2026-08-28 00:13 639234723048550337
25 ms 160.119.253.34