DNS response history for dns2.i-me-i.com

dns2.i-me-i.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 35 DNS check records, 35 successful responses, 0 failed responses, and 593 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 dns2.i-me-i.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

593 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.39.176.36

Most recently resolved hosting IP on selected date

Successful Responses

35

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 dns2.i-me-i.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
35 2026-08-26 11:41 639233403515141099
597 ms 202.39.176.36
34 2026-08-26 10:46 639233370841350248
956 ms 202.39.176.36
33 2026-08-26 10:29 639233360361507238
326 ms 202.39.176.36
32 2026-08-26 10:11 639233350067824371
587 ms 202.39.176.36
31 2026-08-26 09:54 639233339545274518
965 ms 202.39.176.36
30 2026-08-26 09:37 639233329214918079
568 ms 202.39.176.36
29 2026-08-26 09:19 639233318749762337
289 ms 202.39.176.36
28 2026-08-26 09:02 639233308387917838
588 ms 202.39.176.36
27 2026-08-26 08:45 639233297961740122
299 ms 202.39.176.36
26 2026-08-26 08:27 639233287487159094
577 ms 202.39.176.36
25 2026-08-26 08:10 639233276995531707
580 ms 202.39.176.36
24 2026-08-26 07:52 639233266521568229
579 ms 202.39.176.36
23 2026-08-26 07:35 639233256081047431
623 ms 202.39.176.36
22 2026-08-26 06:41 639233223620132921
617 ms 202.39.176.36
21 2026-08-26 06:23 639233213287814244
583 ms 202.39.176.36
20 2026-08-26 06:06 639233202925983161
594 ms 202.39.176.36
19 2026-08-26 05:49 639233192644780696
618 ms 202.39.176.36
18 2026-08-26 05:32 639233182401183833
571 ms 202.39.176.36
17 2026-08-26 05:15 639233172074181051
599 ms 202.39.176.36
16 2026-08-26 04:57 639233161808421455
298 ms 202.39.176.36
15 2026-08-26 04:40 639233151357344052
592 ms 202.39.176.36
14 2026-08-26 04:23 639233141034116946
1899 ms 202.39.176.36
13 2026-08-26 04:06 639233130828334142
568 ms 202.39.176.36
12 2026-08-26 03:49 639233120373450007
672 ms 202.39.176.36
11 2026-08-26 03:31 639233110066216193
614 ms 202.39.176.36
10 2026-08-26 02:38 639233078065410564
580 ms 202.39.176.36
9 2026-08-26 02:21 639233067787457832
577 ms 202.39.176.36
8 2026-08-26 02:04 639233057501801162
654 ms 202.39.176.36
7 2026-08-26 01:47 639233047089431703
301 ms 202.39.176.36
6 2026-08-26 01:29 639233036754790688
587 ms 202.39.176.36
5 2026-08-26 01:12 639233026412602472
295 ms 202.39.176.36
4 2026-08-26 00:55 639233016064066127
572 ms 202.39.176.36
3 2026-08-26 00:38 639233005922655772
279 ms 202.39.176.36
2 2026-08-26 00:21 639232995672256907
577 ms 202.39.176.36
1 2026-08-26 00:03 639232985300872416
574 ms 202.39.176.36