To enhance the performance and ensure the reliability of our systems, we have scheduled a maintenance window for Support.Aleyant.com. Please be advised that during this period, Support.Aleyant.com will be temporarily unavailable as we perform critical updates and maintenance tasks. We appreciate your understanding and apologize for any inconvenience this may cause. To learn more about the EULA Maintenance Window, please visit our Aleyant EULA.
]]>We apologize for any inconvenience this may cause and appreciate your understanding as we keep working to maintain and improve our infrastructure performance and security.
Should you have any questions or concerns regarding this scheduled maintenance, please do not hesitate to contact us.
]]>Sunday (3/26/2023) All Day -- We will be taking a node offline for testing and development at our US (Chicago) data center. This should not cause any downtime on any services, but some latency with some services may be noticeable.
]]>We are notifying you about a new alert as it relates to your tFLOW New Jersey Instance.
Event Summary: New Jersey Scheduled Maintenance - 2023-03-15
Event Type: Network Upgrade
We are performing system changes in the New Jersey location during the following scheduled maintenance window.
Start Time: 2023-03-15 04:00:00 UTC End Time: 2023-03-15 08:00:00 UTC
We schedule higher impact maintenance events during off-peak times to reduce impact to customer infrastructure. Our engineers make every effort to minimize system impact, however, network reachability to New Jersey instances may be affected for some, or all, of the scheduled maintenance window as we perform this work. While it’s important to be aware of start and end times of the maintenance window, due to our redundant network architecture, our engineers expect that you may see little to no impact at all while the work is performed.
]]>Saturday to Sunday (03/12) - from 11:30 PM thru 02:30 AM CST
We have a maintenance is scheduled on 12th of March 2023 from 11:30 pm CST (1:30 pm SG time) till 2:30 am CST (4:30 pm SG time), this maintenance is a part of our server improvement process. The server needs to be restarted after the maintenance and hence there will be a downtime of 15 mins to 30 mins during the maintenance period.
Please accept our apologies for the inconvenience it may cause you.
]]>Event Summary: Scheduled Maintenance - 2023-02-03
Event Type: Network Upgrade
We are performing system changes during the following scheduled maintenance window
Start Time: 2023-02-03 05:00:00 UTC End Time: 2023-02-03 09:00:00 UTC
We schedule higher impact maintenance events during off-peak times to reduce impact to customer infrastructure. Our engineers make every effort to minimize system impact, however, network reachability to New Jersey instances may be affected for some, or all, of the scheduled maintenance window as we perform this work. While it’s important to be aware of start and end times of the maintenance window, due to our redundant network architecture, our engineers expect that you may see little to no impact at all while the work is performed.
]]>Engineers will replace a public network top of rack switch in cabinet cr130.s101.12.24. Servers in this cabinet will observe approximately 20 minutes of public network connectivity loss.
That means that customers may lose data packets while accessing Pressero, eDocBuilder and PJM in Chicago environment during approximately 20 minutes.
Please see more details on the status page of our provider: https://ot.inap.com/
]]>Thank you for your patience.
]]>We are glad to inform that the migration is completed successfully. The final data synchronization is happening now, and if everything works as expected, it will be completed by Monday. All the areas of Pressero and e-Doc Builder are working well, however, we found a little issue with the system. The issue is Pressero is not able to update existing files. Which means if you would like to replace the image of existing Product, Category or want to replace the logo of existing site, then system will not allow you to do that. Our team is working on this and will try to get this resolved as soon as possible.
]]>Dear Aleyant Subscribers, on Saturday, March 20th at 4:00 AM CST Pressero and eDocBuilder services will be temporarily offline while we start to wrap up a migration to newer servers. The newer servers will bring further stability to Aleyant services. The transition phase will take over the course of about 3 calendar days. Pressero and eDocBuilder will not be offline during the entire period, just an hour portion - however there will be some limitations until the transition completes.
*** UPDATE: This will only affect subscribers on our CHI server. This will not affect subscribers on AMS or SG servers. ***
For details, please see our posting here: https://support.aleyant.com/news/510/planned-server-maintenance.aspx
]]>Please accept our apology for the inconvenience it has caused you.
]]>Please accept our apology for the inconvenience it is causing you.
]]>Please accept our apology for the inconvenience it has caused you.
]]>Please accept our apology for the inconvenience it is causing you.
]]>Please accept our apology for the inconvenience it has caused you.
]]>Please accept our apology for the inconvenience it has caused you.
]]>Update: The issue related to Pressero and PJM is resolved and the system is up and running. e-Doc Builder is still showing some intermittent issue our team is still working on it.
]]>We deeply regret any inconvenience that may have caused you because of this issue.
]]>EDIT 1: We're seeing that Pressero API is also being affected. We're continuing our investigation. Be aware this may impact orders syncing, AWI, email notifications, and eDocBuilder production files on Pressero.
EDIT 2: Currently we are experiencing outage and Pressero Admin is inaccessible. We are investigating this.
All the issues are resolved and the system is up and running.
]]>UPDATE 11/3/2020 11:05 AM CST:
We got reports that the Pressero API on AMS was also experiencing the same issues. The same changes were made as well. Things should be stabilizing.
Any Inconvenience caused to you is deeply regretted.
]]>We apologise for any inconvenience that this may have caused you, and we appreciate your understanding as we continue to improve our customer experience
]]>Please accept our apologies for the inconvenience it is causing you.
]]>Update: The issue is resolved now
]]>Update: The issue is resolved now
]]>https://support.aleyant.com/news/473/update-regarding-temporary-base-domains.aspx
Thank you for the effort of those that have already made changes. This will help avoid issues in the future. Those that have not made changes, it is no longer necessary that you do, however we still recommend making the changes to avoid future issues.
]]>1.) accountname.chi.v6.pressero.com (Pressero Chicago users)
2.) accountname.sg.v6.pressero.com (Pressero Singapore users)
3.) accountname.ams.v6.pressero.com (Pressero Amsterdam users)
If you have not yet moved your sites from the temporary domain to your custom domain name address this IMPORTANT message applies to you.
We received notice today that the company that provides our SSL certificates identified a bug in their process (which has been fixed) that will require that certificates be re-issued to avoid problems. The temporary domain addresses should not see a problem unless you have not followed the suggested formatting of your temporary domains by using dashes instead of periods as noted below. Please review the information to ensure that your domains have been formatted correctly, and if necessary, update them immediately. The changes must be done by 5 PM CT to avoid problems.
As you create sites in your Pressero account, create them as variations on your Temporary Base Domain using dashes. Meaning that you might make two new sites and use addresses like firstsite-myaccount.chi.v6.pressero.com and secondsite-myaccount.chi.v6.pressero.com for a user on the US/Chicago server. Using dashes instead of periods in the address will ensure that you can set those sites to be secure for ordering on the pressero.com domain.
]]>Please be aware our team is working hard on getting these resolved asap. We apologize for the inconvenience this is currently causing.
]]>Notices are being sent to these accounts to correct their information, and we should begin to see an improvement momentarily. A final update will be provided once all systems have resumed normal conditions.
]]>Please be aware our team is working hard on getting these resolved asap. We apologize for the inconvenience this is currently causing.
]]>All pending emails, eDocBuilder file generation, recurring budgets and reports are back to normal and processed successfully. The delivery of emails and all other actions mentioned in our previous update are stable.
Thanks for your patience.
]]>UPDATE: Our team is still working on resolving these mentioned issues. Pressero is currently working through a backlog of email notifications, which is the main cause of the bottle neck. It should resume normal working conditions in a few hours. Until then the following processes have been manually paused in order to allow the system to get back to normal:
1 - Scheduled Report Generation 2 - Recurrent Budget
We will update this page once those processes have been restarted.
A very small subset of sites that make use of Recurring budgets with updates during this window will need to be manually updated if site users are prevented from checking out, and manually updated after the normal automatic process is restored in order to prevent a "surplus" in the budget.
Thank you for your patience. Our support team will continue to provide updates as they occur.
]]>This incident only affected Pressero on SG servers.
]]>We will be doing a thorough analysis of this problem over the next few days. We hope to release a detailed explanation for the problem, as well as specific steps we will take to prevent further similar problems, by Monday, October 15.
If you experience any problems outside the admin site settings page, please open a ticket at http://support.aleyant.com.
]]>As of now, our system is working reasonably but we still have our development team working on assessing the slowness on the site settings area of admin.
]]>In addition to that, we have also been reviewing the settings for all components of our application. We will keep you posted on how the changes goes.
]]>We will post an update once those changes are in place.
]]>For the last hours, Aleyant's infrastructure team has been in touch with the datacenter network team trying to identify any other threat that may be causing such service interruptions.
]]>A recent update to the integration with one of our partners, unfortunately collided with some bad QOS issues on the partner's network. As a result a portion of our network got flooded with failed connections, which interfered with the necessary connections between our load balancer and our edoc worker nodes, which are in the same internal network.
As an immediate action, we deactivated such integration, which will be moved to a separated network and have its architecture reviewed, and possibly discussed with the partner.
As a preventive action, we will be reviewing our network distribution for all products so we don't have applications getting penalised.
We are very sorry about this unfortunate incident.
]]>Update: This maintenance action is still going. Some intermittent network connectivity could affect to some tFlow customers. We will keep you updated. Time: 2018-09-24 09:30AM EST
Update: Services are back and working an expected. Time: 2018-09-25 12:25:00 AM
]]>The index wasn't intentionally disabled, and discovering that it had been disabled took us some time. We had to try other recovery procedures, like freeing up execution plan cache, investigating slow queries and blocking processes, and even restarting the database server. During all these attempts, due to the high CPU load on the server, sometimes we could not even connect to the database from an external computer, which interfered with ou identification of the real issue.
Once we identified the disabled index, we had to once again switch off the Pressero servers, so we could get exclusive access to the server and rebuild/reenable the index. The duration of the entire slowness/partial outage was about two hours, and orders did continue to be received during that period. All other services and products remained up and running without any service interruption.
We do apologize for this inconvenience.
Teoni Valois
Infrastructure Manager / Lead Software Architect
]]>