It’s probably a DNS issue, we’ve seen sometimes a similar thing, with some API endpoints but it got resolved by itself.
Might be able to fix it by using resolv-replace
gem.
It’s probably a DNS issue, we’ve seen sometimes a similar thing, with some API endpoints but it got resolved by itself.
Might be able to fix it by using resolv-replace
gem.