Is SMTP2GO Down?

No — SMTP2GO is up

SMTP2GO's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 1143 ms

Right now

The verdict is the worse of these two. How we decide

SMTP2GO's status page

smtp2gostatus.com · read 3 minutes ago · checked every 3 minutes

Operational

SMTP2GO's components, as its status page reports them
Component	Status
Email sending (SMTP service)	Operational
API Servers	Operational
SMS Messaging	Operational
SMTP2GO Website	Operational
Member Dashboard	Operational

Open their status page

FlareWarden checks

app.smtp2go.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 1143 ms
Checked: 5 hours ago

By region

Amsterdam reachable, 678 ms
Chicago reachable, 715 ms
London reachable, 639 ms
San Jose reachable, 581 ms
Singapore reachable, 2054 ms
Sydney reachable, 2794 ms
Tokyo reachable, 1451 ms
Toronto reachable, 235 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	0 ms	76 ms	79 ms	678 ms
Chicago	0 ms	106 ms	110 ms	715 ms
London	0 ms	70 ms	73 ms	639 ms
San Jose	0 ms	65 ms	69 ms	581 ms
Singapore	0 ms	223 ms	227 ms	2054 ms
Sydney	567 ms	332 ms	336 ms	2794 ms
Tokyo	0 ms	162 ms	166 ms	1451 ms
Toronto	0 ms	15 ms	20 ms	235 ms

We check that app.smtp2go.com loads, not every feature behind it. Test it yourself

History

Incidents SMTP2GO reported

Since Oct 22, 2 days · from smtp2gostatus.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

SMTP2GO website availability

Measured by FlareWarden · app.smtp2go.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 832ms

Last 30 days

18-day clean streak

Sep 24 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of app.smtp2go.com from multiple regions every 6 hours. SMTP2GO's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 18 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What SMTP2GO does

SMTP2GO is an outbound email relay. Businesses point applications, websites, mail clients and devices at mail.smtp2go.com, or call its email API, and SMTP2GO handles delivery to recipients. It also sends SMS by API or email-to-SMS. Accounts are hosted in US, EU or Australian data centers, and the dashboard's Activity report shows each email's delivery status.

What an outage looks like

Apps and mail clients cannot connect to mail.smtp2go.com, time out mid-session, a telnet test returns Connect failed, and the dashboard login page may load slowly. The most common SMTP2GO incident leaves emails stuck as Processed in the Activity report: accepted and queued, but not yet delivered. Other incidents only delay Activity updates, so delivered mail still shows Processed, or affect one region such as Australia.

What to do about it

Check smtp2gostatus.com, which tracks email sending, API servers, SMS messaging, the website and the member dashboard separately. Mail already showing Processed is queued on SMTP2GO's side and goes out as the backlog clears, so there is no need to resend it. If connections fail, try another port (25, 2525, 8025, 587 or 80, or 465, 8465 or 443 for SSL) or a regional host: mail-us, mail-eu or mail-au.smtp2go.com.

Is it down for everyone, or just you?

If this page says SMTP2GO is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

SMTP2GO outage FAQ

Is SMTP2GO down for everyone or just me?

Check smtp2gostatus.com, then test the connection yourself: SMTP2GO's troubleshooting guide suggests running telnet mail.smtp2go.com 2525, and a 220 reply means its servers are reachable, so the fault lies in your app, credentials or network. A 535 error means wrong SMTP credentials, not an outage. The checks on this page probe app.smtp2go.com, the dashboard login host, so they show whether the web app is up rather than the SMTP relay itself.

Which SMTP2GO ports can I use if one is blocked?

Ports 25, 2525, 8025, 587 and 80 accept TLS or unencrypted connections, and ports 465, 8465 and 443 accept SSL. SMTP2GO notes that internet providers block some ports, so switching ports is the first fix for a connection that fails only from one network. If your software can only use an IP address, SMTP2GO publishes fixed IPs for North America, Europe and Australia in its Connecting to an IP Address article.

Will emails stuck as Processed in SMTP2GO still be delivered?

Yes, in most incidents. Processed means SMTP2GO has received the email and queued it for delivery, and its incident updates describe the Processed backlog being worked through once a fix is in. During Activity reporting delays the email may already have arrived while the status lags. Bounces are different: SMTP2GO says a hard or soft bounce is final and is never retried, so those need resending.

Does an SMTP2GO outage affect every region?

Often not. SMTP2GO routes each connection to the nearest server and keeps accounts in US, EU or Australian data centers, and many incidents on its status page are limited to the AU region or to EU customers. When mail.smtp2go.com has been unreachable, SMTP2GO has told customers to connect through mail-eu.smtp2go.com or mail-us.smtp2go.com instead. If your firewall allowlists its IPs, make sure newly added inbound addresses are included.

How long do SMTP2GO outages usually last?

Most are resolved within a working day. Of the 50 most recent incidents on smtp2gostatus.com, 42 were resolved within 12 hours and 22 within four hours; four lasted more than a day. You can subscribe there by email, text message, Slack, webhook or RSS. To reach support, generate the 5-digit Support PIN from the dashboard's Support menu; free accounts older than 14 days get ticket support only.

How we measure this

We request SMTP2GO's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where SMTP2GO publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of SMTP2GO itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when SMTP2GO goes down

We check SMTP2GO every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required