Respondus
Respondus declares 10 subprocessors in its subprocessor list, which we last checked on Nov 20, 2026 (evidence). They include Amazon Web Services, Microsoft and Salesforce. No published changes since we first read it on Sep 29, 2026. 2 tracked vendors name Respondus as a subprocessor, including Formative and Newsela.
Not loaded by any published homepage.
Subprocessors CSV of Respondus's subprocessors · Atom feed of Respondus's subprocessors DORA draft CSV of Respondus's subprocessors as declared by Respondus what's this? ·
10 third parties.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Amazon Web Services, Inc. | Storage | USA | |
| GoTo (Webinar and Meeting) | Business Communication and Collaboration | USA | |
| Influx | Customer Support | USA | |
| LiveChat | Customer Support | USA | |
| Microsoft 365 | Business Communication and Collaboration | USA | |
| Pardot | Sales and Marketing | USA | |
| PayPal | Payment Processing | USA | |
| Salesforce | Customer Relationship Management | USA | |
| WordPress | Sales and Marketing | USA | |
| Zendesk | Customer Support | USA |
Web TechnologiesCSV of Respondus's web technologies · Atom feed of Respondus's web technologies
Respondus's homepage made 45 requests to 6 domains, and 2 services controlled by another company.
2 third parties by category: Tag managers 1Cookie compliance 1
2 tracked companies loaded by the homepage are not in Respondus's subprocessor list. A website can use a service without it processing customer data.
Subprocessor of (2)CSV of the companies listing Respondus · Atom feed of the companies listing Respondus
Incidents reported by Respondus's subprocessorsCSV of incidents reported by vendors Respondus lists · Atom feed of incidents reported by vendors Respondus lists
8 reported incidents in the last 30 days, by 2 of the vendors Respondus lists as subprocessors.
A subprocessor list names a company, not the service an incident touched. This does not show that Respondus was involved.
| Date | Company | Incident | Impact | Lasted |
|---|---|---|---|---|
| | LogMeIn Rescue, Pro, Central, and G2ARS v5 - Session Failures | major | 1 h 18 min | |
| | LogMeIn Rescue, Pro, Central, and G2ARS v5 - Session failures | major | 2 h 27 min | |
| | Degraded service: Canned responses, supervision and takeover unavailable | minor | 24 min | |
| | Ticketing funcionality not loading | critical | 51 min | |
| | Degraded service: Canned responses, supervision and takeover unavailable | major | 1 h 9 min | |
| | LogMeIn Rescue, Pro, Central, and G2ARS v5 - session failure | major | 9 h 7 min | |
| | LogMeIn Rescue and G2ARS v5 - new session fails | major | 2 h 44 min | |
| | GoTo Connect - Inbound calls failing for customers in Brazil | major | 54 min |
ChangesCSV of Respondus's changes · Atom feed of Respondus's changes
See the list as we read it on any date: Time machine
None since tracking began.