TIBCO Cloud™ Services status
All Systems Operational

About This Site

Welcome to the TIBCO Cloud™ Services status page. This page shows the status of TIBCO's cloud services, including any ongoing incidents or scheduled maintenance, as well as a record of past incidents and maintenance.

TIBCO Cloud™ Operational
User Management Operational
Login Operational
Analytics Operational
Spotfire® Operational
Mashery® Operational
Runtime ? Operational
Design Time ? Operational
Developer Portals Operational
API Modeling Operational
API Mock Operational
NodeJS Operational
Reporting/Analytics ? Operational
Event Processing Operational
Events Operational
Messaging Operational
eFTL™ Operational
Data Management Operational
Metadata Operational
Connect Operational
Scribe® Applications Operational
Scribe® Agents Operational
Scribe® API Operational
Scribe® Connectors Operational
Scribe® Event Solutions Operational
Develop Operational
Flogo® Operational
Integrate Operational
BusinessWorks™ Operational
AuditSafe Operational
Live Apps Operational
Case Manager Operational
Administrator Operational
Designer Operational
Nimbus® Maps Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
If you are using the Call Log Export feature then please read the full message below, share within your organization and implement the required changes by February 2021 or you risk losing log delivery through this feature.

As we announced previously (check notification https://status.cloud.tibco.com/incidents/9mkfq0rvl9xf), native S3 bucket encryption and assumed-role access to customer buckets for the Call Log Export feature have been released. These upgrades provide improved security for this feature. With this announcement in October 2020, we also announced that Call Log Export profiles using the IAM based bucket access policy option will be disabled.

Customers not upgrading to the new functionality prior to target date will have call log delivery disrupted until the new functionality is configured by them.

In an effort to make this process as straightforward as possible we have outlined the following process for replacing existing ECLE profiles with those using the S3 encryption and assumed-role access:

1 - Create a new S3 bucket using the CloudFormation template. It is available for download here: https://developer.mashery.com/files/ECLE_customer_resources.yaml. Contextual information is available within the application on the Call Log Export create and edit screens.

2 - Log in to your API Control Center, select the Call Log Exports option from the Analyze menu, and then create a new profile. To complete this, you will need values obtained after running the new CloudFormation template.

3 - Once you have completed the new ECLE profile, it will take roughly 3 hours for the new configuration to become active. After this period has passed, check the new S3 bucket for encrypted logs by selecting an object in the bucket, then navigating to the Properties tab and looking for "AWS-KMS" on the Encryption card.

4 - Once confirmed that you are getting the logs, start consuming logs from the new encrypted S3 bucket.

5 - Delete the original, unencrypted bucket policy.

Note: Only files uploaded after the configuration is live will be encrypted, existing files will remain unencrypted.

Please contact us via the TIBCO Support Portal (https://support.tibco.com) if you have any questions regarding the configuration and upgrade.
Posted on Jan 19, 11:45 EST
Past Incidents
Jan 20, 2021

No incidents reported today.

Jan 19, 2021
Resolved - We have implemented the fix that should resolve the problem for most customers. If you continue to experience the fatal error beginning with "Could not find the AdapterType Id '00000000-0000-0000-0000-000000000000' of Connection Id", open a case using the TIBCO support portal (https://support.tibco.com) and our Support team will assist you with correcting the error.
Jan 19, 10:59 EST
Update - We are working on a fix that should resolve the issue for most affected customers. We will provide another update when we begin implementing the fix.
Jan 19, 08:31 EST
Identified - We have identified an issue where for some customers apps/solutions fail with a fatal error beginning with "Could not find the AdapterType Id '00000000-0000-0000-0000-000000000000' of Connection Id". We are working on a solution for the error and will update this incident when we have more information.
Jan 18, 22:07 EST
Jan 18, 2021
Jan 17, 2021

No incidents reported.

Jan 16, 2021

No incidents reported.

Jan 15, 2021

No incidents reported.

Jan 14, 2021

No incidents reported.

Jan 13, 2021
Completed - The scheduled maintenance has been completed.
Jan 13, 02:00 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 13, 00:00 EST
Scheduled - TIBCO Cloud Spotfire® - US will undergo scheduled Maintenance on 12 January 2021 at 9:00 PM Pacific Time.

The maintenance is expected to take up to two hours and downtime is expected.

We apologize for any inconvenience.
Jan 6, 08:25 EST
Jan 12, 2021
Completed - The scheduled maintenance has been completed.
Jan 12, 18:00 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 12, 16:00 EST
Scheduled - TIBCO Cloud Spotfire® - EU will undergo scheduled Maintenance on 12 January, 2021 at 21:00 UTC.

The maintenance is expected to take up to two hours and downtime is expected.

We apologize for any inconvenience.
Jan 6, 08:23 EST
Completed - The scheduled maintenance has been completed.
Jan 12, 01:30 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 12, 00:00 EST
Scheduled - TIBCO Mashery will perform next week's scheduled maintenance on Monday starting at 9:00 PM PST / Tuesday 00:00 AM EST.

This release is focused on our datamart and will have some temporary impact on the reporting system, however, your API traffic will continue to be processed normally with no impact.

During the 90 minute release window, the Call Log Stream (ECLS) data feed is expected to stop for approximately 15 minutes. Unfortunately, those feeds can't be replayed and will result in a gap in data delivered via ECLS. Call Log Export (ECLE) will continue to function but delivery will be slightly delayed for calls during the release window. Dashboard reports and Mashery Reporting APIs will continue to function without issue during the release time.

If you have any questions or concerns about this release then please contact us via the TIBCO Support Portal (https://support.tibco.com).
Jan 8, 13:30 EST
Jan 11, 2021

No incidents reported.

Jan 10, 2021

No incidents reported.

Jan 9, 2021

No incidents reported.

Jan 8, 2021
Completed - The scheduled maintenance has been completed.
Jan 8, 15:00 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 8, 12:00 EST
Scheduled - Emergency Maintenance Notification
Agents in the TIBCO Cloud™ Integration AWS Australia and TIBCO Cloud™ Integration Azure environments will be updated on Friday, 8 January 2021 at 12:00 noon US Eastern Time. All Scribe® Agents running in these environments will be upgraded when they are idle (not running a solution).
Jan 7, 16:26 EST
Jan 7, 2021
Completed - The scheduled maintenance has been completed.
Jan 7, 23:19 EST
Scheduled - Dear TIBCO Cloud Mashery Customers,

2020 is coming to a close soon and like previous years, TIBCO Cloud Mashery will observe a ‘Year End Freeze’. This is to accommodate requests from many of our customers, retail and otherwise, to reduce changes to mission critical systems during this important time of the year. During the freeze, TIBCO will not roll out new code in Mashery cloud. Regular infrastructure maintenance and housekeeping tasks will be carried out to ensure optimum performance and higher capacity.

Start date : 18 November 2020
End date. : 4 January 2021
Note: If absolutely required, we reserve a release window in Mid-December (8th December 2020) to rollout critical fixes that might be needed for system stability or security that can’t wait till January. If we decide to take this release, an announcement will be issued through the status page with further details.

During the freeze, please continue to report Cases through the support portal. Kindly select appropriate priority based on the issue's impact to your business and please refrain from logging 'Urgent' priority cases for non-production or non-traffic impacting issues.

From TIBCO Cloud Mashery, we would like to wish you a safe and happy holiday season!

Best Regards,
TIBCO Cloud Mashery Team
Support Portal (Cases and knowledge): https://support.tibco.com
Status Page (Service status and communication): https://status.cloud.tibco.com
Product/Service Info (Documentation and blog): https://support.mashery.com
Oct 23, 19:40 EDT
Completed - The scheduled maintenance has been completed.
Jan 7, 16:00 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 7, 13:00 EST
Scheduled - Emergency Maintenance Notification
Agents in the US and EU regions of the TIBCO Cloud™ Integration AWS environment will be updated on Thursday, 7 January 2021 at 1:00 PM US Eastern Time. All Scribe® Agents running in these AWS environments will be upgraded when they are idle (not running a solution).
Jan 7, 10:37 EST
Jan 6, 2021
Completed - The connector updates have been postponed and will be rescheduled.
Jan 6, 19:51 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 6, 10:00 EST
Scheduled - TIBCO Cloud™ Integration will update the Scribe® Microsoft Dynamics 365 / CRM and Microsoft Common Data Service (CDS) connectors in the AWS and Azure environments (all regions) beginning on Wednesday, 6 January, 2020 at 10 AM US Eastern Time. The updates will be deployed to all agents using the connectors over a period of about 30 hours. Agents with any of the listed connectors installed will be restarted when they are idle and are not running solutions. No performance impact is expected.
Dec 28, 12:46 EST
Resolved - This incident has been resolved.
Jan 6, 14:02 EST
Investigating - Monitoring tools have detected an issue with the the Agent API in the AWS EU Region. Users will begin to see agent heartbeat failure warnings. We are investigating the issue.

While this issue is occurring, scheduled solutions/apps will continue to run, event based solutions/apps will continue to run, on-demand solutions/apps will run but will not display the appropriate status updates, and parts of the web application that rely on the agent will not work as expected.
Jan 6, 13:52 EST