Respan

respan.ai

4 tracked vendors name Respan as a subprocessor, including Retell AI, Mem0 and Trellis Tech. We have not found a subprocessor list published by Respan. We monitor 4 of its documents, which we last checked on Nov 11, 2026.

Subprocessors

None extracted.

Web TechnologiesCSV · Atom

Respan's homepage made 191 requests to 11 domains, and 6 services controlled by another company.

Advertising (3): Google Cloud, OpenAI, X Corp.Analytics (2): RB2B; usually detected as Analytics: posthogOther (1): reviewed as Appointment scheduling: Cal.com

6 third parties by category: Advertising 3Analytics 2Other 1

Third parties 6 · 111 requests
Cal.com cal.com 47% of the page's requests 90
Google Cloud DoubleClick Floodlight Google Analytics Google Tag Manager 5% of the page's requests 10
OpenAI ChatGPT Ads Measurement Pixel 2% of the page's requests 4
X Corp. Twitter Ads 2% of the page's requests 3
posthog posthog.com 2% of the page's requests 3
RB2B RB2B <1% of the page's requests 1
First party 1 · 80 requests
Respan Framer Motion GSAP HSTS Lucide Next.js 16.3.0 Next.js App Router Open Graph PWA Priority Hints React Turbopack Vercel Vercel Analytics Webpack 42% of the page's requests 80

5 tracked companies loaded by the homepage are not in Respan's subprocessor list. A website can use a service without it processing customer data.

Subprocessor of (4)CSV · Atom

4 companies
  • Mem0 mem0.ai
  • Retell AI retellai.com
  • Trellis Tech trellistech.com LLM observability, tracing, and cost monitoring for AI agent executions
  • Wonderchat wonderchat.io Provision of natural language processing and generation services

Service statusCSV · Atom

Aug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: 1 incident (1 minor)Sep 27: no incident reportedSep 28: no incident reportedSep 29: 1 incident (1 minor)Sep 30: no incident reportedOct 1: no incident reportedOct 2: no incident reportedOct 3: no incident reportedOct 4: no incident reportedOct 5: no incident reportedOct 6: no incident reportedOct 7: no incident reportedOct 8: no incident reportedOct 9: no incident reportedOct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: no incident reportedOct 15: no incident reportedOct 16: no incident reportedOct 17: no incident reportedOct 18: no incident reportedOct 19: no incident reportedOct 20: no incident reportedOct 21: no incident reportedOct 22: no incident reportedOct 23: no incident reportedOct 24: no incident reportedOct 25: no incident reportedOct 26: no incident reportedOct 27: no incident reportedOct 28: no incident reportedOct 29: no incident reportedOct 30: no incident reportedOct 31: no incident reportedNov 1: no incident reportedNov 2: no incident reportedNov 3: no incident reportedNov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reported

90 days agotoday

  • 2 incidents in 47 days
  • 0 major or critical
  • 13 h 47 min typical time to resolve
BeganIncidentImpactLasted
Delayed request logs across all regionsminor1 h 58 min
Response API gateway affectedminor13 h 47 min

Incidents per month

0 2 4 Sep 2026: 2 incidents (2 minor) · partial: our history begins Sep 26 · typical time to resolve 13 h 47 min Oct 2026: 0 incidents Nov 2026: 0 incidents Sep 2026Oct Nov

critical major minor no impact stated before or partly before our history

Components affected

ComponentIncidents
Gateway services2
Enterprise web1
Logging services1
Platform web1

As Respan's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

ChangesCSV · Atom

None since tracking began.

Rating badge for Respan's site

Respan transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/respan"><img src="https://thirdpartyindex.com/badge/respan.svg" alt="Respan transparency rating on Third Party Index" height="20"></a>
[![Respan transparency rating on Third Party Index](https://thirdpartyindex.com/badge/respan.svg)](https://thirdpartyindex.com/vendors/respan)