Flow By Tie Kinetix の障害履歴

The Flow Portal is partially accessible at this moment. The team is working to bring it fully accessible as soon as possible. All background integration services are NOT affected and are fully operational.

Problem has been identified, and the service is recovering. We are monitoring it in case of further issues.

Service is recovered and is fully accessible now. We keep monitoring it.

FLOW Portal is fully operational and accessible in all regions.

Our network provider KPN is reporting an outage in the IPMail and X400 network. We will provide more information once we have received more details from KPN

Out network provider KPN has reported that the IPMail / X400 outage is resolved. We are verifying our systems to make sure that the outage is fully resolved. We will provide more info in the coming 30 minutes.

We have verified that messages are transmitted again on the IPMail and X400 network and we will close this incident. We apologize for the inconvenience caused.

At this moment our Cloud provider is reporting network issues in their datacenters. Some FLOW modules could have a slow response or give a timeout. We will provide more information once we will receive an update from our cloud provider.

Our cloud provider has identified the network configuration issue and is working on a solution. The impact on our services are limited but we keep closely monitoring all connections. We will provide an update once we have more information.

The cause of the network outage at the cloud provider has been identified and a fix has been deployed. The problems should be resolved now but we keep closely monitoring our systems. We apologize for the inconvenience caused.

This incident has been resolved, we apologize for the inconvenience caused.

We are currently having an issue with our DNS provider which could result that the portal cannot be opened for some users. We are investigating the issue and will update once we have more information

Some users will have problems accessing the FLOW portal. This problem is caused by an issue at our DNS provider. They are working on a resolution. We will keep you updated once we have more information. We apologize for any inconvenience this may cause.

Some users might experience problems accessing the FLOW portal. - update: This problem is caused by an issue at our DNS provider and we want to let you know that they are still working on this persistent issue. If users cannot access the portal, then switching to a different wifi or mobile connection might solve the issue. For our integration and invoicing solutions, be aware that our servers are still processing the messages in the background. If you have an integrated connection to our services (for example AS2/sFTP/etc.) then there are workarounds available in some situations. Please contact our support team for more information. We will keep you updated once we have more information. We apologize for any inconvenience this issue may cause.

The DNS issues have been resolved and all services should be accessible again. We are closely monitoring and checking all systems to make sure that all services work as intended. We apologize for any inconvenience this issue may have caused.

We have found no further issues and our monitoring services show all systems are accessible. We will close this incident and we apologize for any inconvenience this may have caused.

We are experiencing problems with our E-invoicing solution, users are not able to open the E-invoicing application. We are investigating the issue and will provide more information soon.

The issue has been resolved and the E-invoicing application is available again. We keep monitoring the application to make sure everything is working as intended. We apologize for any inconvenience caused.

This incident has been resolved.

We noticed a performance degradation issue in the supplier portal (leveranciers portaal) services. We are currently investigating the issue and will provide an update once we have more information.

The issue with the suplier portal has been identified and a fix has been rolled out. New documents can be processed now. Documents that were submitted during the incident are processed at this moment. We will keep monitoring the system closely and apologise for any inconvenience this may have caused.

The system has finished processing the documents that were queued because of the incident and is up to date again. We again aplogise for any inconvience that this incident has caused and will take measures to prevent future incidents.

We are currently experiencing an issue with the login server. We are investigating the issue and will provide more information when available.

We have identified the problem and deployed a fix on the login servers. Users are able to login to the FLOW portal again. We will do further investigation on the cause of this incident and will keep monitoring the service closely.

We will close this incident now

There are currently login problems for a subset of users. We are investigating the issue and will provide more information within 15 minutes.

A subset of users is currently having login problems. The issue is caused by a database connection problem and we are deploying a fix that should resolve these login issues. We will provide more information once the fix is deployed.

A fix has been implemented to resolve the login problems. We will keep monitoring the system closely to make sure all issues are resolved. We do apologize for any inconvenience this may have caused.

We have found no further issues and will close this incident.

We have identified an issue that in some rare cases the opening of the FLOW portal can fail if your system is using Google's public DNS servers and if you use the project url (https://company.flow.tiekinetix.net). You can use the general FLOW portal url without any issues https://flow.tiekinetix.net. We are currently investigating this issue and will update this ticket when we have more information.

Currently, login to the portal might not work when you use Google DNS services. We have deployed a change that should resolve the DNS issue that a small number of users could have when opening the FLOW portal while using Google's public DNS servers. It might take some time before this change is processed worldwide by public DNS servers. If you experience this problem, you can temporarily use the general FLOW Portal URL to login (https://flow.tiekinetix.net) to your portal. We apologize for the inconvenience this may cause.

Google's DNS services worldwide have updated the correct DNS records and all FLOW portal URLs are available again. The cause has been identified as a communication error between our DNS provider and the Google Global DNS servers which caused corrupted DNS records on Google's side. In case you still have connection problems then we advise you to clear your machine's DNS cache. Detailed instructions can be found on this site: https://www.whatsmydns.net/flush-dns.html We sincerely apologize for any inconvenience this may have caused.

There are currently issues with the login to the FLOW portal. We are investigating the issue and will give more information once we have identified the cause.

The issue was caused by a failure of the login servers. This problem is resolved and it is possible again to login to the FLOW portal. We apologize for the inconvenience this may have caused.

We currently have an issue with our eInvoicing module, users are not able to open the module. We are investigating the issue and will let you know when we have more information. We apologize for any inconvenience this may cause

The problem has been identified and a fix has been deployed. The eInvoincing solution is available again and we will monitor the system to verify that it is working correctly. We apologize for the inconvenience the problem has caused.

This incident has been resolved.

We have experienced an issue with the login to the eInvoicing portal. The issue has been resolved with the deployment of a patch and we keep monitoring the environment closely to make sure the issue has been fully resolved.

No further login problems have been reported, we will close this ticket. We apologize for the inconvenience this may have caused.

Network issues at the datacenters that are in use by FLOW caused some problems accessing the FLOW portal. At the moment the FLOW portal is available again but we keep monitoring and checking the situation.

We have received a confirmation from our cloud provider that the network issues in the datacenters have been resolved. We apologize for any inconvenience this disruption may have caused.

The frontend servers are currently not reachable and users will receive an error to retry in 30 seconds. We are investigating the issue and will report once we have more information.

We identified an outage in our storage network and have restarted services. The FLOW portal is now available again. We will continue to investigate what caused the outage and will deploy changes if needed.

We are investigating an issue with the FLOW portal. Users are able to log in but menu's and products are not loading. We will inform you when we have more information.

We have identified a problem with the database and deployed a fix. Users should now be able to log in normally again. Our apologies for the disturbance of the FLOW portal service.

We currenly have a problem with the conenctions to the database. We are working hard to resolve the issue. We will give you an update once we have solved the problem.

The network connectivity to the database servers have been resolved and the FLOW portal is now functioning again. We are closely monitoring the platform now and will make changes to prevent similar problems.

The database connections are stable now. We will close this incident. We apologise for any inconveniences this may have caused.

There is currently an issue with the backends of the FLOW portal. We are investigating the issue and will come with an update once we have more information.

The technical problem with the backends is identified and resolved. We are now closely monitoring the platform to make sure the backends keep working as intended.

The backends are stable now and we will close this incident.