PDFShift

The HTML to PDF conversion API - Learn more at page:

[PDFShift @pdfshift]

The joys of running an online business ...

[PDFShift @pdfshift]

We just released a new website! Pretty happy with the result.

Our intention here was to focus more on the purpose of PDFShift, which is a technical tool. We also wanted to show to our visitors that we are a reliable service that is here for the long haul.

Hope you'll like it!

[Muze Development @muzedevelopment]

Ever needed to save a webpage as a PDF? Our latest guide has you covered! From browser tricks to advanced API use with @pdfshift , we've got all the tips and tricks. Perfect for offline access or archiving. https://t.co/OLe2eTHZOP

[PDFShift @pdfshift]

The deployment was to fix some minor bugs we had on the API (nothing related to generating PDF) but it caused an unexpected issue with a related library.

[PDFShift @pdfshift]

Today at 2:49 UTC, our two APIs encountered an issue caused by a deployment. We got notified on the issue and quickly worked on resolving the problem. The outage lasted for 40 minutes.
We apologize for the troubles during this incident.

[PDFShift @pdfshift]

A new PDFShift is coming! 👀

[PDFShift @pdfshift]

Our LinkedIn page is up (that's about time!) - you can follow us at https://t.co/wgaXOvYcN0 😇

[PDFShift @pdfshift]

Our Webhook system had a longer downtime though, as it was indirectly impacted by the downtime issue, but everything is now back to normal.

[PDFShift @pdfshift]

We had around one hour of downtime today following our work on making our system more redundant. We continued to run some tests after we resolved the issue, which is why our status page shows for longer issues, but the API was back to normal sooner.

[PDFShift @pdfshift]

That's why you can see a longer downtime per server (for example at SBG) while the API was working properly; we voluntarily killed sbg to ensure the redundancy system was 100% working, which it now is.

[PDFShift @pdfshift]

@jogitanikella Yeah we had some troubles but it's fixed now!

[PDFShift @pdfshift]

We had some issues caused by a script stopping one of our servers. With the redundancy we have, the IPs should have handled that, but some users still got problem accessing our API.
So we updated how we accept incoming and dispatch requests across our network :) All is good now!

[PDFShift @pdfshift]

Would you be interested in the challenges of growing an HTML to PDF conversion API?
Great!

We are looking to hire a VP of Growth at @pdfshift.

Reach out to us to share why you'd be a great fit, and we'll discuss this further :)

[PDFShift @pdfshift]

@heavyacreage Sorry, I'm only reading this now. One of our main servers was down, but we have load balancing in place, so there shouldn't have been any front issues. The other IPs were working fine. (the faulty server was fixed a few hours after the incident)

[PDFShift @pdfshift]

Half the processing servers were down Saturday because of an issue at OVH. This did not cause any issues at all on PDFShift because of the way it was built! (redundancy and performances).

[PDFShift @pdfshift]

@__nxbxdy__ We had a sporadic database issue that is now resolved, and caused some conversions to fail. We then took advantage of the issue to implement a way to still be able to serve the conversions even when the database is down. All is deployed now and we are checking the services.

[PDFShift @pdfshift]

@anjanesh @saviomartin7 In the end, it all comes down to your needs. As I've said, if your current implementation of mPDF works fine for you, there's no need to change, but it might be more interesting in the future :)

[PDFShift @pdfshift]

@anjanesh @saviomartin7 mPDF states that their library is outdated (it is written in their home page) and they recommend using headless Chrome, which is exactly what we are doing. So if you want to use the recent CSS properties and advanced network performances, PDFShift might be better.