TOTSCo

TOTSCo Hub Status Updates

This page will display up to the minute service information on our TOTSCo Hub, with an explanation of the issue, impact and resolution.

Hub change and maintenance updates

For all the latest on any changes or maintenance to the TOTSCo hub, click below.

Test environment affected
Defect No Date Priority status Simulator environment Integration (pre-production) Trials (production) Issue Impact
34077 1/07/2024 P2 No Yes No Issue fixed - Following further investigation, we have reclassified the issue as Priority 2, as the majority of messages are flowing through. Where we have identified issues with individual messages, we are reaching out to the organisations impacted to reach a resolution. Users in integration Testing
Resolution We are closing the P2 issue as the hub has been restored. We have now opened a problem ticket to continue our investigations into the incident.
33953 26/06/2024 P2 No Yes No Target CP will not receive messages from source CP Users in integration Testing
Resolution RESOLVED - The issue was identified and fixed.
33125 10/04/2024 P1 Yes Yes Yes RESOLVED - Issue with the DNS impacting all environments. Users testing.
Resolution RESOLVED - The issue was found, investigated and fixed in quick succession.
Various including 32705 19/03/2024 P2 No Yes RESOLVED - Issue of occasional messages not being delivered. Some users in integration testing. Users in this environment can continue to test.
Resolution After investigating, it appears that the issue lies on the CP side. We are currently collaborating with all CPs to resolve these issues effectively. Update 28/03/2024
32537 29/02/2024 P2 No Yes RESOLVED - Intermittent fault has been identified where duplicate messages are being sent to users. This is currently under investigation. Some users in integration testing. Users in this environment can continue to test.
Resolution RESOLVED - Fix was successfully tested in system integration testing (SIT) and deployed successfully. Update 20/03/24
32537 27/02/2024 P2 No Yes RESOLVED - Message response issue where multiple messages are sent by one user to another (one RCPID to another RCPID). We are aware of an issue when sending multiple messages between the same two users in the Integration Test Environment. In this situation, the responses to the receiving user were for a sub-set of the messages from the Hub, and responses were pending for the remaining messages. Users sending multiple messages between each other in the Integration Test Environment.
Resolution THIS ISSUE HAS BEEN RESOLVED. We have fine-tuned one of the configuration parameters in the Hub to fix the issue.
13/02/2024 No Yes RESOLVED: We currently have an issue in our TOTSCo Hub integration testing environment. The hub is not facilitating message exchanges. All users currently testing in the integration environment.
Resolution Now resolved. Issue was due to an access key failure. Restoration was achieved by creating a new key. The issue was moved to the problem stage (as per ITIL processes) for further root cause analysis.
09/02/2024 RESOLVED: The account management portal went down. All CPs using the account management portal.
Resolution Now resolved. If you are unable to access your account please let us know by contacting [email protected].
16/01/2024 No Yes RESOLVED: Integration testing environment unavailable. All CPs using the integration testing environment.
Resolution A full investigation was carried out the issue was related to our Domain Name System (DNS) settings. Upon investigation we learnt that the issue predominantly affected our IT partner, Tech Mahindra. The integration testing environment is now available. You can now use the Integration Test Environment as normal.
11/12/2023 No Yes CPs receiving 503 response intermittently. CPs getting failure messages on intermittent basis resulting in not able to exchange message.
Resolution 18/12/2023: Service Desk informed affected CPs that the issue has now been resolved. 15/12/2023: Issue resolved on Friday at 8:30pm GMT. The TOTSCo technical team investigated the intermittent (Error 503) on hub. There was a configuration issue with one of the load balancer nodes which was identified and corrected to resolve this issue. 11/12/2023: under investigation
20/11/2023 Yes No Test simulator down. 3 hour outage of the Test Simulator.
Resolution 1pm 20/11/2023. Additional memory allocated to the Test simulator. Issue resolved.
Skip to content