Is Apollo.io Down?

No — Apollo.io is up

Reachable from all 8 checked regions

Average response time: 138ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.apollo.io

Apollo.io uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

174ms

Avg response, 30 days

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

30-day history

16-day clean streak

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

ams

184ms

DNS 0ms TCP 1ms TLS 11ms TTFB 160ms

arn

211ms

DNS 1ms TCP 1ms TLS 17ms TTFB 146ms

bom

101ms

DNS 1ms TCP 2ms TLS 16ms TTFB 75ms

cdg

168ms

DNS 0ms TCP 11ms TLS 20ms TTFB 118ms

dfw

270ms

DNS 0ms TCP 1ms TLS 16ms TTFB 187ms

ewr

73ms

DNS 0ms TCP 1ms TLS 10ms TTFB 57ms

fra

79ms

DNS 0ms TCP 1ms TLS 14ms TTFB 63ms

gru

137ms

DNS 0ms TCP 2ms TLS 10ms TTFB 118ms

iad

65ms

DNS 0ms TCP 1ms TLS 9ms TTFB 47ms

What Apollo.io does

Apollo.io is a B2B sales platform that combines a contact database with outbound sequencing: reps search for prospects, enrich records with emails and phone numbers, and run email sequences from the same tool. Sales teams build their pipeline on it, so an outage stops prospecting and pauses sequences already running against live prospects.

What an outage looks like

Search and list building slow down or return errors before anything else does, matching Apollo's own history of search and queue degradation. Sequence emails send late or stall in the queue, and contact enrichment stops returning results, so records save with the email or mobile number missing. The web app at app.apollo.io can be degraded while the marketing site loads normally.

What to do about it

Check status.apollo.io, which tracks app.apollo.io separately from the marketing site and reports latency for background jobs, email sending and mobile number fulfilment. Much of what fails here is slow rather than broken, so give queued sequence steps time before resending. Do not re-run a large enrichment job mid-incident: empty results are hard to tell apart afterwards from prospects that genuinely have no data.

Is it down for everyone, or just you?

If this page says Apollo.io 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

Apollo.io outage FAQ

Is Apollo down or is my search just slow?

Apollo reports latency rather than only up or down for background jobs, email sending and number fulfilment, because degradation is the more common failure here. A search that takes far longer than usual but eventually returns is consistent with a latency incident. Check status.apollo.io for the specific component before assuming the query or your filters are at fault.

Do sequence emails still send during an Apollo outage?

They generally queue rather than being cancelled, and Apollo tracks email sending latency as its own measure. The risk is timing rather than loss: a step meant to go out on a Tuesday morning can land at an odd hour once the backlog drains. Pause time-sensitive sequences during a long incident rather than letting them catch up unsupervised.

Why do enriched contacts save without a phone number?

Apollo fulfils mobile numbers through a separate pipeline with its own latency component, so enrichment can return an email while the number request is still outstanding or failing. During an incident the record saves with that field empty. Re-enrich those specific contacts after the service recovers rather than concluding the numbers do not exist.

Is app.apollo.io down if the Apollo website loads?

Possibly. Apollo lists the main site, www.apollo.io and app.apollo.io as separate components, and the marketing pages are served independently of the application. Loading apollo.io tells you almost nothing about whether reps can sign in and work. Check the app component specifically, and have one person try signing in rather than everyone retrying at once.

How we measure this

We request Apollo.io'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 Apollo.io 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 Apollo.io 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