DNS response history for ns1.revateam.com

ns1.revateam.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-25. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 312 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.revateam.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

312 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.211.202.166

Most recently resolved hosting IP on selected date

Successful Responses

33

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.revateam.com

Showing DNS history for 2026-08-25 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
33 2026-08-25 11:44 639232545839529039
243 ms 103.211.202.166
32 2026-08-25 11:27 639232535349285207
241 ms 103.211.202.166
31 2026-08-25 11:09 639232524938080723
247 ms 103.211.202.166
30 2026-08-25 10:15 639232492740373468
144 ms 103.211.202.166
29 2026-08-25 09:58 639232482235303141
126 ms 103.211.202.166
28 2026-08-25 09:41 639232471861770303
261 ms 103.211.202.166
27 2026-08-25 09:24 639232461630217327
9 ms 103.211.202.166
26 2026-08-25 09:06 639232451282965990
252 ms 103.211.202.166
25 2026-08-25 08:49 639232440814614938
252 ms 103.211.202.166
24 2026-08-25 08:32 639232430410720425
250 ms 103.211.202.166
23 2026-08-25 08:14 639232420003096185
128 ms 103.211.202.166
22 2026-08-25 07:57 639232409467287444
131 ms 103.211.202.166
21 2026-08-25 07:39 639232399077195997
255 ms 103.211.202.166
20 2026-08-25 07:22 639232388731528337
254 ms 103.211.202.166
19 2026-08-25 07:05 639232378288598612
242 ms 103.211.202.166
18 2026-08-25 06:11 639232346196373643
130 ms 103.211.202.166
17 2026-08-25 05:54 639232336112370741
2035 ms 103.211.202.166
16 2026-08-25 05:38 639232326146508970
2132 ms 103.211.202.166
15 2026-08-25 05:21 639232316189381720
257 ms 103.211.202.166
14 2026-08-25 05:05 639232306217998913
147 ms 103.211.202.166
13 2026-08-25 04:48 639232296255744174
232 ms 103.211.202.166
12 2026-08-25 04:31 639232286095760789
258 ms 103.211.202.166
11 2026-08-25 04:14 639232276086186273
233 ms 103.211.202.166
10 2026-08-25 03:57 639232265900986425
242 ms 103.211.202.166
9 2026-08-25 03:40 639232255723518075
233 ms 103.211.202.166
8 2026-08-25 03:23 639232245484452890
256 ms 103.211.202.166
7 2026-08-25 03:06 639232235157175331
122 ms 103.211.202.166
6 2026-08-25 02:13 639232203197189095
238 ms 103.211.202.166
5 2026-08-25 01:56 639232192844564298
270 ms 103.211.202.166
4 2026-08-25 01:38 639232182496008942
236 ms 103.211.202.166
3 2026-08-25 01:21 639232172197053132
3 ms 103.211.202.166
2 2026-08-25 00:28 639232140250307418
13 ms 103.211.202.166
1 2026-08-25 00:11 639232129927860324
236 ms 103.211.202.166