Tracked subprocessors 0 Subprocessor of 0 Third parties loaded 7 Loaded by 0
+ − ⟲
No tracked subprocessors.
Not listed by any tracked vendor.
Not loaded by any published homepage.
Subprocessors None extracted.
amazee.io's homepage made 164 requests to 22 domains, and 7 services controlled by another company.
Analytics (5): Google Cloud, HubSpot, LinkedIn, Leadfeeder; usually detected as Analytics: Cloudflare Cookie compliance (1): CookieHub Other (1): CMS: Prismic 7 third parties by category: 5 1 1
Third parties 7 · 125 requests
Prismic Prismic 58% of the page's requests 95
Google Cloud Google Analytics Google Optimize Google Tag Manager YouTube 9% of the page's requests 15 HubSpot HubSpot HubSpot Analytics 4% of the page's requests 6 LinkedIn Linkedin Insight Tag 2% of the page's requests 4 CookieHub CookieHub 1% of the page's requests 2 Cloudflare cloudflare.com <1% of the page's requests 1 First party 1 · 39 requests
amazee.io Font Awesome 5.12.1 Gatsby 4.13.1 HSTS HTTP/3 Lagoon Matomo Analytics Matomo Tag Manager Open Graph PWA React Webpack cdnjs web-vitals 24% of the page's requests 39
6 tracked companies loaded by the homepage are not in amazee.io's subprocessor list. A website can use a service without it processing customer data.
Certified Says it complies with Certifications as amazee.io's trust center lists them; reports are usually shared on request (evidence )
Aug 15: no incident reported Aug 16: no incident reported Aug 17: no incident reported Aug 18: no incident reported Aug 19: no incident reported Aug 20: no incident reported Aug 21: no incident reported Aug 22: no incident reported Aug 23: no incident reported 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: 1 incident (1 no impact stated) 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: 1 incident (1 major) 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: 1 incident (1 critical) 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: 1 incident (1 no impact stated) Oct 22: no incident reported Oct 23: no incident reported Oct 24: no incident reported Oct 25: no incident reported Oct 26: 1 incident (1 no impact stated) Oct 27: 1 incident (1 no impact stated) Oct 28: no incident reported Oct 29: no incident reported Oct 30: 1 incident (1 no impact stated) Oct 31: no incident reported Nov 1: no incident reported Nov 2: 1 incident (1 no impact stated) 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 90 days ago today
9 incidents in 90 days2 major or critical3 h 43 min typical time to resolve17 h 8 min longest majorIncidents per month 0 3 6 Dec 2025: 1 incident (1 major) · typical time to resolve 47 h 16 min Jan 2026: 3 incidents (1 minor, 2 no impact stated) · typical time to resolve 20 h 3 min Feb 2026: 2 incidents (1 minor, 1 no impact stated) · typical time to resolve 49 days Mar 2026: 2 incidents (1 critical, 1 minor) · typical time to resolve 25 h 11 min Apr 2026: 5 incidents (2 minor, 3 no impact stated) · typical time to resolve 3 h 32 min May 2026: 2 incidents (1 minor, 1 no impact stated) · typical time to resolve 14 days Jun 2026: 3 incidents (2 minor, 1 no impact stated) · typical time to resolve 16 h 10 min Jul 2026: 5 incidents (5 no impact stated) · typical time to resolve 3 h 6 min Aug 2026: 0 incidents Sep 2026: 3 incidents (1 critical, 1 major, 1 no impact stated) · typical time to resolve 3 h 43 min Oct 2026: 4 incidents (4 no impact stated) · typical time to resolve 19 min Nov 2026: 1 incident (1 no impact stated) Dec 2025 Jan 2026 Feb Mar Apr May Jun Jul Aug Sep Oct Nov critical major minor no impact stated
Components affected Component Incidents Bar amazee.ai infrastructure 2 amazee.ai infrastructure: au103 2 amazee.ai infrastructure: ch103 2 amazee.ai infrastructure: de-eu101 2 amazee.ai infrastructure: de103 2 amazee.ai infrastructure: uk103 2 amazee.ai infrastructure: us103 2 amazee.ai infrastructure: us104 2
As amazee.io's status page reports its own incidents (scheduled maintenance left out), read every few hours since Oct 20, 2025 (evidence )
None since tracking began.
amazee.io