TrackAbout System Status
All Systems Operational

About This Site

Sometimes things go wrong. On the rare occurrence they do, we want to be as transparent about our status as we can.

So if things aren't entirely green and operational, just know that it's not you. It's us. And we're working on it.

You can use this page to sign up for notifications about upcoming maintenance and real-time alerts about service issues.

Production Services Operational
90 days ago
99.98 % uptime
Today
Production Application Web Site ? Operational
90 days ago
100.0 % uptime
Today
Production TAMobile 6 Sync Services ? Operational
90 days ago
100.0 % uptime
Today
TAMobile 7 iOS ? Operational
90 days ago
100.0 % uptime
Today
TAMobile 7 Android Operational
90 days ago
100.0 % uptime
Today
Application-Sent Email Delivery ? Operational
90 days ago
100.0 % uptime
Today
Custom Reports and OpenData ? Operational
90 days ago
99.84 % uptime
Today
Production SFTP ? Operational
90 days ago
100.0 % uptime
Today
Production FTPS ? Operational
90 days ago
100.0 % uptime
Today
Customer Test Services Operational
90 days ago
100.0 % uptime
Today
Customer Test TAMobile 6 Sync Services ? Operational
90 days ago
100.0 % uptime
Today
Customer Test Application Web Site ? Operational
90 days ago
100.0 % uptime
Today
Marketing Operational
90 days ago
100.0 % uptime
Today
Corporate Web Site ? Operational
90 days ago
100.0 % uptime
Today
Customer Support Operational
90 days ago
100.0 % uptime
Today
Inbound Phone Service ? Operational
90 days ago
100.0 % uptime
Today
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.
Scheduled Maintenance
On August 1st, 2024, at approximately 11AM Eastern US time, TrackAbout will be making the following change to the Production environment.

Key Details:
New IP Address: The new IP address for www.trackabout.com (Production) will be 52.252.64.105.

Stronger Encryption Ciphers: We will be moving to a stronger set of TLS/SSL encryption ciphers for the Production environment and retiring known-weak ciphers.

The new list of supported ciphers is:
TLS_AES_128_GCM_SHA256
TLS_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

This change reflects our commitment to maintaining robust security standards.

Impact:
We have monitored customer TLS/SSL connections for the past seven months. We have reached out to customers who might have faced issues transitioning to the new ciphers.

Our logs indicate all potential issues with connections from customer ERP systems have been resolved.

55 Windows Mobile devices synced in the last 30 days are still running an outdated version of TAMobile 6. Our Support Team has been contacting you to upgrade these devices.

The required minimum version of TAMobile 6 is 6.0.345.1. Devices running older versions will be unable to connect or self-upgrade after this change. You are strongly encouraged to find them and update them before August 1st.

A small handful of you have employees or agents using operating systems and web browsers that are no longer supported by their manufacturer. These individuals may find they cannot connect to the TrackAbout Production web site (www.trackabout.com) after the cutover. Their systems should be upgraded. These are likely systems running unsupported versions of Windows 10, 7 or earlier.

Action Required:
- Upgrade old TAMobile 6 devices if you have any
- Upgrade PCs or web browsers that are out of support
- Ensure that your firewall settings are updated to accommodate the new IP address. For most customers, there is nothing to do here, but we are aware a few of you have our IP in your firewall.

Important Notes:
TrackAbout reserves the right to change IP addresses without notice to maintain uptime and fault tolerance.
We advise against hardcoding our public IP addresses in your firewall settings to avoid potential outages during service migrations.

Posted on Jul 22, 2024 - 17:28 EDT
Production Uptime (via Pingdom) ?
Fetching
Past Incidents
Jul 26, 2024

No incidents reported today.

Jul 25, 2024
Resolved - Resolved.
Jul 25, 11:55 EDT
Update - Performance has remained nominal since our intervention. We regenerated the database statistics in the affected database in order to help the query planner choose more optimal plans. We have a regular job that updates statistics, and we'll look into whether any changes might be required there to avoid future incidents.

We are closing this incident. If we determine an actionable root cause we will follow up with a post-mortem.

Jul 25, 11:55 EDT
Monitoring - We identified that one customer was sending in excess of 500 requests per minute, which caused a database performance spike.
We took action and the load is now back to normal.
We are monitoring and will investigate further the root cause.

Jul 25, 10:54 EDT
Identified - We are troubleshooting a performance degradation within the database environment. One database has spiked CPU to 100% and is impacting the performance of the environment.
Jul 25, 10:23 EDT
Jul 24, 2024
Completed - Deployment successful. This maintenance is now complete.
Jul 24, 14:31 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 24, 14:00 EDT
Scheduled - TrackAbout will release new code to the Production environment on Wednesday, July 24th, 2024 starting at 2:00 PM US Eastern Time (18:00 UTC).

There will be no downtime or service interruption.

New Application Web Site Version: 15.0.347.30
No new TAMobile 7 iOS Version
No new TAMobile 7 Android Version

Jul 24, 13:31 EDT
Jul 23, 2024

No incidents reported.

Jul 22, 2024

No incidents reported.

Jul 21, 2024

No incidents reported.

Jul 20, 2024

No incidents reported.

Jul 19, 2024

No incidents reported.

Jul 18, 2024
Resolved - All services are now restored and stable. We are resolving this incident.

As per root cause, Microsoft has published their analysis: "We’ve determined the underlying cause. A backend cluster management workflow deployed a configuration change causing backend access to be blocked between a subset of Azure Storage clusters and compute resources in the Central US region. This resulted in the compute resources automatically restarting when connectivity was lost to virtual disks."

Jul 18, 23:10 EDT
Monitoring - Microsoft appears to be making substantial progress in restoring services. Our Azure SQL environment in Central US has come back online and all geo-replicated databases have caught up to their primaries.

As a result, we can now generate Custom Reports and OpenData should be operational as well.

We're still experiencing a bit of slowness here and there and will be keeping a close eye on things for a while.

Jul 18, 22:28 EDT
Update - Microsoft says they are currently applying mitigations, but we do not yet have an ETA for service restoration.

Clarifying our earlier notifications: Even though it is the Azure Central US region that is impacted, ALL customers of TrackAbout are presently unable to run Custom Reports and use OpenData regardless of that customer's global region. Those two TrackAbout services (Custom Reports and OpenData) have dependencies on Azure services operating in the Central US region.

TrackAbout is currently implementing disaster recovery procedures to migrate services to a different Azure region. We'll see who gets there first: us or Microsoft.

Jul 18, 21:25 EDT
Update - The Azure outage does seem to be confined to the Central US region, and not Global as Microsoft stated.

Microsoft hasn't released an update in over an hour. They have not indicated they understand the root cause.

We are continuing to monitor and hoping for some kind of update from Microsoft.

TrackAbout Custom Reports and OpenData remain unavailable for the time being.

Jul 18, 20:21 EDT
Update - Microsoft Azure has updated its status page to indicate they are having problems outside just the Central US region, calling it a "Global" issue.

Our services are operational (aside from the aforementioned Custom Reports and OpenData) at the moment. We're continuing to monitor the situation closely.

Jul 18, 19:32 EDT
Update - It appears several services in the Azure Central US region are down (storage, VMs, just about everything).

We are tracking the issue on Azure's status page here https://azure.status.microsoft/en-us/status/

We will update when we have more information.

As it pertains to our OpenData service, if you have an open connection to the database, it may continue working. New connections to the database are mostly failing.

Custom Reports are unlikely to work until this is resolved.

Jul 18, 19:08 EDT
Identified - Starting at 6:13 PM Eastern US (22:13 UTC) on 18 Jul 2024, Azure has reported a failure in the Central US region in Azure SQL Database.

The impact for TrackAbout customers is that Custom Reports from the application web site may not load and new OpenData SQL connections may fail.

We are awaiting an update from Microsoft Azure on when service will be restored.

Jul 18, 18:53 EDT
Jul 17, 2024

No incidents reported.

Jul 16, 2024

No incidents reported.

Jul 15, 2024

No incidents reported.

Jul 14, 2024

No incidents reported.

Jul 13, 2024

No incidents reported.

Jul 12, 2024

No incidents reported.