All Systems Operational

Updated 2 minutes ago

Scheduled Maintenance

18.3 Release DeploymentScheduled Maintenance

Schedule

November 6, 2018 2:30AM - November 8, 2018 11:59PM MST

Components

Workfront Status, WorkfrontDAM, Workfront Fusion, Workfront API, Proofing

Locations

CL01, CL02, CL03, CL04, CL05, WorkfrontDAM, Workfront Fusion, Proof Processing, Proof Web Application, Proof API, Proof Email

Description

The deployment of the 2018.3 release will start for each cluster and subcomponent as follows: Proofing: November 6 at 2:30 a.m., MST Clusters 2 and 4: November 7 at 8:00 p.m., MST Clusters 1, 3, and 5: November 8 at 8:00p.m., MST This post will be updated when the deployment on each cluster is complete.

Workfront Status




Operational

WorkfrontDAM




Operational

Workfront Fusion




Operational

Workfront API




Operational

Proofing




Operational

External Services

AWS S3

Workfront Uptime

99.99%




Avg. Response Time

152.75ms




Avg. Round Trip

236.39ms




Total Requests

288298.33 Hits




Workfront Uptime

100.00%




Avg. Response Time

169.58ms




Avg. Round Trip

261.38ms




Total Requests

229783.13 Hits




Workfront Uptime

99.99%




Avg. Response Time

167.82ms




Avg. Round Trip

248.48ms




Total Requests

264818.55 Hits




0

Active Incidents

0

Active Maintenances

1

Upcoming Maintenances

Maintenance Windows North America: CL01 | CL02 | CL03 | CL05 2nd and 4th Saturday 8:00 pm to 12:00 am MT 1st and 3rd Thursday 8:00 pm to 12:00 am MT EMEA: CL04 1st and 3rd Friday 2:00 am to 4:00 am GMT CL01, CL02, CL03, CL05 Preview environments refresh on Saturday CL04 Preview environment refreshes on Friday **We infrequently schedule maintenance in the windows listed above. If down time is necessary, it will be scheduled in the corresponding window and announced on this page.**

History (Last 21 days)

Incident Status

Component Disruption - SEV 3


Components

Workfront Status


Locations

CL05




October 4, 2018 4:18PM MDT
[Investigating] We have received reports from a few customers stating individual domains are inaccessible. We are currently investigating the problem.

October 4, 2018 4:35PM MDT
[Identified] We believe we have identified the cause of the problem and have pushed a fix. We are continuing to monitor the situation.

October 4, 2018 4:47PM MDT
[Monitoring] Domains are now active for all reported customers. Continuing to monitor.

October 4, 2018 4:55PM MDT
[Resolved] We have determined that all affected domains are now corrected. It appears the cause was due to a mistake made when updating some DNS entries.