@pdfshift

The HTML to PDF conversion API - Learn more at https://xitter.cf/t.co/VZfHRWiF5L Status page: https://xitter.cf/t.co/rDmN8Ng2gH

pdfshift.io
Joined May 2018
  • Tweets177
  • Following95
  • Followers184
3Media
The joys of running an online business ...
1
2,166
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!
2
1
4
1,911
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. muzedevelopment.com/blog/gui…
1
3
937
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.
1
3
750
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.
669
A new PDFShift is coming! 👀
1
1
6
761
Our LinkedIn page is up (that's about time!) - you can follow us at linkedin.com/company/pdfshif… 😇

PDFShift.io | LinkedIn

PDFShift.io | 13 followers on LinkedIn. Convert HTML to PDF fast and easy with PDFShift. High-quality website and HTML conversion to PDF via API. | Convert HTML to PDF fast and easy with PDFShift....

linkedin.com
1
630
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.
1
1
1
612
more replies
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.
1
465
Our Webhook system had a longer downtime though, as it was indirectly impacted by the downtime issue, but everything is now back to normal.
408
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!
2
371
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 :)
1
1
3
832
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).
1
1
2
503
We've started migrating to OVH and updated the status page to reflect our servers with direct health checks : status.pdfshift.io/ (the grey bars are because the checks are new)

PDFShift status

Welcome to PDFShift status page for real-time and historical data on system performance.

status.pdfshift.io
3
3
Now, what we'll do is first reach out to a few key users about this new infrastructure, and see how it operates. Then, in a few weeks, we'll start balancing the requests between AWS and OVH, and once we are sure the new code is working well, we'll stop AWS.
3
PDFShift will run on two distinct regions and each region can handle the current load of what we serve at AWS ... TWICE! This should give us plenty of room for the next steps.
2
Great news! The new servers are up and running (but we haven't changed the DNS yet). You can try with api.sbg.pdfshift.io and api.gra.pdfshift.io. Yes, we are on two distinct regions now, so one can catch fire ;)
2
676 successful tests (100%) to the `convert/pdf` endpoint seems to indicate the migration is going well.
3
Load more