can't ping api.sendgrid.com from my droplet

February 25, 2019 402 views
DigitalOcean Networking

I created a droplet recently (Ubuntu Docker 18.06.1~ce~3 on 18.04).
And I realize emails couldn’t be sent by my application.

I’m using SendGrid’s API.

It works perfectly from my local machine.

I can’t even ping api.sendgrid.com from my droplet.

PING api.sendgrid.com (159.122.219.48) 56(84) bytes of data.
— api.sendgrid.com ping statistics —
328 packets transmitted, 0 received, 100% packet loss, time 335312ms

It works well if I try locally:

$ ping api.sengrid.com
PING api.sengrid.com (85.128.131.76): 56 data bytes
64 bytes from 85.128.131.76: icmpseq=0 ttl=50 time=85.898 ms
64 bytes from 85.128.131.76: icmp
seq=1 ttl=50 time=79.936 ms
64 bytes from 85.128.131.76: icmp_seq=2 ttl=50 time=112.295 ms

Why is that endpoint not reachable ?
I tried other endpoints without issues.

2 comments
  • I tried from to other droplets (NYC2 & NYC3), it works!
    But it doesn’t from my AMS3 droplet… 😕

  • I’d check that they are using the same nameservers specified in /etc/resolv.conf on linux as well as using dig or mtr to find where exactly the DNS resolution is obstructed.

3 Answers

Hey friend!

This is a good question. I feel like it may be possible that SendGrid has blocked that IP or range that your droplet is on. You might reach out to their support and ask. I could be wrong, it could be what @JosephPersie mentioned because the IP you’re pinging from the droplet doesn’t look to be one on the api.sendgrid.com A record, yet I can still ping that IP locally anyway.

Jarland

Thank you for your answer! 🙂
I couldn’t wait to deploy that application, so I simply used another droplet.
But I’ll keep that in mind if it happens again.

Hey @aduermael,
I had faced the same issue, Your IP has been blocked by Sendgrid.
My Peer suggested me to switch the delivery service and I started using Pepipost,
API Configuration is much easier now. :)

Have another answer? Share your knowledge.