Is Engagespot Down?

No — Engagespot is up

We cannot measure Engagespot directly — it blocks automated checks — but Engagespot's own status page currently reports no issues.

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://engagespot.statuspage.io

Engagespot uptime

—

Last 7 days

—

Last 30 days

—

Last 90 days

—

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 5 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

Aug 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru

HTTP 404 · challenge

Answered in 116ms — the origin is serving traffic, it just refused our client.

iad

HTTP 404 · challenge

Answered in 88ms — the origin is serving traffic, it just refused our client.

jnb

HTTP 404 · challenge

Answered in 120ms — the origin is serving traffic, it just refused our client.

lax

HTTP 404 · challenge

Answered in 141ms — the origin is serving traffic, it just refused our client.

lhr

HTTP 404 · challenge

Answered in 134ms — the origin is serving traffic, it just refused our client.

nrt

HTTP 404 · challenge

Answered in 81ms — the origin is serving traffic, it just refused our client.

ord

HTTP 404 · challenge

Answered in 160ms — the origin is serving traffic, it just refused our client.

sin

HTTP 404 · challenge

Answered in 91ms — the origin is serving traffic, it just refused our client.

What Engagespot does

Engagespot is notification infrastructure for developers. It takes one API call and fans it out across in-app inboxes, email, push and other channels, applying user preferences and batching rules along the way. Products embed it instead of building notification routing themselves, which places it in the path of messages their users are waiting for.

What an outage looks like

Notifications stop reaching users while the application that triggers them works normally, so nobody sees an error anywhere. In-app notification bells stay empty, and email or push messages are never delivered. Calls to send notifications may fail outright, or accept the request while delivery stalls behind it.

What to do about it

Check Engagespot's status page and read which component is affected: API, Dashboard and Notification Delivery Service are reported separately, and delivery can fail while the API still accepts requests. Queue notifications on your own side rather than dropping them if the API is erroring. For time-critical alerts, keep a channel that does not depend on this path.

Is it down for everyone, or just you?

If this page says Engagespot 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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Engagespot outage FAQ

Are notifications queued and sent later?

It depends which component failed. If the API accepted your request, the notification is inside Engagespot and can go out once the delivery service recovers. If the API rejected the call, nothing was stored and the notification is gone unless your own application retries. That distinction is why the two components are reported separately.

My app works but users get no notifications.

That is the normal shape of this outage. Engagespot sits behind your product, so your application keeps running and the failure is invisible from inside it. Nothing errors on the page the user is looking at; the message simply never arrives. Independent measurement is often how this gets noticed at all.

Does an outage affect every channel at once?

Not necessarily. Engagespot fans a single call out to in-app, email, push and other channels, and delivery to each depends on downstream providers as well as on Engagespot. Users may receive email while push is missing, which makes reports from your own users an unreliable guide to what is actually broken.

What should I do about critical alerts?

Do not route them through a single notification layer. Security codes, payment failures and on-call alerts deserve a path that does not share a dependency with product and marketing notifications. Teams commonly keep a direct provider integration for that small set and use Engagespot for everything else.

How we measure this

We request Engagespot's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
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. We only change the 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 Engagespot publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Engagespot goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required