Subprocessors 13 Relied on by 0
+ − ⟲
Not listed by any tracked vendor.
Subprocessors 16 third parties. CSVof Addigy's subprocessors · Atom
Name Purpose Location Listed since Amazon Web Services Seattle, Washington Sep 29, 2026 Atlassian Sydney, Australia Sep 29, 2026 Auth0 Bellevue, Washington Sep 29, 2026 ChurnZero Washington, D.C. Sep 29, 2026 Cloudflare San Francisco, California Sep 29, 2026 Google Cloud Platform Menlo Park, California Sep 29, 2026 Hubspot, Inc. Cambridge, Massachusetts Sep 29, 2026 MongoDB Atlas New York, New York Sep 29, 2026 OwnBackup Englewood Cliffs, New Jersey Sep 29, 2026 Sage Intacct San Jose, California Sep 29, 2026 Salesforce San Francisco, California Sep 29, 2026 Slack San Francisco, California Sep 29, 2026 SSL.com Palo Alto, California Sep 29, 2026 Stripe San Francisco, California Sep 29, 2026 Upflow New York, New York Sep 29, 2026 Zendesk Sanfrancisco, California Sep 29, 2026
Compliance Certified Says it complies with Certifications as Addigy's trust center lists them; reports are usually shared on request (evidence )
Service status Jul 2: before our history of this status page Jul 3: before our history of this status page Jul 4: before our history of this status page Jul 5: before our history of this status page Jul 6: before our history of this status page Jul 7: before our history of this status page Jul 8: before our history of this status page Jul 9: 1 incident (1 minor) Jul 10: no incident reported Jul 11: no incident reported Jul 12: no incident reported Jul 13: no incident reported Jul 14: no incident reported Jul 15: no incident reported Jul 16: no incident reported Jul 17: no incident reported Jul 18: no incident reported Jul 19: no incident reported Jul 20: no incident reported Jul 21: no incident reported Jul 22: no incident reported Jul 23: no incident reported Jul 24: no incident reported Jul 25: no incident reported Jul 26: no incident reported Jul 27: no incident reported Jul 28: no incident reported Jul 29: no incident reported Jul 30: no incident reported Jul 31: no incident reported Aug 1: no incident reported Aug 2: no incident reported Aug 3: 2 incidents (2 no impact stated) Aug 4: no incident reported Aug 5: no incident reported Aug 6: no incident reported Aug 7: no incident reported Aug 8: no incident reported Aug 9: no incident reported Aug 10: no incident reported Aug 11: no incident reported Aug 12: no incident reported Aug 13: no incident reported Aug 14: no incident reported 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: 1 incident (1 major) 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: 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 90 days ago today
4 incidents in 82 days1 major or critical1 h 49 min typical time to resolve1 h 49 min longest majorIncidents per month 0 2 4 Jul 2026: 1 incident (1 minor) · partial: our history begins Jul 9 · typical time to resolve 5 days Aug 2026: 3 incidents (1 major, 2 no impact stated) · typical time to resolve 52 min Sep 2026: 0 incidents Jul 2026 Aug Sep critical major minor no impact stated before or partly before our history
Components affected Component Incidents Bar Addigy Cloud Interface 2 Addigy Identity 1 Addigy MDM Service 1
As Addigy's status page reports its own incidents (scheduled maintenance left out), read every few hours since Jul 9, 2026 (evidence )
Changes None since tracking began.