About this status page

What the status covers

How to read uptime

Uptime reflects availability during the time covered by our checks. Missing checks remain unknown and never count as successful checks. We show a service's uptime percentage once there are enough measurements to report it.

Older history uses five-minute summaries. Small gaps in monitoring do not indicate downtime. Cloud streaming history starts when its monitoring began.

Each bar represents one UTC day. Its colour reflects measured service health for that day. On days with limited data, green shows the observed healthy portion and stripes show monitoring gaps. Hover a bar for measured uptime and check details.

• Green: operational.
• Amber: degraded service.
• Red: service disruption.
• Striped: limited monitoring data, not a confirmed outage.
• Dark: not measured yet.

Incidents and maintenance

Published incidents show the affected services and a timeline of updates. Recorded disruptions remain in uptime history even when no incident was published.

Planned maintenance is excluded from downtime only within an announced maintenance window. Maintenance updates remain in the incident history.

Current status and updates

Current status combines recent checks and published incidents. When checks are missing or delayed, the page shows that uncertainty. It refreshes every minute, and all times are in UTC.

Follow incident updates through the RSS feed, or read service health and uptime history in the Status API. These publish service summaries without customer data, stream counts or infrastructure identifiers.

Need help with a stream?

An individual stream or destination platform can have a problem while the service status is operational. Contact support for help, or visit the Help Center.