DNS response history for lobo.infortele.com

lobo.infortele.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 30 DNS check records, 29 successful responses, 1 failed responses, and 513 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 lobo.infortele.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

513 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

200.95.172.4

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for lobo.infortele.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
30 2026-08-25 10:21 639232492740373468
414 ms 200.95.172.4
29 2026-08-25 10:03 639232482235303141
410 ms 200.95.172.4
28 2026-08-25 09:46 639232471861770303
409 ms 200.95.172.4
27 2026-08-25 09:29 639232461630217327
416 ms 200.95.172.4
26 2026-08-25 09:11 639232451282965990
270 ms 200.95.172.4
25 2026-08-25 08:54 639232440814614938
414 ms 200.95.172.4
24 2026-08-25 08:37 639232430410720425
412 ms 200.95.172.4
23 2026-08-25 08:19 639232420003096185
536 ms 200.95.172.4
22 2026-08-25 08:02 639232409467287444
415 ms 200.95.172.4
21 2026-08-25 07:45 639232399077195997
406 ms 200.95.172.4
20 2026-08-25 07:27 639232388731528337
413 ms 200.95.172.4
19 2026-08-25 07:10 639232378288598612
413 ms 200.95.172.4
18 2026-08-25 06:16 639232346196373643
915 ms 200.95.172.4
17 2026-08-25 05:59 639232336112370741
3 ms 200.95.172.4
16 2026-08-25 05:43 639232326146508970
409 ms 200.95.172.4
15 2026-08-25 05:26 639232316189381720
412 ms 200.95.172.4
14 2026-08-25 05:09 639232306217998913
407 ms 200.95.172.4
13 2026-08-25 04:53 639232296255744174
232 ms 200.95.172.4
12 2026-08-25 04:36 639232286095760789
407 ms 200.95.172.4
11 2026-08-25 04:19 639232276086186273
3 ms 200.95.172.4
10 2026-08-25 04:02 639232265900986425
412 ms 200.95.172.4
9 2026-08-25 03:45 639232255723518075
425 ms 200.95.172.4
8 2026-08-25 03:28 639232245484452890
2213 ms 200.95.172.4
7 2026-08-25 03:11 639232235157175331
241 ms 200.95.172.4
6 2026-08-25 02:18 639232203197189095
-
5 2026-08-25 02:01 639232192844564298
2213 ms 200.95.172.4
4 2026-08-25 01:44 639232182496008942
409 ms 200.95.172.4
3 2026-08-25 01:26 639232172197053132
416 ms 200.95.172.4
2 2026-08-25 00:33 639232140250307418
409 ms 200.95.172.4
1 2026-08-25 00:16 639232129927860324
420 ms 200.95.172.4