frigosservice.com
https://frigosservice.comStatus
Online
Monitoring activeResponse time
1,595ms
SlowLast checked
Nov 12, 2026
5:10 AMUptime (30 days)
99.99%
Recent checks
Last 50 checksResponse history (last 40, oldest → newest)
| Status | HTTP code | Response time | Checked at | Note |
|---|---|---|---|---|
| Online | 200 | 1,595ms | Nov 12, 2026 5:10 AM | |
| Online | 200 | 1,499ms | Nov 12, 2026 5:05 AM | |
| Online | 200 | 1,141ms | Nov 12, 2026 5:00 AM | |
| Online | 200 | 1,484ms | Nov 12, 2026 4:55 AM | |
| Online | 200 | 1,285ms | Nov 12, 2026 4:50 AM | |
| Online | 200 | 1,169ms | Nov 12, 2026 4:45 AM | |
| Online | 200 | 1,183ms | Nov 12, 2026 4:40 AM | |
| Online | 200 | 1,217ms | Nov 12, 2026 4:35 AM | |
| Online | 200 | 1,336ms | Nov 12, 2026 4:30 AM | |
| Online | 200 | 1,252ms | Nov 12, 2026 4:25 AM | |
| Online | 200 | 1,342ms | Nov 12, 2026 4:20 AM | |
| Online | 200 | 1,166ms | Nov 12, 2026 4:15 AM | |
| Online | 200 | 1,075ms | Nov 12, 2026 4:10 AM | |
| Online | 200 | 1,207ms | Nov 12, 2026 4:05 AM | |
| Online | 200 | 1,161ms | Nov 12, 2026 4:00 AM | |
| Online | 200 | 1,232ms | Nov 12, 2026 3:55 AM | |
| Online | 200 | 1,163ms | Nov 12, 2026 3:51 AM | |
| Online | 200 | 1,218ms | Nov 12, 2026 3:45 AM | |
| Online | 200 | 1,303ms | Nov 12, 2026 3:40 AM | |
| Online | 200 | 1,765ms | Nov 12, 2026 3:35 AM | |
| Online | 200 | 1,101ms | Nov 12, 2026 3:30 AM | |
| Online | 200 | 1,212ms | Nov 12, 2026 3:25 AM | |
| Online | 200 | 1,208ms | Nov 12, 2026 3:20 AM | |
| Online | 200 | 1,624ms | Nov 12, 2026 3:15 AM | |
| Online | 200 | 1,126ms | Nov 12, 2026 3:10 AM | |
| Online | 200 | 1,142ms | Nov 12, 2026 3:05 AM | |
| Online | 200 | 973ms | Nov 12, 2026 3:00 AM | |
| Online | 200 | 1,132ms | Nov 12, 2026 2:55 AM | |
| Online | 200 | 1,177ms | Nov 12, 2026 2:50 AM | |
| Online | 200 | 1,212ms | Nov 12, 2026 2:45 AM | |
| Online | 200 | 1,331ms | Nov 12, 2026 2:40 AM | |
| Online | 200 | 1,192ms | Nov 12, 2026 2:35 AM | |
| Online | 200 | 1,095ms | Nov 12, 2026 2:30 AM | |
| Online | 200 | 1,325ms | Nov 12, 2026 2:25 AM | |
| Online | 200 | 1,112ms | Nov 12, 2026 2:20 AM | |
| Online | 200 | 1,130ms | Nov 12, 2026 2:15 AM | |
| Online | 200 | 1,133ms | Nov 12, 2026 2:10 AM | |
| Online | 200 | 1,077ms | Nov 12, 2026 2:05 AM | |
| Online | 200 | 1,220ms | Nov 12, 2026 2:00 AM | |
| Online | 200 | 1,370ms | Nov 12, 2026 1:55 AM | |
| Online | 200 | 1,089ms | Nov 12, 2026 1:50 AM | |
| Online | 200 | 1,205ms | Nov 12, 2026 1:45 AM | |
| Online | 200 | 1,348ms | Nov 12, 2026 1:40 AM | |
| Online | 200 | 992ms | Nov 12, 2026 1:35 AM | |
| Online | 200 | 1,286ms | Nov 12, 2026 1:30 AM | |
| Online | 200 | 1,229ms | Nov 12, 2026 1:25 AM | |
| Online | 200 | 1,305ms | Nov 12, 2026 1:20 AM | |
| Online | 200 | 1,148ms | Nov 12, 2026 1:15 AM | |
| Online | 200 | 1,106ms | Nov 12, 2026 1:10 AM | |
| Online | 200 | 1,164ms | Nov 12, 2026 1: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 20,136 recorded checks between Sep 3, 2026 and Nov 12, 2026 . Response times are measured from our checker, not from your location.