leofame.com
https://leofame.comStatus
Online
Monitoring activeResponse time
107ms
FastLast checked
Nov 12, 2026
4:10 AMUptime (30 days)
98.80%
Recent checks
Last 50 checksResponse history (last 40, oldest → newest)
| Status | HTTP code | Response time | Checked at | Note |
|---|---|---|---|---|
| Online | 200 | 107ms | Nov 12, 2026 4:10 AM | |
| Online | 200 | 77ms | Nov 12, 2026 4:05 AM | |
| Online | 200 | 96ms | Nov 12, 2026 4:00 AM | |
| Online | 200 | 115ms | Nov 12, 2026 3:55 AM | |
| Online | 200 | 83ms | Nov 12, 2026 3:50 AM | |
| Online | 200 | 85ms | Nov 12, 2026 3:45 AM | |
| Online | 200 | 90ms | Nov 12, 2026 3:40 AM | |
| Online | 200 | 102ms | Nov 12, 2026 3:35 AM | |
| Online | 200 | 121ms | Nov 12, 2026 3:30 AM | |
| Online | 200 | 101ms | Nov 12, 2026 3:25 AM | |
| Online | 200 | 112ms | Nov 12, 2026 3:20 AM | |
| Online | 200 | 103ms | Nov 12, 2026 3:15 AM | |
| Online | 200 | 90ms | Nov 12, 2026 3:10 AM | |
| Online | 200 | 106ms | Nov 12, 2026 3:05 AM | |
| Online | 200 | 89ms | Nov 12, 2026 3:00 AM | |
| Online | 200 | 118ms | Nov 12, 2026 2:55 AM | |
| Online | 200 | 101ms | Nov 12, 2026 2:50 AM | |
| Online | 200 | 78ms | Nov 12, 2026 2:45 AM | |
| Online | 200 | 115ms | Nov 12, 2026 2:40 AM | |
| Online | 200 | 97ms | Nov 12, 2026 2:35 AM | |
| Online | 200 | 97ms | Nov 12, 2026 2:30 AM | |
| Online | 200 | 63ms | Nov 12, 2026 2:25 AM | |
| Online | 200 | 117ms | Nov 12, 2026 2:20 AM | |
| Online | 200 | 97ms | Nov 12, 2026 2:15 AM | |
| Online | 200 | 78ms | Nov 12, 2026 2:10 AM | |
| Online | 200 | 75ms | Nov 12, 2026 2:05 AM | |
| Online | 200 | 90ms | Nov 12, 2026 2:00 AM | |
| Online | 200 | 105ms | Nov 12, 2026 1:55 AM | |
| Online | 200 | 109ms | Nov 12, 2026 1:50 AM | |
| Online | 200 | 63ms | Nov 12, 2026 1:45 AM | |
| Online | 200 | 159ms | Nov 12, 2026 1:40 AM | |
| Online | 200 | 110ms | Nov 12, 2026 1:35 AM | |
| Online | 200 | 102ms | Nov 12, 2026 1:30 AM | |
| Online | 200 | 90ms | Nov 12, 2026 1:25 AM | |
| Online | 200 | 112ms | Nov 12, 2026 1:20 AM | |
| Online | 200 | 95ms | Nov 12, 2026 1:15 AM | |
| Online | 200 | 111ms | Nov 12, 2026 1:10 AM | |
| Online | 200 | 81ms | Nov 12, 2026 1:05 AM | |
| Online | 200 | 82ms | Nov 12, 2026 1:00 AM | |
| Online | 200 | 98ms | Nov 12, 2026 12:55 AM | |
| Online | 200 | 94ms | Nov 12, 2026 12:50 AM | |
| Online | 200 | 95ms | Nov 12, 2026 12:45 AM | |
| Online | 200 | 118ms | Nov 12, 2026 12:40 AM | |
| Online | 200 | 116ms | Nov 12, 2026 12:35 AM | |
| Online | 200 | 144ms | Nov 12, 2026 12:30 AM | |
| Online | 200 | 105ms | Nov 12, 2026 12:25 AM | |
| Online | 200 | 128ms | Nov 12, 2026 12:20 AM | |
| Online | 200 | 125ms | Nov 12, 2026 12:15 AM | |
| Online | 200 | 111ms | Nov 12, 2026 12:10 AM | |
| Online | 200 | 126ms | Nov 12, 2026 12:05 AM |
Know before your customers do
This page is a snapshot. Monitoring is the alert.
Checks every five minutes on your own domains, email the moment one stops answering, and the response-time history that shows a site getting slower before it goes down.
Built from 26,556 recorded checks between Jul 25, 2026 and Nov 12, 2026 . Response times are measured from our checker, not from your location.