Skip to main content

Status & Incident Playbook

How Toggly communicates incidents and how to respond.

Status Page​

Check Toggly's status at status.toggly.io:

  • Service Status: Current status of all services
  • Incident History: Past incidents and resolutions
  • Scheduled Maintenance: Upcoming maintenance windows
  • Subscribe: Get notified of status changes

Incident Communication​

Status Updates​

During incidents, Toggly provides:

  • Initial Alert: Immediate notification of issue
  • Progress Updates: Regular updates every 15-30 minutes
  • Resolution: Notification when issue is resolved
  • Post-Mortem: Detailed post-incident report

Notification Channels​

  • Status Page: Real-time updates on status page
  • Email: Email notifications (if subscribed)
  • X / Twitter: Updates on @toggly_app
  • Slack: Updates in Toggly Slack workspace

Incident Response​

During an Incident​

  1. Check Status Page: Verify issue is known
  2. Monitor Updates: Watch for progress updates
  3. Use Cached Values: SDKs use cached values when available
  4. Have Fallback: Implement fallback behavior

After Resolution​

  1. Verify Functionality: Test feature flags
  2. Clear Cache: Clear SDK caches if needed
  3. Review Post-Mortem: Read incident post-mortem
  4. Update Procedures: Update procedures if needed

Best Practices​

  1. Subscribe to Updates: Get notified of incidents
  2. Monitor Status: Check status page regularly
  3. Have Fallbacks: Implement fallback behavior
  4. Test After Incidents: Verify functionality after resolution

Next Steps​