Status pages & incident communication — found from sitemap — Phare Uptime

Cited by

Facts read from this source

• Auto incident creation Report an error

  “When a monitor detects trouble (respecting your confirmation settings and any keyword/SSL checks), Phare springs into action by creating an incident.”

• Manual incidents Report an error

  “Phare makes it easy to create incidents manually: Select the affected monitor(s) Set the impact level Add a descriptive title Include details about the situation”

• Auto recovery Report an error

  “When your service recovers (again, respecting your recovery confirmation settings), Phare automatically resolves the incident and notifies recipients through your alert rules.”

• Impact levels Report an error

  “Unknown: Still investigating, not sure how bad it is Maintenance: The service is unavailable because of planned work Degraded performance: Things are slower / working less well than usual Partial outage: Some users are affected or certain features are down Major outage: Everything is on fire, users can’t access the service or are severely impacted”

• Incident downtime exclusion Report an error

  “An incident can also be excluded from downtime calculations, for example when the downtime is already part of your SLA. Excluded incidents are not counted in the downtime shown in your dashboard and on status pages.”

• Incident tags Report an error

  “Incidents can be organized with tags, such as environment:production or priority-1, shared across your whole organization.”

• Event timeline Report an error

  “The event timeline gives you the full picture of what happened during an incident. You can see every region’s status, which alert rules fired, and follow the incident’s progression from start to finish.”

• Private comments Report an error

  “Comments are only visible to organization members and never appear on public status pages.”

• Incident updates Report an error

  “Each update allows you to communicate progress as you mitigate the issue and is automatically published to connected status pages, helping maintain transparency with users during outages. Each update has a state (investigating, identified, monitoring or resolved) and a publication time.”

• Smart incident merging Report an error

  “Smart incident merging reduces noise by grouping multiple, similar failures into a single incident that evolves over time.”

• Merge window recommendation Report an error

  “Start with a moderate window of 10 to 30 minutes.”

• Dedicated alert events Report an error

  “Two alert rule events are available to help you react precisely to incident propagation and partial recoveries: Incident Propagated Incident Partially Recovered”

• Incident notification threads Report an error

  “Paired with notification threads on the Email, Discord, or Slack integrations, notifications stay focused: one creation, threaded follow‑ups for expansions and partial recoveries, and a final recovery when everything is back to normal.”

• Incident AI Report an error

  “Incident AI leverages the Mistral AI platform to analyze incident data and generate useful summaries and post-mortem reports.”

• Incident AI model Report an error

  “This feature is powered by Mistral Small 4, a lightweight model that provide fast reasoning with lower costs and energy use.”

• Incident AI config Report an error

  “Incident AI can be activated per-project, allowing compliance with different data policies across your organization.”

• Incident AI credits Report an error

  “Each AI generation consumes one credit from your plan’s monthly allowance. When the quota is exhausted, no further AI generation is performed until the next billing cycle. Additional quota can be configured if your organization is subscribed to the Scale plan.”

• Incident AI redaction Report an error

  “Sensitive data like monitor name, API keys, HTTP header values, or user emails are redacted with anonymization tokens in the payload sent to Mistral AI. Phare uses Mistral’s paid plan which does not train artificial intelligence models on your data.”

• Incident AI feedback usage Report an error

  “Only rated AI generations will be used for this purpose.”

Scores citing this record

• The Agency Developer Alerting, escalation & on-call
• The Customer Support Lead Alerting, escalation & on-call
• The Customer Support Lead Status pages & incident communication
• The E-Commerce Operations Manager Alerting, escalation & on-call
• The E-Commerce Operations Manager Status pages & incident communication
• The SaaS Platform Engineer Alerting, escalation & on-call
• The SaaS Platform Engineer Status pages & incident communication
• The Information Security Officer Alerting, escalation & on-call
• The Information Security Officer Status pages & incident communication
• The Information Security Officer Pricing transparency
• The Skeptic Alerting, escalation & on-call
• The Skeptic Status pages & incident communication