All Systems Operational

About This Site

At Permutive, we strive to deliver you a fast, stable, and reliable service.

From here, you can monitor the current and historical status of Permutive, including any issues or incidents we may have had. If you're ever experiencing any problems with our services, you can always get in touch at support@permutive.com.

Content Delivery Network Operational
Permutive API Operational
Permutive Dashboard Operational
Permutive Analytics Operational
Permutive SDKs Operational
Third-Party Data API Operational
AMP API Operational
Routing Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
API - Uptime
Fetching
API - Response Time ?
Fetching
Data Ingestion API - Uptime
Fetching
Data Ingestion API - Response time
Fetching
Dashboard - Uptime
Fetching
Permutive.com Uptime
Fetching

Sep 16, 2026

No incidents reported today.

Sep 15, 2026

No incidents reported.

Sep 14, 2026

No incidents reported.

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

No incidents reported.

Sep 10, 2026

No incidents reported.

Sep 9, 2026

No incidents reported.

Sep 8, 2026

No incidents reported.

Sep 7, 2026

No incidents reported.

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Sep 4, 2026

No incidents reported.

Sep 3, 2026

Resolved - Between 21:14 and 22:13 UTC on 3 September, the CCS (Custom Cohort Segmentation) API experienced degraded performance. During this period the large majority of segmentation requests failed with HTTP 500 errors after a delay of several seconds.

Events sent in the affected requests were still collected. However, users were not segmented and no cohorts were returned from those requests.

This only affected segmentation done via direct calls to the CCS API. Requests outside this window were unaffected. The issue is now resolved and the API has returned to normal.

This was caused by a failure in an upstream service which impacted the CCS API. Improvements to both the upstream service and the CCS API have been identified and are being worked on which will prevent a reoccurrence of this failure and its impact.

Sep 3, 20:00 UTC

Sep 2, 2026

No incidents reported.