Heymarket Outage History

Heymarket had 6 outages in the last 2 years totaling 26h 37m of downtime — averaging 0.2 incidents per month.

There were 6 Heymarket outages since June 12, 2025 totaling 26h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.heymarket.com

Notice May 12, 2026

API issue affecting integrations with HubSpot, Salesforce, and Microsoft Teams

Detected by Pingoru: May 12, 2026, 06:42 PM UTC
Resolved: May 12, 2026, 08:03 PM UTC
Duration: 1h 21m

Affected: Integrations

Timeline · 2 updates

investigating May 12, 2026, 06:42 PM UTC

We are investigating an issue affecting our integrations with HubSpot, Salesforce, and Microsoft Teams. Customers using these integrations may experience intermittent disruptions. Our engineering team is actively working to identify the cause and restore stability.
resolved May 12, 2026, 08:03 PM UTC

This incident has been resolved.

Read the full incident report →

Minor December 2, 2025

Delay in processing incoming messages

Detected by Pingoru: Dec 02, 2025, 08:04 PM UTC
Resolved: Dec 02, 2025, 09:35 PM UTC
Duration: 1h 31m

Affected: Messaging

Timeline · 2 updates

identified Dec 02, 2025, 08:04 PM UTC

We have identified a delay in processing incoming messages. Our engineering team is working on a fix.
resolved Dec 02, 2025, 09:35 PM UTC

This incident has been resolved.

Read the full incident report →

Minor November 11, 2025

Service Interruption

Detected by Pingoru: Nov 11, 2025, 07:02 PM UTC
Resolved: Nov 11, 2025, 08:17 PM UTC
Duration: 1h 14m

Affected: Web App (app.heymarket.com)

Timeline · 5 updates

investigating Nov 11, 2025, 07:02 PM UTC

We are currently investigating this issue.
identified Nov 11, 2025, 07:57 PM UTC

The issue has been identified and a fix is being implemented.
identified Nov 11, 2025, 07:58 PM UTC

We are continuing to work on a fix for this issue.
identified Nov 11, 2025, 08:01 PM UTC

We are continuing to work on a fix for this issue.
resolved Nov 11, 2025, 08:17 PM UTC

This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

SMS Delivery Delays and Failures to AT&T Network in the US for a Subset of 10 Digit Long Codes

Detected by Pingoru: Oct 20, 2025, 06:07 PM UTC
Resolved: Oct 20, 2025, 11:40 PM UTC
Duration: 5h 33m

Affected: Messaging

Timeline · 4 updates

investigating Oct 20, 2025, 06:07 PM UTC

Carrier is reporting SMS delivery delays when sending messages to AT&T US Network via a subset of 10DLC long codes that is impacting a subset of users.
investigating Oct 20, 2025, 11:29 PM UTC

This incident has been resolved.
investigating Oct 20, 2025, 11:40 PM UTC

We are continuing to investigate this issue.
resolved Oct 20, 2025, 11:40 PM UTC

This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

Carrier Service Incident

Detected by Pingoru: Oct 20, 2025, 07:26 AM UTC
Resolved: Oct 20, 2025, 11:06 PM UTC
Duration: 15h 39m

Affected: Messaging

Timeline · 4 updates

investigating Oct 20, 2025, 07:04 PM UTC

We are currently tracking an upstream provider incident that is impacting a subset of users. The issue has been identified as stemming from an underlying infrastructure problem within a major cloud provider’s U.S. region.
identified Oct 20, 2025, 07:05 PM UTC

A fix has been identified by the carrier and is currently being worked on and monitored.
monitoring Oct 20, 2025, 07:06 PM UTC

A fix has been implemented and we are monitoring the results.
resolved Oct 20, 2025, 11:36 PM UTC

This incident has been resolved.

Read the full incident report →

Notice June 12, 2025

Heymarket.com down due to Cloudfare outage

Detected by Pingoru: Jun 12, 2025, 07:05 PM UTC
Resolved: Jun 12, 2025, 08:22 PM UTC
Duration: 1h 17m

Timeline · 2 updates

monitoring Jun 12, 2025, 07:05 PM UTC

Cloudflare is currently investigating an outage that is preventing Heymarket.com’s marketing site from loading. https://www.cloudflarestatus.com/incidents/25r9t0vz99rp
resolved Jun 12, 2025, 08:22 PM UTC

This incident has been resolved.

Read the full incident report →