Is there an Permutive outage?
Permutive status: Systems Active
Last checked: a minute ago
Get notified about any outages, downtime or incidents for Permutive and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: a minute ago
Get notified about any outages, downtime or incidents for Permutive and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Permutive.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| AMP API | Active |
| Content Delivery Network | Active |
| Permutive Analytics | Active |
| Permutive API | Active |
| Permutive Dashboard | Active |
| Permutive SDKs | Active |
| Routing | Active |
| Third-Party Data API | Active |
View the latest incidents for Permutive and check for official updates:
Description: Service has remained fully restored. We are continuing our investigation to find the root cause of the incident and our engineering team will plan infrastructure improvements to reduce the risk of downtime in future.
Status: Resolved
Impact: None | Started At: Dec. 6, 2017, 10 a.m.
Description: A bug was deployed to our JavaScript SDK which caused a period of event tracking failure for a small subset of customers, between 17:00UTC and 19:20UTC. This issue only affected customers who use Permutive's third-party data integrations. A fix has been deployed and event collection has returned to usual.
Status: Resolved
Impact: None | Started At: Nov. 23, 2017, 7:41 p.m.
Description: A bug was deployed to our JavaScript SDK which caused a period of event tracking failure for a small subset of customers, between 17:00UTC and 19:20UTC. This issue only affected customers who use Permutive's third-party data integrations. A fix has been deployed and event collection has returned to usual.
Status: Resolved
Impact: None | Started At: Nov. 23, 2017, 7:41 p.m.
Description: Our API experienced a large spike in traffic at 13.05 UTC. This caused our cluster to autoscale to its maximum capacity, but this wasn't enough to handle the additional load. All of our API instances were simultaneously overloaded, causing our cluster to become non-responsive, and we weren't able to rebuild the cluster until 14:32 UTC. We have now 2x over-provisioned our API cluster to reduce the risk of this happening again and will be replicating our API in more geographical regions to increase availability. We are currently investigating the time taken to rebuild the cluster, and will be taking steps to speed up this process in the future.
Status: Resolved
Impact: Minor | Started At: July 11, 2017, 1:47 p.m.
Description: Our API experienced a large spike in traffic at 13.05 UTC. This caused our cluster to autoscale to its maximum capacity, but this wasn't enough to handle the additional load. All of our API instances were simultaneously overloaded, causing our cluster to become non-responsive, and we weren't able to rebuild the cluster until 14:32 UTC. We have now 2x over-provisioned our API cluster to reduce the risk of this happening again and will be replicating our API in more geographical regions to increase availability. We are currently investigating the time taken to rebuild the cluster, and will be taking steps to speed up this process in the future.
Status: Resolved
Impact: Minor | Started At: July 11, 2017, 1:47 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
