11 of 11 points with fresh data
Last 24 hours at a glance
Lowest web success among sampled points
98.96%
Response time
653 ms
Incidents
1
Web failure at any point
15.00 min
24-hour sample coverage
100%
Percentage source: Hetzner Falkenstein
Monitoring from multiple servers
11 of 11 points with fresh data
Every service is checked from eligible Linux servers in Iran and abroad. A website’s domestic or international category does not restrict its monitoring points.
Checks behind this status
Current status source: Afranet Tehran
No public, unauthenticated, read-only endpoint was found for this service, so the check is reported as not configured rather than shown as a fabricated success.
24-hour trend
This timeline uses actual hourly samples and confirmed events from each point. Green means recorded samples passed; clipped boundary hours and windows without samples stay grey and are not assumed healthy.
- Available
- Slow
- Failed
- No data
History last fetched: 13 Nov 2026, 20:40
Hourly history may refresh every five minutes; the latest current check time is independent.
Incidents in the last 24 hours
- Covered: Zarminex unavailable from hetznerHetzner FalkensteinDuration in this window: 15.00 min13 Nov 2026, 10:17Resolved
Separate Alpha central monitoring history
These are central Alpha checks preceding distributed monitoring. They are not merged with samples from the new node checks.
Alpha / Shatel DC2 · 100.00% · 24-hour sample coverage: 100.0%
- Available
- Slow
- Failed
- No data
History last fetched: 13 Nov 2026, 20:40
Measurement source
- Monitoring system
- Covered.ir
- Method
- Web and API checks from each eligible Linux server, every 60 seconds
- Last checked
- 13 Nov 2026, 20:44
- HTTP response code
- 200
Website status uses web and API checks from Covered monitoring points; users elsewhere may have a different experience. Missing or stale data is not treated as healthy.