DNS response history for ns2.esocom.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

775 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 13:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

122.99.240.73

Most recently resolved hosting IP on selected date

Successful Responses

32

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.esocom.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
32 2026-08-28 13:26 639235195230848570
507 ms 122.99.240.73
31 2026-08-28 13:09 639235184840503274
1128 ms 122.99.240.73
30 2026-08-28 12:52 639235174453894956
1068 ms 122.99.240.73
29 2026-08-28 12:34 639235163898672622
1091 ms 122.99.240.73
28 2026-08-28 11:41 639235132147470568
1120 ms 122.99.240.73
27 2026-08-28 11:24 639235121907744088
1107 ms 122.99.240.73
26 2026-08-28 11:07 639235111428014262
502 ms 122.99.240.73
25 2026-08-28 10:49 639235100921813626
1136 ms 122.99.240.73
24 2026-08-28 09:55 639235068670703481
1421 ms 122.99.240.73
23 2026-08-28 09:38 639235058337459445
495 ms 122.99.240.73
22 2026-08-28 09:21 639235047825109146
492 ms 122.99.240.73
21 2026-08-28 09:03 639235037383229033
500 ms 122.99.240.73
20 2026-08-28 08:10 639235005619242711
476 ms 122.99.240.73
19 2026-08-28 07:53 639234995310346584
492 ms 122.99.240.73
18 2026-08-28 07:36 639234984946548933
501 ms 122.99.240.73
17 2026-08-28 07:19 639234974608077290
512 ms 122.99.240.73
16 2026-08-28 06:25 639234942529845595
537 ms 122.99.240.73
15 2026-08-28 06:08 639234932259126627
1121 ms 122.99.240.73
14 2026-08-28 05:51 639234921916735988
503 ms 122.99.240.73
13 2026-08-28 05:34 639234911470038027
517 ms 122.99.240.73
12 2026-08-28 04:40 639234879588411654
507 ms 122.99.240.73
11 2026-08-28 04:23 639234869341589104
505 ms 122.99.240.73
10 2026-08-28 04:06 639234859012216675
1065 ms 122.99.240.73
9 2026-08-28 03:49 639234848695364934
1105 ms 122.99.240.73
8 2026-08-28 02:56 639234816952458162
1105 ms 122.99.240.73
7 2026-08-28 02:39 639234806773081598
1090 ms 122.99.240.73
6 2026-08-28 02:22 639234796382955255
534 ms 122.99.240.73
5 2026-08-28 02:04 639234786015782563
506 ms 122.99.240.73
4 2026-08-28 01:11 639234753811917646
1098 ms 122.99.240.73
3 2026-08-28 00:54 639234743739767811
503 ms 122.99.240.73
2 2026-08-28 00:37 639234733372362811
1065 ms 122.99.240.73
1 2026-08-28 00:19 639234723048550337
491 ms 122.99.240.73