Live Domain Check

Is SendGrid Down? Check sendgrid.com Status and Outages

Run a live reachability check for sendgrid.com. Compare the regional responses with the problem you see in SendGrid.

Find SendGrid help and reporting links, specific checks, and step-by-step guidance below the live result.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked-

Verdict-

Response Time-

Final URL-

Regional checks8 regions

Rate:

No ratings yet.

Is SendGrid working for you?

Share a quick update and see what other visitors are experiencing.

Loading community reports…

Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy

Understanding SendGrid connection and service problems

SendGrid API submission, message processing and recipient delivery are distinct outcomes.

The checker above requests sendgrid.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual SendGrid action that failed. A homepage response alone cannot verify an account, app workflow or transaction.

Looking for another service? Browse developer service checks.

SendGrid status information and official help

SendGrid service status

Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.

SendGrid help and reporting

Select the SendGrid/email component; unrelated Twilio voice incidents may not apply.

Open sendgrid.com

Open the website in your browser and compare it with the result above.

Where to report problems with SendGrid

Open SendGrid help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.

Details to include in your report

Message ID, submit/delivery time, SMTP/API response and recipient-domain scope without mail contents or credentials.

Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to SendGrid.

What to check when SendGrid is not working

These are troubleshooting comparisons, not claims that SendGrid is currently experiencing a particular incident.

Start with the action that failed

Check whether SendGrid accepted the request and inspect the message's subsequent delivery event before resending.

Narrow down the affected service

Match the email product in Twilio's status information; a recipient rejection requires its actual bounce response.

Read the actual checker response

A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.

How to check if SendGrid is down

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the sendgrid.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
Check for a service notice. Open SendGrid status and check whether the named service and incident time fit your error.
Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.

If SendGrid Is Not Working Only For You, Start Here

Use these local troubleshooting steps after the down-check workflow when SendGrid seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open sendgrid.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.

2. Preserve a working account session

Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader SendGrid issue.

3. Try another network

If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting SendGrid support.

Frequently asked questions about SendGrid problems

Is SendGrid down, or is the problem limited to one feature?

Run the sendgrid.com check and compare its original timestamps and responses with your actual error. SendGrid API submission, message processing and recipient delivery are distinct outcomes.

Where can I report a problem with SendGrid?

Use the community buttons on this page to share whether the service works for you. For help from SendGrid, use the official help/reporting resource linked above. Select the SendGrid/email component; unrelated Twilio voice incidents may not apply.

What should I check first when SendGrid is not working?

Check whether SendGrid accepted the request and inspect the message's subsequent delivery event before resending. Match the email product in Twilio's status information; a recipient rejection requires its actual bounce response.

What information helps SendGrid support investigate?