DNS response history for ns1.eroomai.com

ns1.eroomai.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 29 DNS check records, 29 successful responses, 0 failed responses, and 551 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 ns1.eroomai.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

551 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

221.160.220.101

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns1.eroomai.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
29 2026-08-26 09:19 639233318749762337
4 ms 221.160.220.101
28 2026-08-26 09:02 639233308387917838
4 ms 221.160.220.101
27 2026-08-26 08:44 639233297961740122
503 ms 221.160.220.101
26 2026-08-26 08:27 639233287487159094
498 ms 221.160.220.101
25 2026-08-26 08:10 639233276995531707
502 ms 221.160.220.101
24 2026-08-26 07:52 639233266521568229
500 ms 221.160.220.101
23 2026-08-26 07:34 639233256081047431
1082 ms 221.160.220.101
22 2026-08-26 06:40 639233223620132921
5 ms 221.160.220.101
21 2026-08-26 06:23 639233213287814244
4 ms 221.160.220.101
20 2026-08-26 06:06 639233202925983161
4 ms 221.160.220.101
19 2026-08-26 05:49 639233192644780696
4 ms 221.160.220.101
18 2026-08-26 05:31 639233182401183833
1088 ms 221.160.220.101
17 2026-08-26 05:14 639233172074181051
517 ms 221.160.220.101
16 2026-08-26 04:57 639233161808421455
520 ms 221.160.220.101
15 2026-08-26 04:40 639233151357344052
3 ms 221.160.220.101
14 2026-08-26 04:23 639233141034116946
3 ms 221.160.220.101
13 2026-08-26 04:06 639233130828334142
1214 ms 221.160.220.101
12 2026-08-26 03:48 639233120373450007
1101 ms 221.160.220.101
11 2026-08-26 03:31 639233110066216193
285 ms 221.160.220.101
10 2026-08-26 02:38 639233078065410564
1092 ms 221.160.220.101
9 2026-08-26 02:21 639233067787457832
1092 ms 221.160.220.101
8 2026-08-26 02:03 639233057501801162
1091 ms 221.160.220.101
7 2026-08-26 01:46 639233047089431703
1098 ms 221.160.220.101
6 2026-08-26 01:29 639233036754790688
1101 ms 221.160.220.101
5 2026-08-26 01:12 639233026412602472
492 ms 221.160.220.101
4 2026-08-26 00:54 639233016064066127
1087 ms 221.160.220.101
3 2026-08-26 00:37 639233005922655772
3 ms 221.160.220.101
2 2026-08-26 00:20 639232995672256907
3 ms 221.160.220.101
1 2026-08-26 00:03 639232985300872416
1082 ms 221.160.220.101