Instana Status Page Calendar Shows Resolved Incidents as Ongoing in Timeline View

The Instana public status page calendar (https://status.instana.io/calendar) displays historical incidents as if they are still ongoing in the Day/Week timeline view, even when those incidents are marked as Resolved or Closed.

In the timeline visualization:

• Multiple past incidents appear as long-running bars extending across several hours (or the full day).
• The visual duration does not match the actual incident duration.
• This creates the impression that incidents are still active, even though the status clearly shows “Resolved” or “Closed” within the event card.

Observed Behavior

• Events with a defined start time (e.g., ~11:23 AM UTC) render as continuous blocks across the timeline.
• End times are either:
  • Not visually represented, or
  • Not respected in the timeline rendering
• This results in misleading visualization of incident duration
• Issue is most visible in:
  • Day view
  • Week view

Expected Behavior

• Timeline bars should:
  • Accurately reflect both start AND end times
  • Stop rendering once the incident is resolved/closed
• No event should visually extend beyond its actual duration
• Visualization should align with:
  • Event details
  • Agenda view (which typically shows correct timestamps)

Suggested Enhancements

Fix timeline rendering logic

• Ensure end timestamps are always honored
• Do not default to full-day rendering when end time exists

Improve UI clarity

• Display explicit start and end times on hover or directly on the event
• Visually distinguish:
  • Active vs resolved events
  • Ongoing vs completed incidents

Add safeguards

• If end time is missing:
  • Clearly label as “ongoing” instead of stretching visually
• Validate backend data consistency for incident duration

Optional UX improvements

• Add tooltip: “Duration: X mins”
• Provide toggle:
  • “Accurate duration view” vs “stacked view” (current)

Impact:
Creates confusion for customers monitoring platform health

• Gives the false impression of:
  • Long-running or ongoing outages
  • Reduced platform reliability
• Leads to:
  • Increased support queries
  • Misinterpretation during incident reviews and audits
• Impacts trust in the status page as a reliable source of truth