Service status & outage reports

Is Heart Internet down?

Check Heart Internet availability, incident history, downtime reports, and website performance.

https://www.heartinternet.uk ↗

Provider reports service problems

The official provider feed identifies an active incident or affected component.

0 recorded outage reports · rolling 24 hours

Text version ↗

My watchlist

Estimated down reports for Heart Internet

Last 24 hours

There is not enough activity for a usable 24-hour estimate. Status and website measurements remain available below.

Last collection attempt: 2026-10-20 07:59:29 UTC · Insufficient activity.

No user-submitted outage reports in the last 24 hours.

Heart Internet outage history

2025–2026

Daily history over the past 12 months. Select a day for its evidence.

NovDecJanFebMarAprMayJunJulAugSepOct

GoodDown / service issuesNot enough data

Select a square for daily details. Scroll sideways to explore earlier months.

How to read this calendar

Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.

Heart Internet website uptime and response time

Current website availability is unknown. No website checks available yet.

Unknown
Successful website checks (24h)
0 successful / 0 measurable checks

Unknown
Median response time

Unknown
95th percentile response time

0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.

Evidence behind the status

Provider reports service problems. The official provider feed identifies an active incident or affected component.

Website checks and estimated activity have independent update times. Refer to each section for its latest observation.

These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.

Official component status

Heart Internet official status · fetched 2026-10-22 00:01:02 UTC

61 mapped components · 7 reporting problems

Component	Provider status
Heart Internet - DNS	operational
Heart Internet - Services	operational
Heart Internet - Shared Hosting Servers	degraded performance
Heart Internet - Shared Mail	operational
Heart Internet - FTP	operational
Heart Internet - Windows Services	degraded performance
Cluster 1 (Web 310, Web311)	operational
Cluster 10 (web32, 33, 34, 35, 36)	operational
Cluster 11 (web37, 38, 39, 40, 41)	operational
Cluster 12 (web42, 43, 44, 45, 46)	operational
Cluster 13 (web47, 48, 49, 50)	operational
Cluster 14 (web52, 53, 54, 55)	operational
Cluster 15 (web160, 161, 162, 163)	operational
Cluster 16 (web165, 166, 167, 168)	operational
Cluster 17 (web170, 171, 172, 173)	operational
Cluster 18 (web175, 176, 177, 178)	operational
Cluster 19 (web180, 181, 182, 183)	operational
Cluster 20 (web224, 225, 226, 227)	operational
Cluster 21 (web229, 230, 231, 232, 233)	operational
Cluster 22 (web234, 235, 236, 237)	operational
Cluster 23 (web244, 245, 246, 247, 248)	operational
Cluster 24 (web100, 101, 102, 103)	operational
Cluster 25 (web105, 106, 107, 108)	operational
Cluster 26 (web110, 111, 112, 113)	operational
Cluster 27 (web115, 116, 117, 118)	operational
Cluster 28 (web120, 121, 122, 123)	operational
Cluster 29 (web125, 126, 127, 128)	operational
Cluster 30 (web130, 131, 132, 133)	operational
Cluster 31 (web135, 136, 137, 138)	operational
Cluster 33 (web140, 141, 142)	operational
Cluster 34 (web145, 146, 147, 148)	operational
Cluster 35 (web150, 151, 152)	operational
Cluster 36 (web155, 156, 157)	operational
Cluster 38 (web75, 76, 77, 78)	operational
Cluster 39 (web80, 81, 82, 83)	operational
Cluster 40 (web85, 86, 87, 88)	operational
Cluster 41 (web90, 91, 92, 93)	operational
Cluster 42 (web95, 96, 97, 98)	operational
Cluster 43 (web239, 240, 241, 242)	operational
Cluster 44 (web1, 2, 3, 4)	operational
Cluster 45 (web6, 7, 8, 9)	operational
Cluster 46 (web11, 12, 13, 14)	operational
Cluster 47 (web16, 17, 18, 19)	operational
Cluster 48 (web21, 22, 23, 24)	operational
Cluster 49 (web26, 27, 28, 29)	operational
Cluster 50 (web57, 58, 59, 60)	operational
Cluster 51 (web62, 63, 64, 65)	operational
Cluster 52 (web67, 68, 69, 70)	operational
Cluster 53 (web71, 72, 73, 74)	operational
Cluster 54 (web189, 190, 191, 192)	operational
Cluster 55 (web193, 194, 195, 196)	operational
Cluster 56 (web197, 198, 199, 200)	operational
Cluster 57 (web249, 250, 251, 252)	operational
Cluster 58 (web298, 299, 300, 301)	operational
Cluster 59 (web302, 303, 304, 305)	operational
Cluster 60 (web306, 307, 308, 309)	operational
Shared cPanel - Server 1	degraded performance
Shared cPanel - Server 2	degraded performance
Shared cPanel - Server 3	degraded performance
Shared cPanel - Server 4	degraded performance
Shared cPanel - Server 5	degraded performance

Official incident timeline

Critical PHP Vulnerabilities · investigating · 2026-10-21T08:10:00.000Z

Product match: components.

Read the provider’s incident report

2026-10-21T08:10:00.000Z ·
We are aware of critical vulnerabilities affecting PHP that pose a risk to the affected versions. We have implemented initial mitigation but this is not a complete fix at this time. We are monitoring the risks and are ready to implement further mitigation and security patches as soon as they become available. We will update this status page once we have more information on the vulnerabilities and any potential fixes. Update: We have mitigated all Shared Hosting, Managed VPS and Managed WordPr

Cluster 10 (web32, 33, 34, 35, 36), Cluster 44 (web1, 2, 3, 4), and 2 other services are down · resolved · 2026-10-21T03:36:10.855Z

Product match: components.

Read the provider’s incident report

2026-10-21T03:34:50.386Z ·
Cluster 56 (web197, 198, 199, 200) recovered.
2026-10-21T02:05:04.047Z ·
Cluster 10 (web32, 33, 34, 35, 36) went down.
2026-10-21T02:06:34.082Z ·
Cluster 44 (web1, 2, 3, 4) went down.
2026-10-21T02:07:31.479Z ·
Cluster 49 (web26, 27, 28, 29) went down.
2026-10-21T02:08:38.960Z ·
Cluster 56 (web197, 198, 199, 200) went down.
2026-10-21T03:22:38.227Z ·
Cluster 44 (web1, 2, 3, 4) recovered.
2026-10-21T03:23:27.875Z ·
Cluster 49 (web26, 27, 28, 29) recovered.
2026-10-21T03:36:10.855Z ·
Cluster 10 (web32, 33, 34, 35, 36) recovered.

Cluster 24 (web100, 101, 102, 103), Cluster 38 (web75, 76, 77, 78), and 1 other service are down · resolved · 2026-10-20T05:54:22.843Z

Product match: components.

Read the provider’s incident report

2026-10-20T02:56:43.166Z ·
Cluster 45 (web6, 7, 8, 9) went down.
2026-10-20T04:42:52.624Z ·
Cluster 45 (web6, 7, 8, 9) recovered.
2026-10-20T02:36:32.051Z ·
Cluster 38 (web75, 76, 77, 78) went down.
2026-10-20T02:41:39.458Z ·
Cluster 38 (web75, 76, 77, 78) recovered.
2026-10-20T05:38:22.748Z ·
Cluster 24 (web100, 101, 102, 103) went down.
2026-10-20T05:54:22.843Z ·
Cluster 24 (web100, 101, 102, 103) recovered.

Cluster 54 (web189, 190, 191, 192) is down · resolved · 2026-10-19T13:12:14.448Z

Product match: components.

Read the provider’s incident report

2026-10-19T12:58:08.310Z ·
Cluster 54 (web189, 190, 191, 192) went down.
2026-10-19T13:12:14.448Z ·
Cluster 54 (web189, 190, 191, 192) recovered.

Cluster 10 (web32, 33, 34, 35, 36), Cluster 25 (web105, 106, 107, 108), and 8 other services are down · resolved · 2026-10-15T18:35:14.968Z

Product match: components.

Read the provider’s incident report

2026-10-15T04:00:19.986Z ·
Cluster 29 (web125, 126, 127, 128) recovered.
2026-10-15T04:04:41.967Z ·
Cluster 25 (web105, 106, 107, 108) recovered.
2026-10-15T04:12:07.178Z ·
Cluster 39 (web80, 81, 82, 83) recovered.
2026-10-15T04:59:52.162Z ·
Cluster 10 (web32, 33, 34, 35, 36) went down.
2026-10-15T05:10:22.662Z ·
Cluster 55 (web193, 194, 195, 196) went down.
2026-10-15T05:11:06.359Z ·
Cluster 35 (web150, 151, 152) recovered.
2026-10-15T05:12:14.250Z ·
Cluster 43 (web239, 240, 241, 242) recovered.
2026-10-15T05:13:04.917Z ·
Cluster 47 (web16, 17, 18, 19) recovered.
2026-10-15T05:00:54.071Z ·
Cluster 10 (web32, 33, 34, 35, 36) recovered.
2026-10-15T05:07:01.126Z ·
Cluster 35 (web150, 151, 152) went down.
2026-10-15T05:08:17.000Z ·
Cluster 43 (web239, 240, 241, 242) went down.
2026-10-15T05:08:27.420Z ·
Cluster 44 (web1, 2, 3, 4) went down.

Cluster 24 (web100, 101, 102, 103), Cluster 26 (web110, 111, 112, 113), and 2 other services are down · resolved · 2026-10-14T05:39:41.209Z

Product match: components.

Read the provider’s incident report

2026-10-14T05:39:41.209Z ·
Cluster 26 (web110, 111, 112, 113) recovered.
2026-10-14T01:56:59.072Z ·
Cluster 46 (web11, 12, 13, 14) went down.
2026-10-14T02:41:53.815Z ·
Cluster 38 (web75, 76, 77, 78) recovered.
2026-10-14T01:58:24.519Z ·
Cluster 24 (web100, 101, 102, 103) went down.
2026-10-14T01:58:40.979Z ·
Cluster 26 (web110, 111, 112, 113) went down.
2026-10-14T02:06:38.728Z ·
Cluster 38 (web75, 76, 77, 78) went down.
2026-10-14T02:49:34.197Z ·
Cluster 24 (web100, 101, 102, 103) recovered.
2026-10-14T04:12:53.871Z ·
Cluster 46 (web11, 12, 13, 14) recovered.

Cluster 48 (web21, 22, 23, 24) and Cluster 55 (web193, 194, 195, 196) are down · resolved · 2026-10-08T05:13:15.188Z

Product match: components.

Read the provider’s incident report

2026-10-08T03:58:27.571Z ·
Cluster 55 (web193, 194, 195, 196) went down.
2026-10-08T04:57:11.022Z ·
Cluster 48 (web21, 22, 23, 24) went down.
2026-10-08T05:04:19.569Z ·
Cluster 55 (web193, 194, 195, 196) recovered.
2026-10-08T05:13:15.188Z ·
Cluster 48 (web21, 22, 23, 24) recovered.

Cluster 19 (web180, 181, 182, 183) and Cluster 51 (web62, 63, 64, 65) are down · resolved · 2026-10-07T03:31:18.016Z

Product match: components.

Read the provider’s incident report

2026-10-07T02:43:44.875Z ·
Cluster 51 (web62, 63, 64, 65) recovered.
2026-10-07T01:57:55.521Z ·
Cluster 51 (web62, 63, 64, 65) went down.
2026-10-07T03:10:16.218Z ·
Cluster 19 (web180, 181, 182, 183) went down.
2026-10-07T03:31:18.016Z ·
Cluster 19 (web180, 181, 182, 183) recovered.

Recovery tracker

The provider still reports an active problem.

0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.

Slowdown detection

More successful checks are needed to establish a response-time baseline.

Recent median: unknown · Earlier median: unknown. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.

Emerging down-report signals

No recent emerging problem patterns are available for this service.

Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.

Is it down in your region?

Run one public website check from a community probe. Results describe that probe, not every user in a country.

Check location

Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.

Infrastructure incident context

Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Heart Internet.

GitHub official status · 2026-10-22 00:13:12 UTC

No active incidents recorded.

Cloudflare official status · 2026-10-22 00:13:12 UTC

Elevated Error Rate for Durable Objects in Lisbon · investigating
Incorrect geo location for some Cloudflare WARP users · identified

About Heart Internet status on Iszdown

Check Heart Internet availability, incident history, downtime reports, and website performance.

This page combines the available Heart Internet report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.

61 product-matched official components are listed above. No public website measurement is available in the current window.

Visit the official Heart Internet website · Official provider status · How it works

What to check when Heart Internet is not working

These are troubleshooting suggestions, not a list of currently reported problems.

Heart Internet will not open

Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.

Heart Internet is slow or only one feature fails

Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.

Website troubleshooting guide · Sign-in problems · API errors and timeouts

Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.

Recent Heart Internet outage history

Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.

Incident	Started (UTC)	Recorded duration	Last collected status
Critical PHP Vulnerabilities	2026-10-21 08:10:00 UTC	No resolution recorded	investigating
Cluster 10 (web32, 33, 34, 35, 36), Cluster 44 (web1, 2, 3, 4), and 2 other services are down	2026-10-21 02:05:04 UTC	91 min	resolved
Cluster 24 (web100, 101, 102, 103), Cluster 38 (web75, 76, 77, 78), and 1 other service are down	2026-10-20 02:36:32 UTC	198 min	resolved
Cluster 54 (web189, 190, 191, 192) is down	2026-10-19 12:58:08 UTC	14 min	resolved
Cluster 10 (web32, 33, 34, 35, 36), Cluster 25 (web105, 106, 107, 108), and 8 other services are down	2026-10-15 02:05:48 UTC	989 min	resolved
Cluster 24 (web100, 101, 102, 103), Cluster 26 (web110, 111, 112, 113), and 2 other services are down	2026-10-14 01:56:59 UTC	223 min	resolved
Cluster 48 (web21, 22, 23, 24) and Cluster 55 (web193, 194, 195, 196) are down	2026-10-08 03:58:27 UTC	75 min	resolved
Cluster 19 (web180, 181, 182, 183) and Cluster 51 (web62, 63, 64, 65) are down	2026-10-07 01:57:55 UTC	93 min	resolved

Frequently asked questions about Heart Internet

Is Heart Internet down right now?

Provider reports service problems. The official provider feed identifies an active incident or affected component. This page was assembled at 2026-10-22T00:15:03.000Z.

How many Heart Internet outage reports are there today?

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

Why does Heart Internet show operational when it is not working for me?

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Heart Internet feature.

When was Heart Internet status last updated?

The latest status observation was 2026-10-22T00:01:02.000Z. Only matched product components and incidents are shown. The assessment is recent.

Has Heart Internet had outages before?

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

How do I follow Heart Internet or report a problem?

Use “Watch this service” to save Heart Internet in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.