@task Project and Portfolio Management Software - AtTask, Inc.
 
OVERVIEW
 
SOLUTIONS
 
SERVICES
 
NEWS
 
LIBRARY
 
COMPANY
 
layout image

Trust.attask.com

AtTask is committed to building and delivering the most secure, reliable and responsive project and portfolio management solution on the market today. As a SaaS provider, we want to offer our customers complete and immediate visibility into our data center operations and system availability. Being accountable to our customers is essential for building and retaining their trust.

We commit to 99.9% service availability, excluding scheduled maintenance and outages caused by circumstances beyond our reasonable control. If you’d like to view and track our real-time uptime statistics, please click here.

http://trust.attask.com is your home for real-time information on @task On-Demand system performance and security. On this site you'll find:

Are you an @task On-Demand customer with suggesions about what you would like to see on this site? Post your suggestions on the @task Community at http://community.attask.com/ideas.

AtTask™ Data Security & Privacy Policy

This page outlines AtTask's policy regarding the security of information stored in the On-Demand @task software and submitted through the AtTask.com website.

@task On-Demand Software Data Security Policy

AtTask will use commercially reasonable efforts consistent with, and no less rigorous than, best industry practices to ensure that appropriate facility and data security procedures and processes are in place to protect against destruction, corruption, loss or alteration of, unauthorized access to, or interference with, any of a customer’s production and other data, accounts, systems, confidential information or customer data created and generated through the use of the @task software.

AtTask.com Website Privacy Policy

AtTask is committed to protecting your privacy and ensuring the security of your information. To prevent unauthorized access or disclosure, to maintain the accuracy of all data and to ensure the appropriate restrictions on use of information, we have put in place appropriate physical, electronic and managerial procedures to safeguard and secure the information we collect online.

This site contains information about our company, products and services. It will also feature success stories about partners and customers, the latest AtTask news, schedules for upcoming events, and possible employment opportunities. We've structured the AtTask Web site so that, in general, you can visit most pages without identifying yourself or revealing personal information. Registration is required for submitting information to and participating in AtTask's knowledge base, forum, and blog.

In some circumstances, AtTask may request personal information from you, such your name, e-mail address and company name or telephone number. Examples include on access to product demos and featured docuements, registration for select services and training courses, participating in a beta program or joining a user group. Your response to these inquiries is strictly voluntary, although it may be necessary to complete the activity with which the information is associated.

AtTask may use this information to customize your experience on our Web site. In addition, AtTask may use this information for other business purposes, such as to alerting you to products and services that can assist you in your business or assisting in order processing. Once you choose to provide us personally identifiable information (any information by which you can be identified), you can be assured that it will only be used to support your relationship with AtTask.

If you do provide personal information, we will not disclose (share, sell or divulge) it to external organizations unless we have informed you or are required to do so by law. We will maintain this information, as well as your business activities and transactions, according to AtTask's normal confidentiality standards.

AtTask also collects domain information as part of its analysis of the use of this site. This data enables us to become more familiar with customer usage of our site. AtTask uses this information to improve its web-based offerings. This information is collected automatically and requires no action on your part.

AtTask's Web site may contain links to Web pages not created and/or owned by AtTask. We make no guarantees or promises about the information on those web sites and cannot accept responsibility for the actions or inaction of their operators.

Changes and Contact Information

If we make material changes to our data security & privacy policy, these changes will be posted to this data security & privacy policy page. You should review this page regularly for updates

If you have comments or questions about our policy, please send them to information [at] attask.com.

 

Performance Status

Speed by Region:

North AmericaAPACEMEASouth America
    
@task Instance Current Status
OnDemand  
Hosting  
Number of Transactions
Avg. Round Trip (in seconds)
Avg. Response Time
 
09/02/10 09/01/10 08/31/10 08/30/10 08/29/10 08/28/10 08/27/10 08/26/10 08/25/10 08/24/10 08/23/10 08/22/10 08/21/10 08/20/10 08/19/10 08/18/10 08/17/10 08/16/10 08/15/10 08/14/10 08/13/10
                                         
                                         
184,143 633,551 615,641 578,800 184,213 154,369 486,057 541,038 562,203 560,612 567,735 182,164 156,241 457,940 530,102 544,516 560,104 578,315 187,427 156,430 453,767
0.388 0.335 0.36 0.353 0.298 0.246 0.323 0.333 0.336 0.349 0.372 0.272 0.22 0.372 0.401 0.385 0.36 0.353 0.263 0.213 0.342
0.085 0.074 0.085 0.079 0.05 0.037 0.079 0.065 0.08 0.086 0.086 0.031 0.039 0.11 0.116 0.11 0.076 0.075 0.029 0.035 0.094
 
Up and Running Up and Running
Service Disruption Service Disruption
Performance Issue Performance Issue
Informational Message Informational Message
 
The number of transactions and average speed are updated every 5 minutes. Date ranges are based on America/Denver (GMT -6:00).
Page load times may vary based on your bandwidth and network latency.

Maintenance Windows

Am I OnDemand or Hosting?
@task Instance Days Time
OnDemand Every Saturday 8:00 pm to 12:00 am MST
Hosting Every Saturday 8:00 pm to 12:00 am MST
helpdesk.attask.com Every Saturday 8:00 pm to 12:00 am MST
OnDemand Beta  What is OnDemand Beta? Every Friday 3:00 pm to 7:00 pm MST
OnDemand Beta data will be re-synced with OnDemand during maintenance. Any changes made to OnDemand Beta will be lost.

Testdrive Expirations

What Testdrive am I using?
Testdrive Server Days Remaining Expiration Date
Testdrive2 2 Days Saturday, September 4, 2010 at 8:00 pm MDT
Testdrive1 9 Days Saturday, September 11, 2010 at 8:00 pm MDT
Testdrive4 16 Days Saturday, September 18, 2010 at 8:00 pm MDT
Testdrive3 23 Days Saturday, September 25, 2010 at 8:00 pm MDT
Service Disruption
When: 07/09/10 11:54 to 07/09/10 12:15 (21 minutes)
What: The AtTask operations team responded to reports that customers were not able to login. AtTask apologizes for any inconveniences experienced during this time.
 
Performance Issue
When: 05/31/10 06:27 to 05/31/10 06:30 (3 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on the On-Demand service. Customers may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
 
1 of 2 incidents
Informational Message Informational Message
When: 05/25/10 12:00
What: The AtTask operations team received notification from customers who's API's were slow to respond. AtTask apologizes for any inconveniences experienced during this time and will begin troubleshooting the problem.
When: 05/23/10 00:00 to 05/25/10 21:00 (-21246840 minutes)
What: The AtTask operations team received notifications from customers that they were experiencing irregular browsing experiences. Issues such as being reverted to the @task home screen and incorrect bread crumb history. Users in some timezones also noticed dates and times were being calculated incorrectly.
Why: An incorrect rule was uploaded to a new set of load balancers. This caused the load balancers to incorrectly maintain application session consistency between application servers causing irregular user browsing experience. This issue was resolved by the load balancer manufacturer and has been pushed to production.
 
Informational Message
When: 05/23/10 00:00 to 05/25/10 21:00 (2 days)
What: The AtTask operations team received notifications from customers that they were experiencing irregular browsing experiences. Issues such as being reverted to the @task home screen and incorrect bread crumb history. Users in some timezones also noticed dates and times were being calculated incorrectly.
Why: An incorrect rule was uploaded to a new set of load balancers. This caused the load balancers to incorrectly maintain application session consistency between application servers causing irregular user browsing experience. This issue was resolved by the load balancer manufacturer and has been pushed to production.
 
Informational Message
When: 05/23/10 00:00 to 05/25/10 21:00 (2 days)
What: The AtTask operations team received notifications from customers that they were experiencing irregular browsing experiences. Issues such as being reverted to the @task home screen and incorrect bread crumb history. Users in some timezones also noticed dates and times were being calculated incorrectly.
Why: An incorrect rule was uploaded to a new set of load balancers. This caused the load balancers to incorrectly maintain application session consistency between application servers causing irregular user browsing experience. This issue was resolved by the load balancer manufacturer and has been pushed to production.
 
Informational Message
When: 05/21/10 13:34 to 05/21/10 13:37 (3 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on one or more On-Demand application servers. Customers who were pinned to app02 may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: A customer was running a large project copy which slowed down the @task service.
 
Service Disruption
When: 05/02/10 00:00 to 05/02/10 09:39 (9 hours)
What: In order to provide better customer service the AtTask operations team migrated our entire @task On-Demand production systems to a Tier3 datacenter facility. The maintenance page had to be kept up for an extended period of time while the migration was taking place. All customers who attempted to log in during this time period would have seen a maintenance page when trying to access their On-Demand instance. AtTask apologizes for any inconveniences experienced during this time.
Why: Production @task On-Demand complete datacenter move
 
Service Disruption
When: 03/16/10 06:59 to 03/16/10 08:30 (1 hour)
What: All services have been restored, AtTask IT department is still investigating root cause of the outage.
Why: Several devices failed and the redundant systems did not failover properly. The AtTask operations team is working with the hardware vendor to make sure failover works as specified by the vendor.
 
1 of 2 incidents
Informational Message Informational Message
When: 03/11/10 00:27 to 03/11/10 00:28 (1 minute)
What: The AtTask operations monitoring tools reported a possible problem with one of the application servers. The server was taken offline and action was take to fix the issue. Customers should not have experienced any problems.
When: 03/11/10 01:09 to 03/11/10 01:10 (1 minute)
What: The AtTask operations monitoring tools reported a possible problem with one of the application servers. The server was taken offline and action was take to fix the issue. Customers should not have experienced any problems.
 
1 of 6 incidents
Service Disruption Performance Issue Performance Issue Performance Issue Informational Message Informational Message
When: 03/10/10 11:50 to 03/10/10 11:51 (1 minute)
What: The AtTask operations team responded to alerts that On-Demand was not accessible to customers. All customers would have seen an emergency maintenance page when trying to access their On-Demand instance. AtTask apologizes for any inconveniences experienced during this time.
When: 03/10/10 11:48 to 03/10/10 11:52 (1 minute)
What: The AtTask operations team responded to alerts that there were performance issues on the On-Demand service. Customers may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
When: 03/10/10 14:05 to 03/10/10 14:13 (1 minute)
What: The AtTask operations team responded to alerts that there were performance issues on one or more On-Demand application servers. Customers who were pinned to app03 or app04 may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
When: 03/10/10 14:48 to 03/10/10 14:50 (1 minute)
What: The AtTask operations team responded to alerts that there were performance issues on the On-Demand service. Customers may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
When: 03/10/10 01:01 to 03/10/10 01:02 (1 minute)
What: The AtTask operations monitoring tools reported a possible problem with one of the application servers. The server was taken offline and action was take to fix the issue. Customers should not have experienced any problems.
Why: Unknown
When: 03/10/10 11:19 to 03/10/10 11:20 (1 minute)
What: The AtTask operations monitoring tools reported a possible problem with one of the application servers. The server was taken offline and action was take to fix the issue. Customers should not have experienced any problems.
Why: Unknown
 
1 of 4 incidents
Service Disruption Performance Issue Informational Message Informational Message
When: 03/09/10 13:43 to 03/09/10 13:47 (4 minutes)
What: The AtTask operations team responded to alerts that OnDemand was not accessible to customers. All customers would have seen an emergency maintenance page when trying to access their OnDemand instance. AtTask apologizes for any inconveniences experienced during this time.
Why: Unknown
When: 03/09/10 13:29 to 03/09/10 13:43 (4 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on the OnDemand service. Customers may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: Unknown
When: 03/09/10 06:03 to 03/09/10 06:07 (4 minutes)
What: The AtTask operations monitoring tools reported a possible problem with one of the application servers. The server was taken offline and action was taken to fix the issue. Customers would not have experienced any problems.
Why: Unknown
When: 03/09/10 22:53 to 03/09/10 22:54 (4 minutes)
What: The AtTask operations monitoring tools reported a possible problem with one of the application servers. The server was taken offline and action was take to fix the issue. Customers should not have experienced any problems.
Why: Unknown
 
1 of 2 incidents
Service Disruption Performance Issue
When: 03/05/10 08:12 to 03/05/10 08:20 (8 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on one or more On-Demand application servers. Customers who were pinned to app02 may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: Unknown
When: 03/05/10 00:55 to 03/05/10 00:57 (8 minutes)
What: The AtTask operations team responded to reports that customers were not able to login. Customers who were pinned to app02 could not login, however, customers that were logged in before the problem happened were not affected. AtTask apologizes for any inconveniences experienced during this time.
Why: Unknown
 
Performance Issue
When: 03/04/10 23:39 to 03/04/10 23:41 (2 minutes)
What: The AtTask operations team responded to reports that customers were not able to login. Customers who were pinned to app01could not login, however, customers that were logged in before the problem happened were not affected. AtTask apologizes for any inconveniences experienced during this time.
Why: Unknown
 
1 of 3 incidents
Performance Issue Performance Issue Performance Issue
When: 03/03/10 00:14 to 03/03/10 00:29 (15 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on one or more On-Demand application servers. Customers who were pinned to app03 may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: A custom report was run that used up all available memory, which caused the application server to slow its response time.
When: 03/03/10 03:07 to 03/03/10 03:12 (15 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on one or more On-Demand application servers. Customers who were pinned to app02 may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: A custom report was run that used up all available memory, which caused the application server to slow its response time.
When: 03/03/10 08:39 to 03/03/10 08:41 (15 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on one or more On-Demand application servers. Customers who were pinned to app01 may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: Unknown
 
Performance Issue
When: 03/01/10 10:15 to 03/01/10 10:24 (9 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on the On-Demand service. Customers may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: A custom report was run that used up all available memory, which caused the application server to slow its response time.
 
1 of 2 incidents
Service Disruption Informational Message
When: 02/21/10 16:14 to 02/23/10 19:00 (2 days)
What: Customers using IE 6 & IE 7 with HTTP 1.0 turned on could not login to On-Demand.
Why: We changed the way we use the compression filter so that it wouldn't interfere with a compression technology we were using elsewhere. In the process we introduced a bug where it wouldn't serve the file if an accept-encoding header was not present in the request. This issue only affected browsers that had HTTP 1.0 settings on.
When: 02/23/10 19:00 to 02/23/10 19:30 (2 days)
What: The AtTask operations team deemed it necessary to apply a patch to the On-Demand systems in order to restore service for some customers. The patch was applied during "off peak" hours and had no impact to the On-Demand service.
Why: The applied patch was to fix a bug dealing with HTML 1.0
 
1 of 3 incidents
Service Disruption Performance Issue Informational Message
When: 02/21/10 16:14 to 02/23/10 19:00 (2 days)
What: Customers using IE 6 & IE 7 with HTTP 1.0 turned on could not login to On-Demand.
Why: We changed the way we use the compression filter so that it wouldn't interfere with a compression technology we were using elsewhere. In the process we introduced a bug where it wouldn't serve the file if an accept-encoding header was not present in the request. This issue only affected browsers that had HTTP 1.0 settings on.
When: 02/22/10 12:38 to 02/22/10 12:43 (2 days)
What: The AtTask operations team responded to alerts that there were performance issues on the On-Demand service. Customers may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: A custom report was run that used up all available memory, which caused the application server to slow its response time.
When: 02/22/10 10:00 to 02/22/10 08:00 (2 days)
What: The AtTask operations team received notification from customers who's API's were working before the weekends code roll, but are no longer returning data. AtTask apologizes for any inconveniences experienced during this time.
Why: A fix to a bug in Clik cause the domain authentication to stop working for some of @task API calls. This was fixed by turning domain authentication off.
 
Service Disruption
When: 02/21/10 16:14 to 02/23/10 19:00 (2 days)
What: Customers using IE 6 & IE 7 with HTTP 1.0 turned on could not login to On-Demand.
Why: We changed the way we use the compression filter so that it wouldn't interfere with a compression technology we were using elsewhere. In the process we introduced a bug where it wouldn't serve the file if an accept-encoding header was not present in the request. This issue only affected browsers that had HTTP 1.0 settings on.
 
1 of 2 incidents
Performance Issue Performance Issue
When: 02/19/10 06:25 to 02/19/10 06:30 (5 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on the On-Demand service. Customers may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: A custom report was run that used up all available memory, which caused the application server to slow its response time.
When: 02/19/10 10:32 to 02/19/10 10:35 (5 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on the On-Demand service. Customers may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: A custom report was run that used up all available memory, which caused the application server to slow its response time.
 
Performance Issue
When: 02/18/10 18:33 to 02/18/10 18:45 (12 minutes)
What: The AtTask operations team responded to alerts that there were performance issues on the On-Demand service. Customers may have observed slow response times, issues saving and retrieving data, and other system errors. AtTask apologizes for any inconveniences experienced during this time.
Why: A custom report was run which used up all available memory, which caused the application server to slow its response time.
 

What System Are You Using?

The instance your organization uses is indicated in the browser's Address bar, shown highlighted below.
 

What is OnDemand Beta?

OnDemand Beta gives your organization a chance to experience new functionality in @task before it is officially released.

The Beta environment can be accessed at: https://yourDomain.attaskbeta.com Replace yourDomain with your OnDemand account.

Keep in mind that any changes made in Beta will not be reflected in your OnDemand environment. Beta is strictly for evaluation purposes.

 

What Testdrive am I using?

Your Testdrive number is shown after "testdrive" in your testdrive URL.
 

Am I OnDemand or Hosting?

If the URL your company uses has "attask-ondemand" in it, you're on OnDemand. If not, you're on Hosting.
 
 
Privacy Policy