Tracked subprocessors 0 Subprocessor of 3 Third parties loaded 3 Loaded by 0
+ − ⟲
No tracked subprocessors.
Not loaded by any published homepage.
Subprocessors None extracted.
Omnisend's homepage made 100 requests to 8 domains, and 3 services controlled by another company.
Analytics (2): Google Cloud, Cloudflare Cookie compliance (1): Cookiebot 3 third parties by category: Analytics 2 Cookie compliance 1
Third parties 3 · 14 requests
Google Cloud Google Analytics Google Tag Manager 6% of the page's requests 6 Cloudflare Cloudflare Browser Insights cdnjs jQuery 3.6.0 4% of the page's requests 4 Cookiebot Cookiebot 1 4% of the page's requests 4 First party 1 · 86 requests
Omnisend Cloudflare Cybot Envoy Google Font API Google Tag Manager for WordPress 1.16.2 HSTS HTTP/3 MySQL Open Graph PHP Priority Hints Swiper WordPress Yoast SEO 17.4 YouTube 86% of the page's requests 86
3 tracked companies loaded by the homepage are not in Omnisend's subprocessor list. A website can use a service without it processing customer data.
Aug 24: no incident reported Aug 25: no incident reported Aug 26: no incident reported Aug 27: no incident reported Aug 28: no incident reported Aug 29: no incident reported Aug 30: no incident reported Aug 31: no incident reported Sep 1: no incident reported Sep 2: no incident reported Sep 3: no incident reported Sep 4: no incident reported Sep 5: no incident reported Sep 6: no incident reported Sep 7: no incident reported Sep 8: no incident reported Sep 9: no incident reported Sep 10: no incident reported Sep 11: no incident reported Sep 12: no incident reported Sep 13: no incident reported Sep 14: no incident reported Sep 15: no incident reported Sep 16: no incident reported Sep 17: no incident reported Sep 18: no incident reported Sep 19: no incident reported Sep 20: no incident reported Sep 21: no incident reported Sep 22: no incident reported Sep 23: no incident reported Sep 24: no incident reported Sep 25: no incident reported Sep 26: no incident reported Sep 27: no incident reported Sep 28: no incident reported Sep 29: no incident reported Sep 30: no incident reported Oct 1: no incident reported Oct 2: no incident reported Oct 3: no incident reported Oct 4: no incident reported Oct 5: no incident reported Oct 6: no incident reported Oct 7: no incident reported Oct 8: no incident reported Oct 9: no incident reported Oct 10: no incident reported Oct 11: no incident reported Oct 12: no incident reported Oct 13: no incident reported Oct 14: no incident reported Oct 15: no incident reported Oct 16: no incident reported Oct 17: no incident reported Oct 18: no incident reported Oct 19: no incident reported Oct 20: no incident reported Oct 21: no incident reported Oct 22: no incident reported Oct 23: no incident reported Oct 24: no incident reported Oct 25: no incident reported Oct 26: no incident reported Oct 27: no incident reported Oct 28: no incident reported Oct 29: no incident reported Oct 30: no incident reported Oct 31: no incident reported Nov 1: no incident reported Nov 2: no incident reported Nov 3: no incident reported Nov 4: no incident reported Nov 5: no incident reported Nov 6: no incident reported Nov 7: no incident reported Nov 8: no incident reported Nov 9: no incident reported Nov 10: no incident reported Nov 11: no incident reported Nov 12: no incident reported Nov 13: no incident reported Nov 14: no incident reported Nov 15: no incident reported Nov 16: 1 incident (1 no impact stated) Nov 17: no incident reported Nov 18: no incident reported Nov 19: no incident reported Nov 20: no incident reported Nov 21: no incident reported 90 days ago today
1 incident in 90 days0 major or critical19 min typical time to resolveIncidents per month 0 2 4 Dec 2025: 1 incident (1 no impact stated) Jan 2026: 3 incidents (2 minor, 1 no impact stated) · typical time to resolve 1 h 10 min Feb 2026: 0 incidents Mar 2026: 3 incidents (1 minor, 2 no impact stated) · typical time to resolve 1 h 41 min Apr 2026: 3 incidents (2 critical, 1 minor) · typical time to resolve 18 min May 2026: 1 incident (1 no impact stated) · typical time to resolve 6 h 42 min Jun 2026: 0 incidents Jul 2026: 0 incidents Aug 2026: 0 incidents Sep 2026: 0 incidents Oct 2026: 0 incidents Nov 2026: 1 incident (1 no impact stated) · typical time to resolve 19 min Dec 2025 Jan 2026 Feb Mar Apr May Jun Jul Aug Sep Oct Nov critical major minor no impact stated
As Omnisend's status page reports its own incidents (scheduled maintenance left out), read every few hours since Oct 3, 2025 (evidence )
None since tracking began.