Get email notifications whenever Arc XP creates, updates or resolves an incident.
Get text message notifications whenever Arc XP creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get incident updates and maintenance status messages in Microsoft Teams channel.
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever Arc XP creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
All Systems Operational
About This Site
This page will be updated to reflect any product incidents we are aware of which cause customer impact. During any such incidents, status updates will be posted here regularly.
Postmortems will be added to incidents after internal review has been completed.
Please visit https://support.arcpublishing.com to access our support portal, where you can access documentation and support tickets.
This Status Page is to be used for informational purposes only.
Content Platform
Operational
Publishing Platform
?
Operational
Migration Center
?
Operational
View API
?
Operational
Developer Experience & SDKs
Operational
Themes
?
Operational
Mobile SDK
?
Operational
IFX
?
Operational
Creator Apps
Operational
Composer
?
Operational
WebSked
?
Operational
PageBuilder Editor
?
Operational
Photo Center
?
Operational
Video Center
?
Operational
Content Intelligence
Operational
Arc Intelligence
?
Operational
Recommendations
?
Operational
Platform & Delivery Acceleration
Operational
PageBuilder Engine
?
Operational
Web Delivery
?
Operational
Revenue Engine
Operational
Subscriptions
?
Operational
Partner Products
Operational
Queryly
?
Operational
Akamai Botman
?
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Oct 26, 2025
No incidents reported today.
Oct 25, 2025
No incidents reported.
Oct 24, 2025
No incidents reported.
Oct 23, 2025
Resolved -
This incident has been resolved.
Oct 23, 19:40 EDT
Oct 23, 19:40 EDT
Update -
The backlog has been fully cleared. All past updates have been processed, and new updates are being handled live for both Composer and programmatic ingestion. Any remaining errors can be resolved by republishing affected content. Customers should now be able to work normally across all environments.
Oct 23, 12:56 EDT
Oct 23, 12:56 EDT
Update -
The majority of content published in the past 12 hours has now been processed. New content may still experience delays while full recovery continues. We will confirm once all processing times have returned to normal levels.
Oct 23, 11:40 EDT
Oct 23, 11:40 EDT
Update -
We've increased capacity, and content updates are now processing quickly. Full recovery may take a few more hours, we'll continue providing updates and confirm once systems are fully back to normal. Thank you for your patience as we work through this.
Oct 23, 10:45 EDT
Oct 23, 10:45 EDT
Update -
As mentioned in our previous updates, we have largely increased capacity and the backlog of content updates is being processed rapidly. Due to the large volume of updates however, we expect full recovery to take some time still (a few hours, not days). We will continue to provide regular updates as well as an "all clear" once we are back to normal.
We appreciate your patience as we work through this recovery.
Oct 23, 09:27 EDT
We appreciate your patience as we work through this recovery.
Oct 23, 09:27 EDT
Update -
As mentioned in our previous updates, we have largely increased capacity and the backlog of content updates is being processed rapidly. Due to the large volume of updates however, we expect full recovery to take some time still (a few hours, not days). We will continue to provide regular updates as well as an "all clear" once we are back to normal.
We appreciate your patience as we work through this recovery.
Oct 23, 09:13 EDT
We appreciate your patience as we work through this recovery.
Oct 23, 09:13 EDT
Update -
Due to the large backlog of operations, some stories that were created, saved, or updated in the past couple hours may not yet be processed. This may result in stories not showing up on the web, or in the Composer search. In most cases, simply republishing those stories via Composer is enough to rectify them.
We are adding capacity and taking steps to accelerate the processing of the backlog to remediate this situation as fast as possible.
We will continue posting updates on a regular basis.
Oct 23, 07:27 EDT
We are adding capacity and taking steps to accelerate the processing of the backlog to remediate this situation as fast as possible.
We will continue posting updates on a regular basis.
Oct 23, 07:27 EDT
Update -
We have resolved the secondary issue with the Kafka cluster, and the processing pipelines is now working as expected. Changes in Composer (and other updates of priority "standard") should reflect normally in Content API for all organizations. For programmatic updates (Arc-Priority: ingestion), there is a backlog that is currently being processed, and may take up to a couple hours to clear up. Some of this backlog is within the range of our normal processing times for customers with large ingestion volumes, but may be more elevated for some.
If some important stories are out of sync, a re-publish in Composer should bring them to an updated status.
We will continue providing regular updates until all metrics are back to normal levels.
Oct 23, 06:36 EDT
If some important stories are out of sync, a re-publish in Composer should bring them to an updated status.
We will continue providing regular updates until all metrics are back to normal levels.
Oct 23, 06:36 EDT
Update -
We have identified a secondary issue with our Kafka cluster and are working with our infrastructure provider to resolve it. This affects a subset of customers for whom stories are either delayed or not being processed. We will continue to provide updates as the situation progresses.
Oct 23, 05:10 EDT
Oct 23, 05:10 EDT
Update -
Operations with Arc-Priority: ingestion are still being processed with a delay. As we continued our investigation however, we became aware of a disruption for messages from Composer (messages with Arc-Priority: standard) for a subset of customers. Changes in Composer may not reflect in Content API and thus the web. This is being actively investigated.
Oct 23, 04:13 EDT
Oct 23, 04:13 EDT
Update -
Operations with Arc-Priority: ingestion are still being processed with a delay. As we continued our investigation however, we became aware of a disruption for messages with priority "standard" for a subset of customers. Changes in stories may not reflect in Content API and thus the web. This is being actively investigated.
Oct 23, 04:08 EDT
Oct 23, 04:08 EDT
Update -
Many publishing features have returned to normal operation. We are continuing to monitor metrics as recovery continues.
Oct 23, 03:25 EDT
Oct 23, 03:25 EDT
Update -
At this time, Composer and Websked applications are expected to be responsive to search & publishing actions. Any applications leveraging the Arc-Priority: standard are also expected to be arriving in a timely manner.
Customer Applications that are leveraging the Arc-Priority: ingestion are expected to be slightly delayed but are actively being processed.
Oct 23, 02:20 EDT
Customer Applications that are leveraging the Arc-Priority: ingestion are expected to be slightly delayed but are actively being processed.
Oct 23, 02:20 EDT
Update -
System monitoring points to solid recovery metrics and delays are trending downwards. Engineering teams continue to be engaged until the event is resolved.
Oct 23, 01:33 EDT
Oct 23, 01:33 EDT
Update -
Content operations continue to clear through the backlog queue. Monitoring by the full response team is ongoing.
Oct 23, 00:54 EDT
Oct 23, 00:54 EDT
Update -
We have observed an improvement in content operations clearing through the backlog queue. Our team is still engaged after scaling infrastructure components and we continue to monitor the situation.
Oct 23, 00:15 EDT
Oct 23, 00:15 EDT
Update -
We continue to process the backlog of content operations and are working to restore the stability of publishing times.
Oct 22, 23:42 EDT
Oct 22, 23:42 EDT
Update -
We continue to process the backlog of content operations and are seeing an improvement in article publish times. The team is scaling additional infrastructure components to further increase processing velocity and restore publish times to normal levels.
Oct 22, 23:09 EDT
Oct 22, 23:09 EDT
Update -
We are continuing to monitor the progress of mitigation of delays across the region.
Oct 22, 22:19 EDT
Oct 22, 22:19 EDT
Update -
Photo Center and Video Center are back to full capacity and normal operation.
We are continuing to monitor for any further issues.
Oct 22, 21:33 EDT
We are continuing to monitor for any further issues.
Oct 22, 21:33 EDT
Update -
We are continuing to monitor for any further issues.
Oct 22, 20:52 EDT
Oct 22, 20:52 EDT
Update -
Processing times have been observed to continue to improve as expected. We expect normal operational levels within in hour.
Oct 22, 20:20 EDT
Oct 22, 20:20 EDT
Update -
The cluster reboot has resolved the connectivity issues, and Kafka queues are now processing messages normally. The team has scaled up message topics and supporting infrastructure to accelerate backlog processing. Customers should see continued improvement as the queues clear and content operations return to normal performance.
Oct 22, 20:00 EDT
Oct 22, 20:00 EDT
Update -
We are investigating a potential root cause related to a recent AWS patch that may have affected the stability of our Kafka cluster. As part of mitigation efforts, we are rebooting the cluster to re-establish component connectivity.
Oct 22, 19:47 EDT
Oct 22, 19:47 EDT
Update -
We are now observing an increase in delays affecting content operations, including publishing in the us-east-1 region. Engineering is investigating elevated latency in the content synchronization layer and is working to mitigate the impact. Further updates will be provided as we learn more.
Oct 22, 19:09 EDT
Oct 22, 19:09 EDT
Update -
We are continuing to monitor the progress of mitigation of delays across the region. Some customers will still see delays but we expect this improve over time.
Oct 22, 18:17 EDT
Oct 22, 18:17 EDT
Monitoring -
A fix has been applied and is propagating across the system. The content operations delay is now about five minutes and is continuing to decrease.
Oct 22, 17:37 EDT
Oct 22, 17:37 EDT
Identified -
There is delay for our internal routing for content synchronization at around 4:30 PM ET which led to a 10 minute delay in Content Operations. This incident is limited to customers located in the us-east-1 region.
Oct 22, 17:17 EDT
Oct 22, 17:17 EDT
Oct 22, 2025
Resolved -
The issues affecting the Photo Center UI have been fully resolved. Service has been restored across all regions, and the application is operating normally.
We will continue to monitor performance to ensure stability. Thank you for your patience while we worked to resolve this incident.
Oct 22, 13:35 EDT
We will continue to monitor performance to ensure stability. Thank you for your patience while we worked to resolve this incident.
Oct 22, 13:35 EDT
Update -
We’ve identified the root cause of the Photo Center UI issues and have implemented a fix. Service restoration is in progress, and availability should return to normal across various regions shortly.
We continue to monitor performance and will confirm once the issue is fully resolved.
Oct 22, 13:28 EDT
We continue to monitor performance and will confirm once the issue is fully resolved.
Oct 22, 13:28 EDT
Identified -
We are currently investigating issues affecting the Photo Center user interface. Some users may experience errors accessing certain features.
Our engineering teams are actively working to identify the root cause and restore normal functionality as quickly as possible.
We will provide updates as more information becomes available.
Oct 22, 13:22 EDT
Our engineering teams are actively working to identify the root cause and restore normal functionality as quickly as possible.
We will provide updates as more information becomes available.
Oct 22, 13:22 EDT
Oct 21, 2025
No incidents reported.
Oct 20, 2025
Resolved -
All services have been fully recovered.
Video Center services are back to normal state, but all source systems should be double-checked to confirm successful reconnection.
Oct 20, 18:25 EDT
Video Center services are back to normal state, but all source systems should be double-checked to confirm successful reconnection.
Oct 20, 18:25 EDT
Update -
Most services have been fully recovered. Video is still experiencing impaired functionally in some of its features, and it is continuing to process backlogs.
Oct 20, 18:15 EDT
Oct 20, 18:15 EDT
Update -
We are observing recovery in some of our applications. Page Builder deployment and IFX functionality are restored. Changes sent to those applications will possibly need to be retried.
Videos are still being processed in the backlog. And other APIs might still experience service interruptions.
We will continue providing feedback and updates.
Oct 20, 17:23 EDT
Videos are still being processed in the backlog. And other APIs might still experience service interruptions.
We will continue providing feedback and updates.
Oct 20, 17:23 EDT
Update -
In addition to previous reported services, we can confirm that IFX was severely impacted. We are observing partial recovery, with some integrations now restarting.
We are also seeing slow recovery for multiples other services: videos are being processed, but the backlog is significant, and will take time to process.
While access to Arc XP apps and APIs is improving, there are still errors, in particular at integration points, which continues to cause issues with updates not always propagating from one place to another. Our guidance remains to limit changes as much as possible for the time being.
We will continue providing updates as the situation evolves.
Oct 20, 16:40 EDT
We are also seeing slow recovery for multiples other services: videos are being processed, but the backlog is significant, and will take time to process.
While access to Arc XP apps and APIs is improving, there are still errors, in particular at integration points, which continues to cause issues with updates not always propagating from one place to another. Our guidance remains to limit changes as much as possible for the time being.
We will continue providing updates as the situation evolves.
Oct 20, 16:40 EDT
Update -
In addition to previous reported services, we can confirm that IFX was severely impacted. We are observing partial recovery, with some integrations now restarting.
We are also seeing slow recovery for multiple other services: videos are being processed, but the backlog is significant, and will take time to process.
While access to Arc XP apps and APIs is improving, there are still errors, in particular at integration points, which continues to cause issues with updates not always propagating from one place to another. Our guidance remains to limit changes as much as possible for the time being.
We will continue providing updates as the situation evolves.
Oct 20, 16:28 EDT
We are also seeing slow recovery for multiple other services: videos are being processed, but the backlog is significant, and will take time to process.
While access to Arc XP apps and APIs is improving, there are still errors, in particular at integration points, which continues to cause issues with updates not always propagating from one place to another. Our guidance remains to limit changes as much as possible for the time being.
We will continue providing updates as the situation evolves.
Oct 20, 16:28 EDT
Update -
We are continuing to observe significant service degradation across multiple Arc services in the US-East-1 region:
Access to several Arc UI is impacted and may be non-functional for some customers, with PageBuilder editor being the most affected.
There may be issues saving changes in PageBuilder, and saved changed may not reflect on websites, as propagation between the different serving layers is also impacted.
All video encoding services are down.
In addition, access to underlying APIs through Trident is also affected, which results in occasional errors for both APIs and UIs.
We are advising customers in this region to not deploy any new bundle.
Due to the extent of the outage and the number of services affected, we do not have an ETA at this time for full recovery of all services. We will continue to provide regular updates as information becomes available.
Oct 20, 14:56 EDT
Access to several Arc UI is impacted and may be non-functional for some customers, with PageBuilder editor being the most affected.
There may be issues saving changes in PageBuilder, and saved changed may not reflect on websites, as propagation between the different serving layers is also impacted.
All video encoding services are down.
In addition, access to underlying APIs through Trident is also affected, which results in occasional errors for both APIs and UIs.
We are advising customers in this region to not deploy any new bundle.
Due to the extent of the outage and the number of services affected, we do not have an ETA at this time for full recovery of all services. We will continue to provide regular updates as information becomes available.
Oct 20, 14:56 EDT
Update -
Our cloud provider outage continues and some services are degraded. We continue to monitor the situation and take corrective actions when possible.
There is no direct workaround, and availability may occasionally be spotty depending on the service and time.
We will continue providing updates as the situation evolves.
Oct 20, 13:25 EDT
There is no direct workaround, and availability may occasionally be spotty depending on the service and time.
We will continue providing updates as the situation evolves.
Oct 20, 13:25 EDT
Update -
We are continuing to monitor for any further issues.
Oct 20, 13:25 EDT
Oct 20, 13:25 EDT
Update -
We are currently experiencing intermittent issues affecting multiple services. These disruptions appear to be related to an ongoing outage with our cloud provider. Our teams are actively working to restore full functionality and are closely monitoring the situation.
If you encounter any issues, please wait a few minutes and try again. We will continue to share updates as the situation evolves.
Oct 20, 12:16 EDT
If you encounter any issues, please wait a few minutes and try again. We will continue to share updates as the situation evolves.
Oct 20, 12:16 EDT
Update -
We are continuing to monitor for any further issues.
Oct 20, 12:16 EDT
Oct 20, 12:16 EDT
Update -
We are observing sporadic issues on several APIs, most notably WebSked, though others may be affected as well. Those tend to resolve within a few minutes, and appear to remain linked to our cloud provider outage. We are continuing to actively monitor the situation. If you experience issues within any of our apps, wait a few minutes and try again.
We will continue to provide updates as the situation evolves.
Oct 20, 10:35 EDT
We will continue to provide updates as the situation evolves.
Oct 20, 10:35 EDT
Update -
We are continuing to monitor for any further issues.
Oct 20, 10:34 EDT
Oct 20, 10:34 EDT
Update -
We are now seeing partial recovery for Jira was well, and many customers should be able to post tickets.
As a reminder, the recommended course of action for any failed operation during the outage is simply to retry. Saving/republishing stories will fix most editorial issues. Similarly, some stories that were scheduled for publishing may have missed their publishing deadlines. Re-publishing them manually should work as well.
If you continue to experience any other issue at this time, please feel free to contact our support via our regular channels.
Oct 20, 09:46 EDT
As a reminder, the recommended course of action for any failed operation during the outage is simply to retry. Saving/republishing stories will fix most editorial issues. Similarly, some stories that were scheduled for publishing may have missed their publishing deadlines. Re-publishing them manually should work as well.
If you continue to experience any other issue at this time, please feel free to contact our support via our regular channels.
Oct 20, 09:46 EDT
Update -
At this time, Arc XP systems are considered functional, and we've seen recovery across the board. It appears our ticketing platform is still experiencing issues however. If you are in need of urgent assistance, we recommend reaching out to your TAM through the usual channels, which can then escalate internally.
We will continue to provide updates on a regular basis.
Oct 20, 07:18 EDT
We will continue to provide updates on a regular basis.
Oct 20, 07:18 EDT
Monitoring -
We are observing recovery across multiple services and are continuing to actively monitor the situation. At this stage, we recommend retrying any failed action. It may take some time still for all services to be operating normally. We will continue to provide updates as they become available.
Oct 20, 05:59 EDT
Oct 20, 05:59 EDT
Update -
There are no updates at the moment; the system is still down.
Oct 20, 05:07 EDT
Oct 20, 05:07 EDT
Investigating -
We are observing a large global outage in our main infrastructure provider (AWS).
Several services (UI and API) may be affected.
Our ticketing system (JIRA) may also be affected by the same outage, which limits the ability to post support tickets.
Oct 20, 03:58 EDT
Several services (UI and API) may be affected.
Our ticketing system (JIRA) may also be affected by the same outage, which limits the ability to post support tickets.
Oct 20, 03:58 EDT
Oct 19, 2025
No incidents reported.
Oct 18, 2025
No incidents reported.
Oct 17, 2025
No incidents reported.
Oct 16, 2025
Resolved -
We have fixed all of that the tokens that were active. If there are still issues, please redeploy your bundle.
Oct 16, 15:20 EDT
Oct 16, 15:20 EDT
Update -
We have identified that the bundle termination issue is limited to the termination of a *live* bundle. This is generally not advisable, but is currently possible via the API. We are adding additional guardrails to prevent this case. In the meantime, customers are advised to not terminate any live bundle, as this would invalidate their live token, which is used for content retrieval, and could thus negatively affect their site.
Beside this edge case, normal use of the PageBuilder deployer is now deemed safe, and normal operation can resume.
If you have any concerns, or experience any issue with the deployer, please open a new ticket
Oct 16, 14:41 EDT
Beside this edge case, normal use of the PageBuilder deployer is now deemed safe, and normal operation can resume.
If you have any concerns, or experience any issue with the deployer, please open a new ticket
Oct 16, 14:41 EDT
Update -
We rolled back the fix from this morning. Bundles can be deployed and promoted.
However Terminating a bundle can result in the incorrect deactivation of a live token.
We are still working on a permanent fix.
Oct 16, 12:58 EDT
However Terminating a bundle can result in the incorrect deactivation of a live token.
We are still working on a permanent fix.
Oct 16, 12:58 EDT
Monitoring -
A hotfix was released for the PageBuilder deployer, and normal activity can resume. However;
Any deployment made between 5am (US eastern time) and 8am (US eastern time) should be terminated and not used. Using bundles deployed during this time period will cause errors if promoted. Bundles deployed during this time window will need to be redeployed.
Oct 16, 07:58 EDT
Any deployment made between 5am (US eastern time) and 8am (US eastern time) should be terminated and not used. Using bundles deployed during this time period will cause errors if promoted. Bundles deployed during this time window will need to be redeployed.
Oct 16, 07:58 EDT
Update -
We haved determined that the issue may also be caused by any action taken in deployer and is not isolated only to the termination of bundles. While this issue is being investigated, please do not deploy, promote, or terminate any bundle.
Oct 16, 06:44 EDT
Oct 16, 06:44 EDT
Identified -
The issue has been identified and a fix is being implemented.
Oct 16, 05:52 EDT
Oct 16, 05:52 EDT
Investigating -
We have identified an issue with the PageBuilder deployer. The issue is triggered when a bundle is terminated. Customers are advised to not terminate any bundle until the issue is fully resolved.
Terminating a bundle may result in the incorrect deactivation of a live token. If this happens rendering will begin failing. If this occurs to immediately resolve the issue, customers must re-deploy and re-promote the same bundle, as this will recreate the token. We are actively working on a fix for this issue to allow for termination of deployed bundles.
Oct 16, 05:51 EDT
Terminating a bundle may result in the incorrect deactivation of a live token. If this happens rendering will begin failing. If this occurs to immediately resolve the issue, customers must re-deploy and re-promote the same bundle, as this will recreate the token. We are actively working on a fix for this issue to allow for termination of deployed bundles.
Oct 16, 05:51 EDT
Oct 15, 2025
No incidents reported.
Oct 14, 2025
No incidents reported.
Oct 13, 2025
No incidents reported.
Oct 12, 2025
No incidents reported.