How Iszdown tracks outages
Iszdown helps you check service availability, follow emerging problems, and explore past incidents.
Reports and estimated activity
Recorded outage reports and estimated activity are displayed separately. Estimates use a relative 0–100 scale: 100 marks the peak within that service and time window, not 100 submitted reports or affected users. Independently scaled services, countries, and time windows cannot be compared as absolute report counts.
Website performance
Website checks measure connectivity and response time, not full page load, sign-in, or every application feature. Success percentages describe sampled checks, not continuous uptime. Restricted requests and missing checks remain inconclusive. Slowness alone does not identify server load as the cause.
Updates and missing data
Popular services receive priority. Observation times are shown alongside results. Updates may be delayed, partial observations are excluded, and missing samples remain blank. An empty graph or zero reports does not guarantee that a service works for everyone. Emerging activity alone does not confirm an outage.
Disruption activity index
When a current activity estimate is unavailable, the service page charts an evidence index from 0 to 100. Published minor, major, and critical incidents score 40, 80, and 100 during their recorded duration. A website check failure scores 40; repeated failures within 20 minutes score 80. Authentication and bot challenges are excluded. Recorded reports contribute a capped score of 75; corroborated problem-pattern ranking changes contribute at most 30 after a mature history baseline. Each ten-minute bucket uses its strongest evidence. Archived healthy status observations are plotted in their recorded hour; these are hourly buckets rather than exact check times. Missing buckets remain unknown; connecting lines do not add observations. This index is not a report count, outage probability, or percentage of affected users, and a zero does not establish uninterrupted service.
Daily outage history
Calendar dates use America/New_York. Pink marks detected service issues; select a day to see its details. Green means no issues observed with sufficient monitoring coverage, not guaranteed uninterrupted uptime. Gray means insufficient coverage. Today’s result can change. Activity estimates alone do not turn a day pink.
Country-specific coverage
Country pages show local observations and reference times when available. Missing country data is never replaced with another country’s data. Global incidents do not establish local impact.
Historical incident articles
Blog articles document the event date shown. They do not establish availability right now. Check the live service page for current status.
Citing Iszdown
Link to the specific service page, include your access time and the displayed observation time, and distinguish recorded reports from estimated activity. Recheck current status before publishing.
Iszdown is independent of the services it monitors. Product names belong to their respective owners.