System Status
——:—— ISTLive health of the APIN plant-disease service. This page refreshes itself every 30 seconds.
Checking system status…
Contacting the status feed…
External Availability
ground-truth uptime measured from outside the containerURL-reachable — HTTP 2xx + valid response shape + latency under SLO. This is what users see. Fully-healthy (smaller number underneath) additionally requires every component to report up AND no resource alerts — the stricter engineering SLO. The two numbers will diverge during ops-only incidents (high memory, degraded subsystem) that don't affect responses.
Probe sources (last 24h)
independent vantage points; disagreement reveals network-path issuesRecent external incidents
failed probes from the last 7 daysComponent Health
90-day history · one cell per day · inside-the-container viewRecent pulse
recent heartbeats · hatched marks are gapsPast incidents
component faults in the 90-day recordPast interruptions
monitor gaps in the last 48 hoursUptime bars fill in over time — a brand-new deployment shows mostly “no data” until 90 days of heartbeats accumulate. Past incidents are component faults recorded while APIN was running. Past interruptions are gaps in the heartbeat stream — a crash, a redeploy, or the free Space going to sleep, when nothing was alive to record a heartbeat. A total outage of the Space is also tracked by a separate external monitor.