2.2.60 — System Update

What changed

• Added a Recent Availability card to model detail pages.
• Added heartbeat bars for the recent delivery window.
• Added hover and keyboard-focus tooltips with date, time, availability percentage, and status.
• Counted retried or fallback-routed requests as healthy when the request ultimately succeeds.

How to read it

The card reports observed delivery, not a synthetic uptime probe.

If Apertis has recent successful delivery for a model, the relevant heartbeat bucket is green. If an actual delivery failure is observed, the bucket can move to degraded or unavailable based on the observed success rate.

When there is no recent traffic for a bucket, Apertis treats that silence as no observed anomaly and displays it as green 100%. This keeps the signal aligned with the rule that a model should not look unhealthy just because no one called it during that interval.

Why this matters

You can now check model-level health from the same page where you review pricing, context, endpoints, and examples. Teams choosing between models can see recent delivery quality without waiting for a separate status page or paying for active probes.

The implementation stays cost-aware by using delivery results Apertis already sees during normal routing.

Enjoy it.