We started checking Keap on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Keap reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Keap's own status page declared. Below it, any public chatter we saw about Keap and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Keap's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Keap in the last 24 hours, which is not evidence that nothing is wrong.
Keap's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Keap's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Keap next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
99.77%
427
US-West
99.38%
321
Europe
100.00%
294
Asia-Pacific
100.00%
179
Their declared record
Keap's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Thryv Business Center - Platform DownMajor outage
Jul 8, 2026, 4:42 PM UTC to Jul 8, 2026, 5:51 PM UTC (1h 9m)resolved
their latest update (Jul 8, 2026, 5:51 PM UTC): This issue has been fully resolved.
Marketing Center Reputation Review Response - Continuous LoadingMajor outage
Jun 11, 2026, 1:39 PM UTC to Jun 11, 2026, 2:10 PM UTC (31 min)resolved
their latest update (Jun 11, 2026, 2:10 PM UTC): Our development team was able to quickly identify the root cause for this issue and a fix has been implemented. We are seeing the Reputation tab fully loading and functioning as expected within the Marketing Center platform.
Please reach out to our Thryv Support Team if any fur…
ThryvPayPartial outage
Mar 11, 2026, 8:27 PM UTC to Mar 11, 2026, 10:00 PM UTC (1h 33m)resolved
their latest update (Mar 11, 2026, 10:00 PM UTC): This incident is fully resolved.
Business Center & Marketing Center - Listings Management, ReputationMajor outage
Mar 4, 2026, 2:53 PM UTC to Mar 4, 2026, 5:39 PM UTC (2h 46m)resolved
their latest update (Mar 4, 2026, 5:39 PM UTC): This issue has been resolved. All systems are operational.
Scheduled Social Posting - Marketing Center & Business CenterPartial outage
Feb 13, 2026, 4:15 PM UTC to Feb 13, 2026, 4:54 PM UTC (40 min)resolved
their latest update (Feb 13, 2026, 4:54 PM UTC): A fix for this has been implemented and the Scheduled Social Posting feature is functioning normally. Users will need to log out and log back in to their thryv software. Our team will continue to monitor for any further disruptions.
Social Scheduled Posting - Marketing Center and Business CenterAll systems operational
Jan 15, 2026, 2:00 PM UTC to Jan 15, 2026, 2:00 PM UTC (0 min)resolved
their latest update (Jan 15, 2026, 2:00 PM UTC): On January 15th 2026 at approximately 8am CT we received reports of users being unable to schedule social posts through the Social feature within Marketing Center and Business Center.
Issue Experience: Users were unable to schedule social posts as they normally would through the…
Business Center - Calendar on Mobile Application and DesktopMinor incident
Dec 2, 2025, 4:27 PM UTC to Dec 2, 2025, 5:30 PM UTC (1h 3m)resolved
their latest update (Dec 2, 2025, 5:30 PM UTC): This incident has been resolved.
Business Center - Mobile App and DesktopMinor incident
Nov 26, 2025, 3:04 PM UTC to Nov 27, 2025, 3:30 PM UTC (1d 0h)resolved
their latest update (Nov 27, 2025, 3:30 PM UTC): Our development team has implemented a fix that has resolved the issue. We suggest users to log out, force close the app in the background, and log in one more time. Please reach out to our Thryv support team if any further issues persist.
Business Center Mobile App - Access ErrorPartial outage
Nov 25, 2025, 3:19 PM UTC to Nov 25, 2025, 4:37 PM UTC (1h 19m)resolved
their latest update (Nov 25, 2025, 4:37 PM UTC): The issue preventing users from accessing the Business Center mobile app has been fully resolved.
Business Center - Mobile AppMinor incident
Oct 27, 2025, 7:53 PM UTC to Oct 28, 2025, 3:16 PM UTC (19h 23m)resolved
their latest update (Oct 28, 2025, 3:16 PM UTC): This incident has been resolved. Our development has implemented measures that have resolved users being unable to access the thryv Business Center mobile application.
Showing the 10 most recent of 50 incidents Keap has declared in the history we hold.
These entries are Keap's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Keap's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.