TIBCO incident
TIBCO Scribe online - Agent issue | AWS and Azure Region(s)
TIBCO is currently in scheduled maintenance affecting Scribe® Agents, which began 70d ago. The vendor's full update timeline is below.
Affected components
Update timeline
- investigating Aug 11, 2026, 01:51 PM UTC
Please be advised that TIBCO Scribe online is experiencing an issue with agent service. The TIBCO team is investigating this issue as a priority. While this issue is occurring, users may see the error “Unable to send the command to the Agent.” Scheduled jobs will continue to run normally. However, on-demand solutions may not run and may display the same error when testing the connection. Please contact us via the TIBCO Support Portal (https://support.tibco.com) with any questions or concerns.
- identified Aug 11, 2026, 05:18 PM UTC
We are still actively working with the vendor (Microsoft) to investigate and resolve the issue. Please contact us via the TIBCO Support Portal (https://support.tibco.com) with any questions or concerns.
- investigating Aug 12, 2026, 10:29 AM UTC
We are continuing to work closely with Microsoft to investigate and resolve the issue. We will provide further updates as we make progress. Please contact us via the TIBCO Support Portal (https://support.tibco.com) with any questions or concerns.
- identified Aug 13, 2026, 03:15 PM UTC
We have identified the root cause of the issue and are currently working on implementing a resolution. We will provide further updates as we make progress. Please contact us via the TIBCO Support Portal (https://support.tibco.com) with any questions or concerns.
- identified Aug 14, 2026, 02:33 AM UTC
We have completed development of the solution and are now moving into testing to confirm that it resolves the issue before deployment. We will provide another update once testing is complete and we have a timeline for the rollout.
- identified Aug 14, 2026, 03:09 PM UTC
Emergency Maintenance Notice – TIBCO Scribe Online We will be performing emergency maintenance on TIBCO Scribe Online over the upcoming weekend to address an ongoing issue affecting the platform. This work is necessary to ensure the continued stability and reliability of the service. The specific schedule for each environment will be posted here as soon as the release is ready. We will provide updates as more information becomes available
- identified Aug 16, 2026, 01:09 PM UTC
Emergency Maintenance Release Notice – TIBCO Scribe Online The emergency release deployment is currently underway in the Sandbox environment. The specific deployment schedule for each environment will be posted here soon.
- identified Aug 17, 2026, 03:26 PM UTC
Emergency Maintenance Release Update – TIBCO Scribe Online The emergency maintenance release has been successfully deployed to the AWS US-East and AWS AU environments. We will continue to monitor these environments following the deployment and provide further updates as the maintenance progresses. The deployment schedule for the remaining environments will be posted here shortly.
- identified Aug 18, 2026, 05:59 PM UTC
The planned emergency maintenance for TIBCO Scribe® Online in the AWS US (N. Virginia) and EU (Frankfurt) regions is taking longer than anticipated. We are extending the maintenance window by an additional 3 hours. The maintenance is now expected to be completed within 10 hours from the original start time of August 18th, 2026 at 05:30 AM (US Eastern time). Any deployed apps and services will not be affected. We apologize for the extended maintenance window and appreciate your patience and understanding. Please contact us via the TIBCO Support Portal (https://support.tibco.com) with any questions or concerns.
- identified Aug 18, 2026, 07:20 PM UTC
Update- The scheduled maintenance has been completed successfully to AWS US and EU. We will continue to monitor these environments following the deployment and provide further updates as the maintenance progresses.
- monitoring Aug 19, 2026, 03:47 PM UTC
Update: The scheduled maintenance for the US West Azure region has been completed successfully. We are continuing to monitor the environment post-maintenance and will provide further updates as necessary.