There have been sparse incidents reported where your users in the US might not be able to access content or images served from the domain name ik.imagekit.io. The images may not load, or they may receive an SSL error. The error usually resolves automatically after some time, but it can persist longer in some cases.
This is not an issue with ImageKit or the SSL configuration at our end, but with the user's ISP (typically Comcast Xfinity) incorrectly blocking these requests or routing the HTTPS (secure) traffic to HTTP ports. You can also ask your user to report this issue to their ISP.
While we are working with the ISP to get this resolved, if you or your customers face this issue for content on `ik.imagekit.io` domain, there are two ways to resolve it.
Only if you are on a paid plan, you can get a custom domain name setup to use on ImageKit. This is included for free in your paid plan. Instead of serving content via `ik.imagekit.io`, you would be able to serve it via `images.yourwebsite.com` (or any other domain name of your choice). Setting this up requires you to work with our support team (via email or live chat) and takes up to 12 hours, though we usually try to do it in 30 minutes or less.
On any plan of ImageKit including the free plan, instead of loading your images via `ik.imagekit.io` domain name, you can load them `ik.imgkit.net` domain name. You can do this change immediately without any intervention needed by our team.
ik.imgkit.netwould not work with the signed URLs feature in ImageKit for now, contact us if you use signed URLs and we will help you.
With either of these changes, everything else, including your transformation parameters, remains the same. It is just the hostname that needs to change.
We are actively working on this issue with the specific ISP. Let us know if you have any questions regarding this issue.