Is Gladly Down?

No — Gladly is up

Reachable from all 8 checked regions

Average response time: 880ms

Last checked 1 hour ago · checks run every 6 hours

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

Gladly 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 — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

Jul 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.

iad

632ms

DNS 283ms TCP 2ms TLS 10ms TTFB 613ms

jnb

1238ms

DNS 190ms TCP 0ms TLS 60ms TTFB 779ms

lax

550ms

DNS 21ms TCP 1ms TLS 27ms TTFB 367ms

lhr

547ms

DNS 37ms TCP 2ms TLS 9ms TTFB 467ms

nrt

840ms

DNS 134ms TCP 1ms TLS 11ms TTFB 490ms

ord

343ms

DNS 46ms TCP 1ms TLS 27ms TTFB 318ms

sin

1978ms

DNS 283ms TCP 1ms TLS 6ms TTFB 1284ms

sjc

485ms

DNS 88ms TCP 1ms TLS 8ms TTFB 404ms

syd

1065ms

DNS 114ms TCP 11ms TLS 38ms TTFB 615ms

What Gladly does

Gladly is a customer service platform built around the customer rather than the ticket, giving agents one timeline per person across voice, email, SMS, chat, WhatsApp, Instagram and Facebook Messenger. Consumer brands use it as the system their support team works in all day, so an outage stops the contact center rather than degrading a side feature.

What an outage looks like

Agents cannot sign in, or sign in and find conversations missing because search or routing is affected. One channel commonly fails while others keep working: voice drops while email and SMS continue, or Instagram and WhatsApp stall while the Glad App chat widget on the brand's own site is fine. Reporting and Tasks fail independently of the channels.

What to do about it

Gladly's own guidance is channel-specific: switch voice to a voicemail-only IVR or move customers to another channel, mark chat closed with an alternative contact route on display, and let SMS and email wait, since they are asynchronous. Subscribe to gladly.statuspage.io for updates, and use Gladly's support form if the incident is what is stopping you signing in.

Is it down for everyone, or just you?

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

Test it yourself

Related services

Gladly outage FAQ

Which Gladly channel is affected?

Check the rows individually. Gladly tracks Channel - Voice, Email, SMS, Chat (Glad App), WhatsApp, Instagram and Facebook Messenger as separate components, and incidents regularly hit one without the others. Login, Search, Reporting, Tasks and Routing are tracked apart again, so agents being unable to work does not necessarily mean any channel is down.

Do customer messages arrive after the outage clears?

For the asynchronous channels, usually yes, which is why Gladly advises letting SMS and email wait rather than acting. Voice and live chat are different: a call that could not connect and a chat that was never opened do not queue anywhere. That is the reasoning behind switching voice to a voicemail-only IVR, which turns a lost call into a message.

How do I contact Gladly support if I cannot log in?

Gladly publishes a support form for exactly this case, so being locked out by the incident does not leave you without a route. Its documented advice is also to subscribe to the status page in advance, because during an incident the fastest confirmation that the problem is platform-wide comes from there rather than from a support reply.

Is Gladly AI affected separately from the rest?

Yes. Gladly AI Solution is its own component, listed alongside Gladly Team Solution and the legacy Structured Threads Solution. An AI-side incident affects automated replies and assistance while human agents keep working normally, and the reverse also happens. Check which of the three solution rows is affected before assuming the whole platform is out.

How we measure this

We request Gladly's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
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 Gladly 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 Gladly goes down

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

Start Free Monitoring

Free plan available No credit card required