Skip to content

Outage tracker / Omnisend / In the US

Is Omnisend down in the US?

Vendor reports no incidentWhat Omnisend reports

Omnisend reports no incident on its status page.

As of the last successful poll, 2026-11-07 18:03 UTC.

Omnisend's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Omnisend at Nov 7, 2026, 6:13 PM UTC.

Over the last 24 hours we completed 262 checks from Ashburn and San Jose and 262 answered cleanly, 100.00% availability.

Of the 2 other regions we check Omnisend from, all 2 read checks passing right now.

Email me when Omnisend reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Omnisend's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing141 checks in 24h, 100.00%
San JoseChecks passing121 checks in 24h, 100.00%

Last checked Nov 7, 2026, 6:13 PM UTC.

Omnisend from Ashburn and San Jose over the last 30 days

Over the last 30 days, Omnisend answered our Ashburn probe in 1,796 ms on average, and 1 check in 20 took longer than 2,492 ms.

Over the last 30 days, Omnisend answered our San Jose probe in 2,209 ms on average, and 1 check in 20 took longer than 3,050 ms.

Ranked by average response time across the 4 cities we check Omnisend from, Ashburn 1st, San Jose 3rd; Ashburn was fastest at 1,796 ms and Tokyo slowest at 2,943 ms.

From Ashburn and San Jose we ran 1,290 checks of Omnisend in 6 days, and 1,287 answered cleanly: 99.76% availability.

2 of the 6 days had at least one failed check. The weakest was Nov 6 (UTC), at 99.19% across 249 checks.

In Ashburn local time (EST), Omnisend was slowest around 2 AM, at 2,297 ms on average over the last 14 days, and quickest around 10 AM, at 1,611 ms.

Day (UTC)ChecksAvailabilityAverage response
Sat, Nov 7203100.00%2,023 ms
Fri, Nov 624999.19%1,943 ms
Thu, Nov 5247100.00%1,921 ms
Wed, Nov 4248100.00%1,885 ms
Tue, Nov 324199.58%2,066 ms
Mon, Nov 2102100.00%2,104 ms

Omnisend outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Omnisend outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Omnisend from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 116 checks
TokyoChecks passing100.00% of 66 checks

Other countries we check Omnisend from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Omnisend's public endpoints. They are not user reports, and they are not Omnisend's own status page.

See Omnisend's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Omnisend has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter