Fluke MET/TEAM Outage History

Started Oct 12, 2026, 04:49 PM UTC· resolved Oct 13, 2026, 07:39 AM UTC

1. investigating Oct 12, 2026, 04:49 PM UTC

   We are currently investigating an issue related to the licensing process where emails sent report as having extra malformed content before the main body, causing the request to be rejected.

2. identified Oct 12, 2026, 06:26 PM UTC

   We have identified the cause of the issue and are working to implement a fix.

3. resolved Oct 13, 2026, 07:39 AM UTC

   This incident has been resolved.

4. postmortem Oct 13, 2026, 07:45 AM UTC

   **Summary** From approximately October 9 through October 12, 2026, some customers who emailed a license request received an “invalid format” error or a garbled response instead of their license. The issue was resolved on October 12 at approximately 5:30 PM PT, and license requests are now processing normally. **What happened** A change to how our email system labels messages from external senders added a notice to incoming license request emails. That notice repeated part of the original message, which our license processing application did not expect. The application could not read the request correctly and returned an error or an incorrect response. **Impact** Customers submitting license requests by email may have received an “invalid format” error or a response containing repeated or jumbled text. Some customers retried more than once without success. Gold requests showed the same repeated text. **Resolution** We updated the license processing application to correctly read requests even when the notice is present, and we corrected the format of its replies so they no longer include the repeated text. **What you need to do** If you received an error or a garbled response during this period, please resubmit your request. If you still have trouble, contact Support and we will help you directly. **Timeline \(Pacific Time\)** * **Oct 9:** First customer report of license request errors. * **Oct 12, morning:** Investigation began, and the cause was identified by early afternoon. * **Oct 12, afternoon:** Fix applied and replies corrected. * **Oct 12, ~5:30 PM:** Issue confirmed resolved. **Preventing a recurrence** We are making our request processing more tolerant of changes to how email is formatted, adding tests for this case, and working to ensure changes to our email system are communicated to the teams who rely on it. We are also adding monitoring so we detect problems like this sooner. We apologize for the inconvenience this caused.

Read the full incident report →

Started Sep 11, 2026, 08:02 AM UTC· resolved Sep 11, 2026, 02:31 PM UTC

1. investigating Sep 11, 2026, 08:02 AM UTC

   OptiCal is currently unavailable, we are investigating and working to resolve the outage as soon as possible.

2. resolved Sep 11, 2026, 02:31 PM UTC

   OptiCal is back to full availability.

Read the full incident report →

Started Aug 05, 2025, 11:07 PM UTC· resolved Aug 28, 2025, 09:23 PM UTC

1. investigating Aug 05, 2025, 11:07 PM UTC

   We are currently investigating an internal system issue that is preventing the licensing system from responding to requests.

2. monitoring Aug 06, 2025, 03:16 PM UTC

   The licensing system is now working again, but we are continuing to investigate root cause for this outage.

3. identified Aug 06, 2025, 03:30 PM UTC

   The permissions issue that is driving the outage has not been fully resolved. We are awaiting action from IT personnel who are addressing this issue which is affecting multiple teams.

4. monitoring Aug 06, 2025, 07:10 PM UTC

   The system is fully operational again, but we are continuing to pursue the root cause to prevent future issues.

5. resolved Aug 28, 2025, 09:23 PM UTC

   This incident has been resolved.

6. postmortem Aug 28, 2025, 09:24 PM UTC

   ### Summary Our licensing system became unavailable after a change to corporate email/identity groups associated with our shared mailboxes. The change was part of broader corporate separation work between Fortive and Ralliant/Tektronix. It unintentionally removed access controls needed by the licensing service. Once identified, our IT partners restored the affected group associations and resolved directory errors, returning the system to normal operation. > Context: Tektronix is transitioning to **Ralliant** as part of Fortive’s separation; some shared infrastructure and groups were being updated during this work. ### What happened \(root cause\) An email/identity group that was removed as part of the separation program inadvertently impacted other groups still in use to secure Fluke shared mailboxes that our licensing system depends on. That change removed required access, which interrupted mailbox‑based licensing workflows. ### Timeline * **Aug 6** – We escalated the access failures and opened a ticket with the IT Service Desk. * **Aug 13** – IT confirmed the cause \(removal of a mail‑enabled security group related to separation work\) and restored access by re‑associating the correct groups and clearing directory/GUID issues. * **Aug 13\+** – We requested the preventive‑actions plan from IT; final confirmation is pending. ### Resolution IT re‑associated the correct email security groups with the affected shared mailboxes, corrected proxy addresses, and resolved several GUID‑related errors. Services recovered immediately after these changes. ### What we’re doing to prevent this We’ve asked for \(and will publish once confirmed\) the formal prevention plan. Areas we’re pushing on include: * Stronger change controls and impact assessment for email/identity group changes that could affect shared mailboxes. * Guardrails to prevent removal of groups with active production dependencies. * Monitoring/alerts for mailbox access failures tied to licensing workflows. We’ll update this post with specific commitments and dates once we receive IT’s final plan. ### Customer action No action is required. If you still see licensing issues, please contact Support with your license ID and timestamp.

Read the full incident report →

Started Nov 11, 2024, 11:47 PM UTC· resolved Dec 02, 2024, 06:32 PM UTC

1. monitoring Nov 11, 2024, 11:47 PM UTC

   Earlier today, the Fluke Calibration website at flukecal.com was redirected to the newly combined site at fluke.com. This impacted access to the latest release of MET/CONNECT and MET/CAL. While we work on migrating the pages for the latest release, they can be acquired by contacting technical support [email protected] Additionally, MET/SUPPORT Gold registration is currently unavailable. An updated knowledge base article will be published with the new process for this shortly, and existing members will have their data migrated.

2. identified Nov 11, 2024, 11:58 PM UTC

   Updating to correct status.

3. identified Nov 14, 2024, 09:22 PM UTC

   Some download links on the Fluke website are still broken at this time. MET/CAL version 11.1.0 for MET/TEAM version 3.3.1 can be downloaded here: https://fortive.box.com/s/kx0htr1xv1be2dv0cwjx0a9b94nnntdv MET/CONNECT version 2.2.0 with MET/CAL version 11.1.0 can be downloaded here: https://fortive.box.com/s/79imzeylzcs6bbb5p0ua8xuthzzhm3ce The latest Accuracy Files (required for MET/TEAM users updating to MET/CAL 11.1.0, but included in the MET/CONNECT server installer) can be downloaded here: https://fortive.box.com/s/si525ecuibif8ln9wlrx0e4dfkv61yn0 The knowledge base article for MET/SUPPORT Gold registration (https://my.fluke.com/en-us/article/KA-03972) has been updated to reflect the new steps for this process. Existing Gold registrations should be automatically migrated to the new system by the end of this week. The PIN required for new user registrations for existing Gold contracts can be obtained from Technical Support at [email protected], but we are working on sending out this information proactively as well.

4. monitoring Nov 15, 2024, 03:27 PM UTC

   All known issues with broken links for Fluke Calibration software downloads have been resolved. We will continue to monitor for additional reports. The knowledge base article for MET/SUPPORT Gold registration (https://my.fluke.com/en-us/article/KA-03972) has been updated to reflect the new steps for this process. Existing Gold registrations should be automatically migrated to the new system by the end of this week. The PIN required for new user registrations for existing Gold contracts can be obtained from Technical Support at [email protected], but we are working on sending out this information proactively as well.

5. resolved Dec 02, 2024, 06:32 PM UTC

   This incident has been resolved.

Read the full incident report →