PrintNode services were unavailable or intermittent from approximately 22:17 UTC to 22:52 UTC today due to a database issue. We have restored normal service and are monitoring the system closely. Our apologies to any users who experienced disruption as a result of this outage.
We have received reports of connectivity issues affecting some customers. Our internal and external monitoring systems show normal operation and we are investigating the possibility of an external network issue.
Hello, Zapier users! For early access to the PrintNode-Zapier integration (and to help us test it!), please use the following link: https://t.co/b5j0q0dTGK. All feedback welcome :-)
We are investigating reports of slow responses from the HTTP API, specifically the GET /printjobs endpoint. For some users, this may cause Print History not to be displayed in the web application.
Our data centre made routing changes to avoid traffic from an upstream Telia device. As of 19:17 UTC you should see improvements, please contact us if you are still encountering issues.
The data centre has informed us that their maintenance work, which caused the outage, has been completed for the time being and that there should be no further disruptions.
The issue seems to affect a small minority of users who connect from AWS. We are working with our data centre to resolve it, but as it seems to originate somewhere between AWS servers and ours, it is beyond our control. To help us troubleshoot, please raise an issue with AWS.
Our email service provider is experiencing an issue which is delaying their email and webhook processing. This may cause delays or service interruption for email-based printing. Other PrintNode functionality is unaffected. We will issue updates as we receive more information.
At least partial connectivity has been restored; we are continuing to monitor and work with the data centre to understand the likelihood of further disruption.
Network maintenance in our UK data centre is causing an interruption to PrintNode online services. We are working with the data centre to limit the impact and will post an update shortly.
@fishstick51 The router issues were resolved on 2020-05-28 at around 03:20 UTC. For up-to-date information please check https://t.co/RyGhJlI0fn or contact us directly at [email protected]